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.
Description of problem:
WALA cannot find temporary disk device in Gen2 VM
Version-Release number of selected component (if applicable):
WALinuxAgent-2.2.32-1.el7
WALinuxAgent-2.2.40 upstream
How reproducible:
100%
Steps to Reproduce:
1. Create a gen2 VM in Azure(DC2s vm size)
2. Login and check if /dev/sdb1 is mounted
Actual results:
/dev/sdb1 is not mounted
# cat /var/log/waagent.log
ERROR Daemon Failed to mount resource disk [ResourceDiskError] unable to detect disk topology
Expected results:
Can mount /dev/sdb1 to /mnt/resources
Additional info:
In Gen2 VM the /dev/sdb device_id is different from Gen1, and WALA cannot find it.
Gen2: # udevadm info /dev/sdb
P: /devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0004:00/VMBUS:00/f8b3781a-1e82-4818-a1c3-63d806ec15bb/host0/target0:0:0/0:0:0:1/block/sdb
Gen1: # udevadm info /dev/sdb
P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/00000000-0001-8899-0000-000000000000/host3/target3:0:1/3:0:1:0/block/sdb
(In reply to Dan from comment #20)
> What is the ETA to get .45 into Z stream for RHEL 7 and 8?> What is the ETA to get .45 into Z stream for RHEL 7 and 8?
For the full rebase, we would need to sync delivery of RHEL 7 EXTRAS with a RHEL 8 release, probably RHEL 8.2.1 which GA's around mid-year. We need to do that so customers won't run into upgrade problems going from RHEL 7.9 to RHEL 8.2/8.2.1.
Remember, too, for RHEL 8, there's no EXTRAS channel. The agent is part of RHEL proper. We're not able to deliver full rebases on z-streams, only with major/minor releases. If there are critical bug-fixes, we'll need to back-port them to z-stream.
Thanks Rick, as mentioned in another thread, this is highly visible to customers using Gen2 images, they will be seeing these issues now.
Instead of a rebase, can you cherry pick the fix, and back port it?
https://github.com/Azure/WALinuxAgent/issues/1362
(In reply to Dan from comment #23)
> Thanks Rick, as mentioned in another thread, this is highly visible to
> customers using Gen2 images, they will be seeing these issues now.
>
> Instead of a rebase, can you cherry pick the fix, and back port it?
> https://github.com/Azure/WALinuxAgent/issues/1362
Hi Dan, yes, that's what we plan to do with this BZ. We'll be pushing out an update with just this fix as soon as possible.
(In reply to Dan from comment #27)
> Thanks Rick, and rough ETA's?
No ETA yet. I'm trying to find out if we can deliver the fix asynchronously instead of aligning with a batch update.
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, 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:0674