Red Hat Bugzilla – Bug 1170276
Provisioning fails with VMware Compute Resource if the vCenter's datacenter is using nested folders.
Last modified: 2017-03-17 17:02:21 EDT
Description of problem: ----------------------------------------- This issue still exists in Foreman 1.5.1. However, the patch only works if their are no organizational folders in vSphere for the cluster group. If a cluster is organized into folders under a datacenter, foreman fails to see any clusters. This appears to be an underlying issue with either fog or rbvmomi though. When creating a new host using VMware as a compute resource and selecting 'Deploy on' datacenter cluster folders do not show up; additionally nested folders aren't showing up either. 1) The current upstream patch that allows the use of cluster folders in VMwares datacenters: https://github.com/fog/fog/commit/66e5521 After the committing the patch vm's are able to be automatically provisioned from Satellite using VMware as a compute resource: vCenter -> datacenter chosen in dropdown menu -> cluster folder 2) This leads to an issue if nested cluster folders are created under a datacenter with or without the previously mentioned patch. Non working example with patch or without patch: vCenter -> datacenter chosen in dropdown menu -> cluster folder -> nested cluster folder Version-Release number of selected component (if applicable): ----------------------------------------- 6.0.6 How reproducible: ----------------------------------------- Easily reproducible Steps to Reproduce: ----------------------------------------- 1. Add VMware as a compute resource on Satellite 6. 2. Create a New Host and attempt to select a VMware datacenter cluster folder or nested folder for the 'Deploy on' option. 3. The resource does not exist. Actual results: ----------------------------------------- If the patch https://github.com/fog/fog/commit/66e5521 is not applied the new host is not able to be created. If the patch is applied it appears the cluster folder is selectable however provisioning fails, please see attached screenshots and debugs. Expected results: ----------------------------------------- The cluster folder or nested cluster folder is a selectable option when creating a new host and is able to be provisioned properly on Satellite 6 when using VMware as a Compute Resource. Additional info: ----------------------------------------- https://github.com/fog/fog/blob/master/lib/fog/vsphere/requests/compute/list_clusters.rb https://github.com/fog/fog/blob/master/lib/fog/vsphere/requests/compute/create_vm.rb
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created attachment 964745 [details] foreman-debug
Created attachment 964747 [details] sosreport
Connecting redmine issue http://projects.theforeman.org/issues/8581 from this bug
fixed by upstream foreman PRs: https://github.com/theforeman/foreman/pull/2014 and https://github.com/theforeman/foreman/pull/2095. Can be cherry picked with: Fog repo git: https://github.com/fog/fog.git Fog commit sha1: 23bd65232bbcd0b3ae67ac40abebb9757dfa9280 Fog commit url: https://github.com/shlomizadok/fog/commit/23bd65232bbcd0b3ae67ac40abebb9757dfa9280 Foreman repo git: https://github.com/theforeman/foreman.git Foreman commit sha1: de764bf506e0b1bc3ca66f477d06f57c502e002b Foreman commit url: https://github.com/shlomizadok/foreman/commit/de764bf506e0b1bc3ca66f477d06f57c502e002b
Also seems like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1142861 - can you please verify and close if so?
When vCenter's datacenter is using nested folders, failed to display "Cluster", maybe related patches are not applied yet, so change status to Assigned. Please check picture attached, thanks!
Created attachment 1012119 [details] cluster in folder
Created attachment 1012122 [details] failed to display
Can you guys re-test, I see the patch in the fog library now.
If it fails, the patch is not correct.
First of all are we talking about 6.1.0 or 6.0.4? Lukas is referencing 6.0 repos and fog 1.21.0 which is part of 6.0, yet this bug is ACK'ed against Satellite 6.1.0 which is fog 1.24.0. If it needs to be fixed in Satellite 6.1.0 and Satellite 6.0.z please open separate bugs. The patch is applied during build based on what was provided. http://git.app.eng.bos.redhat.com/git/katello-thirdparty.git/tree/rubygem-fog/fog-add-full-path-vsphere.patch?h=SATELLITE-6.1.0 http://git.app.eng.bos.redhat.com/git/katello-thirdparty.git/tree/rubygem-fog/fog-add-full-path-vsphere.patch?h=SATELLITE-6.0.4
Since this bug is ACK'ed against Satellite 6.1.0, I verified it on Satellite-6.1.0-RHEL-7-20150407.1, it still failed to show cluster in nested folders, so change status to Assigned.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1592
Accidentally closed with 6.1.1 errata
From a rel note perspective, this is covered afaik as part of BZ 1223962: VMware Compute Resource issue in the Release notes.
Upstream bug component is Compute Resources
Until this is resolved I am working around it on Satellite 6.1.2 by doing the following [root@sat-dev ~]# cp /opt/rh/ruby193/root/usr/share/gems/gems/fog-1.24.0/lib/fog/vsphere/requests/compute/list_clusters.rb{,.old} [root@sat-dev ~]# curl https://raw.githubusercontent.com/fog/fog/master/lib/fog/vsphere/requests/compute/list_clusters.rb -o /opt/rh/ruby193/root/usr/share/gems/gems/fog-1.24.0/lib/fog/vsphere/requests/compute/list_clusters.rb [root@sat-dev ~]# katello-service restart
Still same issue with Satellite 6.1.4. The work around from Tristan hoar was working for me but it's not available any more ??? Tristan, can you please put it online again. Thanks.
Is there a timeline or other workaround. This was working for a period with 6.0 but seems to have regressed after upgrading to 6.1.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions
Reset docs contact <> daobrien
** SATELLITE 6.1 HOTFIX INSTRUCTIONS ** This patch only applies to Satellite 6.1 1) Download attached 170276-HOTFIX.patch hotfix patch file to your Satellite 2) cp 170276-HOTFIX.patch /opt/rh/ruby193/root/usr/share/gems/gems/fog-1.24.1/ 3) cd /opt/rh/ruby193/root/usr/share/gems/gems/fog-1.24.1/ 4) patch -p1 < 170276-HOTFIX.patch 5) katello-service restart 6) resume operations
Created attachment 1174702 [details] hotfix patch
Hi Mike, Customer in case# 01611941 has tried entire system update (and katello-installer --upgrade) and the hotfix but it still doesn't work. Please find attached screenshot shared by customer in ticket. Preetesh
Created attachment 1177131 [details] Case-01611941
Verified in Satellite 6.1.10 Snap 1.1 Cluster now shows up as expected. See attached screenshot for verification.
Created attachment 1203794 [details] verification screenshot
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1938