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.

When a guest image with cloud-init installed is started in a non-cloud environment, there is a long delay during boot while cloud-init waits for services (that don't exist) to respond to its requests.

This prevents a single guest image with cloud-init installed from being used in both environments. There is a KB article thast provides a work-around (https://access.redhat.com/solutions/3798671), but there's a desire to remove the need for this work-around.

This is a request for a solution that will enable a guest image with cloud-init installed to be self-aware of it's environment and avoid boot delays.

See also bug 1654683 and thread http://post-office.corp.redhat.com/archives/rhel8-devel/2018-December/thread.html#00066.

This is fixed on cloud-init >= 18.5-5.el7 with the presence of ds-identify. The script ds-identify should identify the environment that cloud-init is running and adjust the runtime accordingly, even if the instance is not running on a cloud platform - in which cloud-init will use the NoCloud DataSouce.

If you believe there's a bug on cloud-init >= 18.5-5.el7 please reopen this bug.