Verified. Tested on Satellite 6.13.3 Snap 1.0 rubygem-fog-vsphere-3.6.2-1.el8sat.noarch Steps followed: 1. Deploy a fresh satellite(6.13.3) 2. Add VMware as compute resource and create an image. 3. Try to deploy the host using the same image. Observation: Image-based provisioning is successful, no issues observed.
Hey @sganar Thanks for the verification. As this was a regression from the previous bug and has no definite reproducer steps ( at least not for us ), Can you please confirm that the changes from the following commit https://github.com/fog/fog-vsphere/commit/ddbff201ba50462dec7359e34baf5959a819ff34 exist in 6.13.3 Snap 1.0 please ( as a part of same QE verification ) ? Two files to be checked for the change in code would be /usr/share/gems/gems/fog-vsphere-3.6.2/lib/fog/vsphere/requests/compute/get_network.rb /usr/share/gems/gems/fog-vsphere-3.6.2/lib/fog/vsphere/requests/compute/list_networks.rb -- Sayan
Hey @saydas Yes, I can confirm all the changes as per commit https://github.com/fog/fog-vsphere/commit/ddbff201ba50462dec7359e34baf5959a819ff34 exists in 6.13.3 snap 1.0
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 (Important: Satellite 6.13.3 Async Security Update), 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-2023:4466