Bug 2119911
Summary: | VMware Image 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: | Chris Roberts <chrobert> | ||||||
Status: | CLOSED ERRATA | QA Contact: | addubey | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | high | ||||||||
Version: | 6.10.7 | CC: | addubey, aganbat, ahumbe, ajambhul, bvassova, chrobert, jyejare, lstejska, mhulan, momran, pcreech, rlavi, saydas, shwsingh, wclark | ||||||
Target Milestone: | 6.13.0 | Keywords: | PrioBumpGSS, Regression, Triaged, WorkAround | ||||||
Target Release: | Unused | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | fog-vsphere-3.5.3 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | |||||||||
: | 2174994 (view as bug list) | Environment: | |||||||
Last Closed: | 2023-05-03 13:21:36 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: | |||||||||
Attachments: |
|
Description
Satyajit Das
2022-08-19 22:14:41 UTC
Sayan, Is this customer using vCenter 6.7 or 7.0? (In reply to Chris Roberts from comment #5) > Sayan, > > Is this customer using vCenter 6.7 or 7.0? The customer is using 6.7. Chris, Marek, do you think we should revert https://github.com/fog/fog-vsphere/commit/9b88e63b8eef2ba9a4fcad49c1df9027cef52624 ? it seems like the issue occurred in fog-vsphere v3.5.1, or maybe you can identify the line that broke it? Adding qe_test_coverage flag as its raised in SD-QE Cadence to triage if we could add this in automation. What SD said: ``` A fare amount of users have reported this issue and for all of them downgrading the version of tfm-rubygem-fog-vsphere helped to fix the issue. ``` Ron, that's also affecting the issue leos is working on, so my thoughts are revert the commit get a new version out so it fixes the 2 bugs for customers that are regression, then make a new redmine for these 2 issues I heard from one customer that the patch fixed their issue. Made an updated version of fog-vsphere here: https://rubygems.org/gems/fog-vsphere/versions/3.5.3 Moving the BZ to POST so the delivery team can bring the new version of the gem in, also added it to the fixed in version. - Chris Roberts Created attachment 1947040 [details]
Hotfix RPM for Satellite 6.11.4 on RHEL7
INSTALL INSTRUCTIONS:
1. Take a complete backup or snapshot of Satellite 6.11.4 server
2. Download the hotfix RPM matching your Satellite and RHEL version and copy it to the affected Satellite server
3. # yum install ./tfm-rubygem-fog-vsphere-3.5.2-3.HOTFIXRHBZ2119911.el7sat.noarch.rpm --disableplugin=foreman-protector
4. # systemctl restart foreman.service
Created attachment 1947042 [details]
Hotfix RPM for Satellite 6.11.4 (RHEL8) or 6.12.2
INSTALL INSTRUCTIONS:
1. Take a complete backup or snapshot of Satellite server
2. Download the hotfix RPM matching your Satellite and RHEL version and copy it to the affected Satellite server
3. # dnf install ./rubygem-fog-vsphere-3.5.2-3.HOTFIXRHBZ2119911.el8sat.noarch.rpm --disableplugin=foreman-protector
4. # systemctl restart foreman.service
NOTE: This hotfix works with Satellite version 6.11 or 6.12, running on RHEL8
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 Release), 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:2097 |