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.

Bug 1801317

Summary: [Azure][WALA][RHEL8] Cannot find temporary disk device in Gen2 VM
Product: Red Hat Enterprise Linux 8 Reporter: Rick Barry <ribarry>
Component: WALinuxAgentAssignee: Vitaly Kuznetsov <vkuznets>
Status: CLOSED CURRENTRELEASE QA Contact: Yuxin Sun <yuxisun>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: danis, gchakkar, klaas, mrezanin, ofalk, peter.vreman, ribarry, stephen.zarkos, vkuznets, yacao, yujiang, yuxisun
Target Milestone: rcKeywords: Extras, TestOnly
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1714167 Environment:
Last Closed: 2020-11-12 03:24:11 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: 1714167, 1791069    
Bug Blocks: 1794682    

Comment 4 Klaas Weyermann 2020-04-23 07:07:23 UTC
Hi,
is this going to be addressed in RHEL8 anytime soon?
It was fixed in RHEL 7.7 with a patch https://bugzilla.redhat.com/show_bug.cgi?id=1714167
I am not seeing that fix in RHEL 8.1 or RHEL 8.2 Beta

Maybe it's time for another rebase to the version used in RHEL7 extras like done here: https://bugzilla.redhat.com/show_bug.cgi?id=1722848 ?

Or even a switch to a newer WALinuxAgent version like being discussed here: https://bugzilla.redhat.com/show_bug.cgi?id=1794682 ?

Greetings
Klaas

Comment 5 Yaju Cao 2020-04-23 07:42:27 UTC
(In reply to Klaas Demter from comment #4)
> Hi,
> is this going to be addressed in RHEL8 anytime soon?
> It was fixed in RHEL 7.7 with a patch
> https://bugzilla.redhat.com/show_bug.cgi?id=1714167
> I am not seeing that fix in RHEL 8.1 or RHEL 8.2 Beta
> 
> Maybe it's time for another rebase to the version used in RHEL7 extras like
> done here: https://bugzilla.redhat.com/show_bug.cgi?id=1722848 ?
> 
> Or even a switch to a newer WALinuxAgent version like being discussed here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1794682 ?
> 
> Greetings
> Klaas
Hi, 

This is planing to be addressed in next RHEL 8 Application Stream (8.2.1), and its release cycle is about 3 months. And yes it will be fixed by rebasing to a newer WALinuxAgent version.
Not sure if this will meet your requirement.If you need a quick fix, it is best that you talk with our support engineer in your case https://access.redhat.com/support/cases/#/case/02636779, and he can help to raise your request.

Thanks!