Bug 1378992 - CFME doesn't pick up blank vCenter folders
Summary: CFME doesn't pick up blank vCenter folders
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.6.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: GA
: 5.7.0
Assignee: Adam Grare
QA Contact: Leo Khomenko
URL:
Whiteboard: vmware:provision
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-23 19:58 UTC by Colin Arnott
Modified: 2019-12-16 06:53 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-04 16:50:28 UTC
Category: ---
Cloudforms Team: VMware
Target Upstream Version:


Attachments (Terms of Use)

Description Colin Arnott 2016-09-23 19:58:12 UTC
Description of problem:
If there is a folder in vCenter that does not contain any VMs, CFME will not pick up or display that folder. We have a process that creates new folders if a folder does not exist, however CFME does not see this folder because there is nothing in it. This prevents us from placing VMs in that new folder. We expect CFME to pick up that folder and allow us to place VMs in it.

Version-Release number of selected component (if applicable):
cfme-5.6.1.2

How reproducible:
this vmware environment

Steps to Reproduce:
1) Folder ABCD doesn't exist
2) user creates folder ABCD
3) Folder ABCD is physically created in VMware (and can be seen right away)


Actual results:
Folder cannot be seen in CloudForms

Expected results:
I should be able to see folders empty or not

Additional info:
I attempted to reproduce this with vmware 5.1 and cfme-5.6.1.2, but was unable; not sure what version of vmware this env uses: version is pending.

Comment 2 Adam Grare 2016-09-26 17:05:06 UTC
I also attempted to reproduce this but was unable to.
After creating a new folder a CreateFolder event was emitted and a full refresh was started.

After this refresh completed I checked the DB and a record for the new folder existed.  The folder was also visible in the VMs & Templates view (/ems_infra/1?display=ems_folders&vat=true).

The only page I didn't see the folder was the tree view on the vm explorer (I presume because there were no VMs in it).

Can we confirm they waited for a full refresh to complete?  If after a full refresh the folder doesn't exist we should collect some logs to find out what could be wrong.

Comment 5 Adam Grare 2016-10-04 16:50:28 UTC
Closing since the empty folder was confirmed to be picked up by inventory refresh.


Note You need to log in before you can comment on or make changes to this bug.