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 1993083 - Shim breaks first reboot from console on new builds in Azure 8.4
Summary: Shim breaks first reboot from console on new builds in Azure 8.4
Keywords:
Status: CLOSED DUPLICATE of bug 1970632
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: shim
Version: 8.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: beta
: ---
Assignee: Javier Martinez Canillas
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-12 10:52 UTC by Parikshit Khedekar
Modified: 2021-12-03 08:27 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-20 10:12:39 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-93365 0 None None None 2021-08-12 11:09:07 UTC

Description Parikshit Khedekar 2021-08-12 10:52:12 UTC 
Description of problem:

The VM provisioned for RHEL 8.4 in Azure will fail to do a first reboot if
it's done from Azure portal. Post troubleshooting and checking all the things
as kdump,WaLinuxAgent customer found the shim package is responsible for
this.


How reproducible:

Always post provisioning the VM and rebooting it from portal with a restart
switch/button.


Steps to Reproduce:

[1] Get the Azure Cli and provision a VM as,

$az login
$az account set --subscription <your sub id>
$az group create -l <location (I prefer westus2)> -n <Resource Group name>
$az vm create --name <VM Name> --resource-group <RG Name that is create by above command> --location <westus2> --image "RedHat:RHEL:84-gen2:8.4.2021053102" --size Standard_D2s_v3 --admin-username <username> --admin-password <password>

Secondly, you can go through this link for reference :
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/redhat/redhat-images

[2] Once done Open the Azure portal and click the restart button. The VM will
notify about rebooting but will never come up.

[3] Upon hard - reset or restart as Stop and Start the VM will start and there
after the "restart" will work as expected.

*** The issue occurs only at first reboot done using restart button" ***

Version-Release number of selected component (if applicable):
shim-x64-15.4-2.el8_1.x86_64

Actual results: 

System fails to reboot with nothing printed to console as
suspect, no screenshot as there is no direct console and so far I see it
fails to return the boot status to arm signal sent by the webcode to
hypervisor.

Hard reset boots it up and next "restarts" work fine so shims seems to be
adapting something.

Expected results:
Shall not fail to reboot at first reboot from Portal call.

Additional info:

Customer did check as,

We have 

RHEL 8.4  shim-x64-15.4-2.el8_1.x86_64
RHEL 8.3  shim-x64-15-16.el8.x86_64

So even if we update the 8.3 release with shim-x64-15.4-2.el8_1.x86_64 it will
fail to boot once. So I suspect the arm calls from portal are failing as
while checking this more I have checked journal and can see a kill sent as
normal shutdown.

Limited to Hyper-V env so can't have direct serial console logs and I have
asked to share them, will forword if get available.

Downgrading the shim to shim-x64-15-16.el8.x86_64 on RHEL 8.4 image makes the
issue go away!
Comment 7 Peter Jones 2021-08-17 17:47:56 UTC 
At present I cannot get to a point where I can even try to reproduce this issue.  While we work that out, anyone who *can* reproduce the issue, please:

1) install shim-x64-15-16.el8.x86_64
2) from linux, run "mokutil --set-verbosity true" as root
3) if possible, copy \EFI\redhat to \EFI\test , put the shimx64.efi from shim-x64-15.4-2.el8_1.x86_64 there, and set it up as a second boot entry in the system firmware
4) capture the console log while restarting with this new boot entry selected
Comment 11 Yuxin Sun 2021-08-18 10:49:18 UTC 
(In reply to Peter Jones from comment #7)
> At present I cannot get to a point where I can even try to reproduce this
> issue.  While we work that out, anyone who *can* reproduce the issue, please:
> 
> 1) install shim-x64-15-16.el8.x86_64
> 2) from linux, run "mokutil --set-verbosity true" as root
> 3) if possible, copy \EFI\redhat to \EFI\test , put the shimx64.efi from
> shim-x64-15.4-2.el8_1.x86_64 there, and set it up as a second boot entry in
> the system firmware
> 4) capture the console log while restarting with this new boot entry selected

Hi Peter,

If I run "mokutil --set-verbosity true" and then restart the VM, the VM shows a "Secure Boot not enabled" blue screen, and because Azure only have serial console, it cannot get passed.
Besides, Azure cannot select boot order, so I have to set the new entry as the first boot order.
Comment 12 Renaud Métrich 2021-08-18 11:36:55 UTC 
Hi pjones,
Setting verbosity indeed drops you to a OK prompt, so that's problematic since console is not available.
Would it be possible to provide a shim-x64 package that doesn't show that OK prompt?
Note You need to log in before you can comment on or make changes to this bug.