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.
DescriptionKlaas Weyermann
2022-05-02 06:08:15 UTC
Description of problem:
It seems there is a known problem in 2.3.0.2 where network gets (occasionally) messed up during firstboot by walinuxagent. This leaves the newly deployed VM without network
According to MS this should be fixed in 2.3.1.1 via this PR: https://github.com/Azure/WALinuxAgent/pull/2283
Please backport fix or update package to 2.3.1.1
Version-Release number of selected component (if applicable):
2.3.0.2-2
How reproducible:
This seems to happen to about 1/3 of my Azure deployments.
(In reply to Klaas Demter from comment #18)
> any reason this won't be fixed?
This are just bureaucratic measures. As we cloned this BZ to bug#2092753 (RHEL-8.6.z backport fix) this bug was re-targeted to RHEL-8.7. Since we already have a rebase bug#2083465 for RHEL-8.7 which already contains this fix, this BZ became obsolete. In other words, the fix will be present in all relevant branches, and this does not depend on this BZ to be open anymore.
Thanks!
the other linked issues are private, so I can't see their contents. Then solution is more like "Closed, will be handled in different bz" than "Won't Fix" :)
Comment 21Germano Veit Michel
2022-06-03 00:32:49 UTC
Thanks Eduardo. Problem was we got ITR set after my zstream+ , so it was cloned. It wasn't what I wanted but it worked.
Klass, should be clearer to viewers now.
*** This bug has been marked as a duplicate of bug 2083465 ***
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 (WALinuxAgent bug fix and enhancement 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/RHBA-2022:7576