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.

+++ This bug was initially created as a clone of Bug #1972102 +++

This bug was initially created as a copy of Bug #1972101

I am copying this bug because: 
The current version of walinuxagent in the eus/e4s streams is not supported via the azure side of things:
https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-machines/support-extensions-agent-version
https://bugzilla.redhat.com/show_bug.cgi?id=2082801

So this also needs to happen in the supported EUS/E4S Streams, I am using 8.4 for SAP on Azure for example.
The current version in there is 2.2.49.2-3.

--------------------------------------------

WALinuxAgent-2.3.0.2 was released:
https://github.com/Azure/WALinuxAgent/releases/tag/v2.3.0.2

we should consider rebasing to this version.

--- Additional comment from errata-xmlrpc on 2021-11-09 18:50:30 UTC ---

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/RHEA-2021:4305

--- Additional comment from Klaas Demter on 2022-09-16 06:50:52 UTC ---

Hi,
this also needs to happen in the supported EUS/E4S streams

Greetings
Klaas

Hi Eduardo,

Could you please help to check if we can rebase the WALA in EUS/E4S according to the policy? Thanks!

I think the same logic applies here as in https://bugzilla.redhat.com/show_bug.cgi?id=2082801 for RHEL7. This needs to happen in order to be fully supported on Azure.

This BZ was opened against RHEL-8.6 and according to this doc[0], we need support Azure compatibility until May 30, 2025.

So yes we can proceed with the rebase.

[0] https://access.redhat.com/articles/5456301

We can't directly create BZ's for z-stream. Marking this BZ in way we can create z-stream clone and fix the issue properly and than close unused BZs.

@mrezanin you cloned this into three bugs, 8.7,8.6,8.4 -- but I think this should have gone into 8.4 (EUS),8.2 (E4S) and 8.1 (E4S).

(In reply to Klaas Demter from comment #6)
> @mrezanin you cloned this into three bugs, 8.7,8.6,8.4 -- but I
> think this should have gone into 8.4 (EUS),8.2 (E4S) and 8.1 (E4S).

All 3 rebases (8.4, 8.2 and 8.1) are built and testing is going to be started.