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.
Bug 2215426 - [Regression] VMware Image-based and full host boot disk based Provisioning fails with error-: Could not find virtual machine network interface matching <IP>
Summary: [Regression] VMware Image-based and full host boot disk based Provisioning fa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.14.0
Assignee: satellite6-bugs
QA Contact: sganar
URL:
Whiteboard:
: 2215425 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-16 00:58 UTC by Satyajit Das
Modified: 2024-05-02 17:29 UTC (History)
10 users (show)

Fixed In Version: rubygem-fog-vsphere-3.6.1.gem
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2218954 2228127 (view as bug list)
Environment:
Last Closed: 2023-11-08 14:19:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github fog fog-vsphere pull 283 0 None Merged Revert "Unify network ID attribute" 2023-06-22 10:45:13 UTC
Github fog/fog-vsphere/releases/tag/3.6.1 0 None None None 2023-06-22 18:21:26 UTC
Red Hat Issue Tracker SAT-18485 0 None None None 2023-06-20 07:21:41 UTC
Red Hat Knowledge Base (Solution) 6972882 0 None None None 2023-06-22 06:46:48 UTC
Red Hat Product Errata RHSA-2023:6818 0 None None None 2023-11-08 14:19:59 UTC

Description Satyajit Das 2023-06-16 00:58:43 UTC 
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
Comment 3 Sayan Das 2023-06-16 11:52:15 UTC 
*** Bug 2215425 has been marked as a duplicate of this bug. ***
Comment 5 Sayan Das 2023-06-20 06:41:18 UTC 
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.
Comment 6 Chris Roberts 2023-06-20 18:30:49 UTC 
We are going to make a new version of fog-vsphere for satellite that includes this commit so we can deliver this to customers.
Comment 10 Chris Roberts 2023-06-22 18:25:38 UTC 
Fixed with https://rubygems.org/gems/fog-vsphere/versions/3.6.1

* Reverted the commit that caused the issue
Comment 11 sganar 2023-07-27 10:10:04 UTC 
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
Comment 14 errata-xmlrpc 2023-11-08 14:19:49 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.