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:
In Gen2 VM, the 66-azure-storage.rules cannot create /dev/disk/azure/resource and /dev/disk/azure/root softlinks.

Version-Release number of selected components (if applicable):
WALinuxAgent-2.2.46-7.el8.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a Gen2 VM in Azure
2. Run "ll /dev/disk/azure/"

Actual results:
Cannot show "root" "resource" disks

# ll /dev/disk/azure/
total 0
drwxr-xr-x. 2 root root 180 Jul 21 15:30 scsi0

Expected results: 
Can show "root" "resource" disks. Like in Gen1:
# ll /dev/disk/azure/
lrwxrwxrwx. 1 root root  9 Apr 23 18:12 resource -> ../../sdb
lrwxrwxrwx. 1 root root 10 Apr 23 18:12 resource-part1 -> ../../sdb1
lrwxrwxrwx. 1 root root  9 Apr 23 18:12 root -> ../../sda
lrwxrwxrwx. 1 root root 10 Apr 23 18:12 root-part1 -> ../../sda1
lrwxrwxrwx. 1 root root 10 Apr 23 18:12 root-part2 -> ../../sda2
lrwxrwxrwx. 1 root root 10 Apr 23 18:12 root-part3 -> ../../sda3
lrwxrwxrwx. 1 root root 10 Apr 23 18:12 root-part4 -> ../../sda4

Upstream fix: https://github.com/Azure/WALinuxAgent/pull/1954

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-2020:4636