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.

See description in cloud-init bug #1641190 and NetworkManager bug #1663253.

Composer seems to have to include a workaround to make Azure images work.

I don't think this is an issue for composer. Our vhd.ks is already using WALinuxAgent instead of cloud-init.

Is there some other work that needs to be done? Vendula Poncova changed this in commit b594fa99bc765a9ea54dd7d61ac49d3b72b6581e back in October.

Not sure if we need a workaround but I'm seeing this issue too. The VM is stuck in the Creating status on Azure for more than 10 minutes.

for reference this is what I'm seeing:

> https://bugzilla.redhat.com/show_bug.cgi?id=1641190#c1
>
> With  this issue existing, cloud-init can't successfully decrypt ssh public key, so if we create a vm with public ssh key logging in, we can't login the vm with ssh > public key. And Azure VM's status can't change from creating to running.

This has not been an issue in the last couple of months. We've had Azure images successfully working in CI so closing.