Bug 1755844 - @vm.storage on some VMs result nil
Summary: @vm.storage on some VMs result nil
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.10.5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: GA
: 5.11.0
Assignee: Adam Grare
QA Contact: Kedar Kulkarni
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks: 1765583
TreeView+ depends on / blocked
 
Reported: 2019-09-26 10:41 UTC by Gellert Kis
Modified: 2023-03-24 15:31 UTC (History)
16 users (show)

Fixed In Version: 5.11.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1765583 (view as bug list)
Environment:
Last Closed: 2019-12-13 14:54:09 UTC
Category: Inquiry
Cloudforms Team: VMware
Target Upstream Version:
Embargoed:
mfeifer: mirror+

Attachments (Terms of Use)

Comment 15 Tina Fitzgerald 2019-10-14 17:00:12 UTC 
Hi Gellert,

Can you provide an update?

Thanks,
Tina
Comment 18 Adam Grare 2019-10-22 19:28:20 UTC 
https://github.com/ManageIQ/manageiq-providers-vmware/pull/361
Comment 23 Kedar Kulkarni 2019-10-30 15:43:57 UTC 
After discussing with Adam offline, I setup our vcenter6.0 to have 2 datacenters, each with 1 cluster and 1 host. Both datacenters had identical iscsi/nfs storage domains, when I added provider to CloudForms build 5.11.0.27.20191001204742_d9cf38b I didn't see duplicate datastores in the UI under Compute->Infrastructure->Datastores.  Hence closing the bz with the fact that if we don't create the duplicate in the first place then it can't put a vm on a storage that won't get created causing vm.storage being nil. Hence verified.
Note You need to log in before you can comment on or make changes to this bug.