Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Description of problem:
Install RHEL on ESXi host, then install cloud-init,if the open-vm-tools installed after reboot the cloud-init could not detect the iso metadata file, if uninstall the open-vm-tools, the cloud-init will be disabled
Version-Release number of selected component (if applicable):
RHEL-8
cloud-init-21.1-7.el8.noarch
How reproducible:
100%
Steps to Reproduce:
1.Install RHEL8 guest on ESXi host
2.Start the guest and install cloud-init
3.Attach a iso metadata file in the guest via CD/DVD
4.Reboot guest and check the guest whether configure follow the iso metadata file
5.Uninstall the open-vm-tools and reboot the guest
6.Check the guest whether configure follow the iso metadata file and the cloud-init service status
Actual results:
After step 4, cloud-init doesn't configure the guest following the iso metadata file as it can't detect the iso file.
After step 6, cloud-init is disabled and cloud-init doesn't configure the guest follow the iso metadata file
Expected results:
Cloud-init can configure the guest follow the iso metadata file with open-vm-tools installed
Additional info: