Bug 1714167

Summary: [Azure][RHEL7][WALA] Cannot find temporary disk device in Gen2 VM
Product: Red Hat Enterprise Linux 7 Reporter: Yuxin Sun <yuxisun>
Component: WALinuxAgentAssignee: Vitaly Kuznetsov <vkuznets>
Status: CLOSED ERRATA QA Contact: Yuxin Sun <yuxisun>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.7CC: danis, esflores, jherrman, mrezanin, mtessun, ofalk, peter.vreman, ribarry, stephen.zarkos, vkuznets, wpinheir, xialiu, yacao, yujiang
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: WALinuxAgent-2.2.38-2.el7_9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1801317 (view as bug list) Environment:
Last Closed: 2020-03-03 13:13:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1794682, 1801317    

Description Yuxin Sun 2019-05-27 09:52:21 UTC
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

Comment 2 Yuxin Sun 2019-05-27 09:56:06 UTC
It's a new feature request and is in discussing in upstream:
https://github.com/Azure/WALinuxAgent/issues/1362

Comment 3 Yuxin Sun 2019-11-18 07:51:35 UTC
This issue is fixed in upstream v2.2.45. Will verify when official release is published.

Comment 20 Dan 2020-02-12 01:43:58 UTC
What is the ETA to get .45 into Z stream for RHEL 7 and 8?

Comment 21 Rick Barry 2020-02-12 21:13:32 UTC
(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.

Comment 23 Dan 2020-02-18 15:39:12 UTC
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

Comment 24 Dan 2020-02-18 15:40:05 UTC
sorry, wrong needing

Comment 25 Rick Barry 2020-02-18 15:42:19 UTC
(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.

Comment 27 Dan 2020-02-18 15:49:56 UTC
Thanks Rick, and rough ETA's?

Comment 28 Rick Barry 2020-02-18 16:33:09 UTC
(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.

Comment 44 errata-xmlrpc 2020-03-03 13:13:27 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, 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

Comment 51 Yuxin Sun 2020-04-23 03:18:32 UTC
*** Bug 1825320 has been marked as a duplicate of this bug. ***