Red Hat Bugzilla – 2215425 – [Regression] VMware Image-based and full host boot disk based Provisioning fails with error-: Could not find virtual machine network interface matching <IP>
Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
[Regression] VMware Image-based and full host boot disk based Provisioning fails with error-: Could not find virtual machine network interface matching <IP>
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
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