Bug 2215426
| Summary: | [Regression] VMware Image-based and full host boot disk based Provisioning fails with error-: Could not find virtual machine network interface matching <IP> | |||
|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Satyajit Das <sadas> | |
| Component: | Compute Resources - VMWare | Assignee: | satellite6-bugs <satellite6-bugs> | |
| Status: | CLOSED ERRATA | QA Contact: | sganar | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 6.13.0 | CC: | ahumbe, arsingh, chrobert, lstejska, mhulan, momran, pcreech, rlavi, saydas, shwsingh | |
| Target Milestone: | 6.14.0 | Keywords: | Regression, Triaged | |
| Target Release: | Unused | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | rubygem-fog-vsphere-3.6.1.gem | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2218954 2228127 (view as bug list) | Environment: | ||
| Last Closed: | 2023-11-08 14:19:49 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
*** Bug 2215425 has been marked as a duplicate of this bug. *** Good news. After discussing with Chris about the issue, I created a patch out of https://github.com/fog/fog-vsphere/commit/ddbff201ba50462dec7359e34baf5959a819ff34 and sent it to the end-user. And the end-user confirmed that it fixes the issue reported in this BZ. We are going to make a new version of fog-vsphere for satellite that includes this commit so we can deliver this to customers. Fixed with https://rubygems.org/gems/fog-vsphere/versions/3.6.1 * Reverted the commit that caused the issue Verified. Tested on Satellite 6.14 Snap 7.0 rubygem-fog-vsphere-3.6.2-1.el8sat.noarch Steps followed: 1. Deploy a fresh satellite(6.14) 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. The changes in the https://github.com/fog/fog-vsphere/commit/ddbff201ba50462dec7359e34baf5959a819ff34 are present on 6.14 Snap 7.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.14 security and bug fix 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:6818 |
Description of problem: VMware Image-based and full host boot disk-based Provisioning fails with the error-: Could not find virtual machine network interface matching <IP> Version-Release number of selected component (if applicable): Satellite 6.13.1 rubygem-fog-vsphere-3.6.0-1.el8sat.noarch How reproducible: 100% (Customer's env) Steps to Reproduce for Image-based : 1. Deploy a fresh satellite (Version: 6.13.1) 2. Add VMware as compute resource and associate an image to the compute resource(). 3. Try to deploy the host using the same image (Provisioning method:cloud-init and user data templates). Actual results: Image-based build fails with errors : ----------------- 2023-06-15T12:21:21 [I|app|594918af] Adding Compute instance for client.example.com 2023-06-15T12:21:22 [W|app|594918af] Orchestration::Compute: Could not match network interface #<Nic::Managed id: nil, mac: nil, ip: "xx.xx.xx.xxx", type: "Nic::Managed", name: "client.example.com", host_id: nil, subnet_id: 2, domain_id: 1, attrs: {}, created_at: nil, updated_at: nil, provider: nil, username: nil, password: nil, virtual: false, link: true, identifier: "", tag: "", attached_to: "", managed: true, mode: "balance-rr", attached_devices: "", bond_options: "", primary: true, provision: true, compute_attributes: {"type"=>"VirtualVmxnet3", "network"=>"dvportgroup-xx"}, execution: true, ip6: "", subnet6_id: nil> 2023-06-15T12:21:22 [W|app|594918af] Could not find virtual machine network interface matching xx.xx.xx.xx Expected results: Build system without issues Additional info: The customer had faced the same issue earlier, and applied the steps from the article [1] to remediate the issue, however after upgrading to 6.13.1 again started seeing the same behavior. [1]https://access.redhat.com/solutions/6972882