First Last Prev Next    This bug is not in your last search results.
Bug 1150158 - Grub2 fails to start from HTTPS boot
Grub2 fails to start from HTTPS boot
Status: NEW
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Bootloader
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: Bootloader Maintainers
Jiri Srain
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2019-09-10 11:55 UTC by Guillaume GARDET
Modified: 2022-07-28 12:29 UTC (History)
5 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Serial log from httpS attempt (6.68 KB, text/plain)
2019-09-10 11:55 UTC, Guillaume GARDET 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Guillaume GARDET 2019-09-10 11:55:53 UTC 
Created attachment 817566 [details]
Serial log from httpS attempt

While boot from HTTP in qemu is fine from:
http://openqa.opensuse.org/assets/repo/openSUSE-Tumbleweed-oss-aarch64-Snapshot20190907/EFI/BOOT/bootaa64.efi
See: https://openqa.opensuse.org/tests/1028448

It does not work as expected with HTTPS from the same file downloaded from a secure httpS connection:
https://openqa.opensuse.org/assets/repo/openSUSE-Tumbleweed-oss-aarch64-Snapshot20190907/EFI/BOOT/bootaa64.efi

According to the log, the file is downloaded properly and grub started, but it fails with:
  error: unrecognised network address `openqa.opensuse.org'.
And we end up with the grub prompt.

If I run 'ls proc' on the grub prompt, I get again:
  error: unrecognised network address `openqa.opensuse.org'.
Comment 1 Benjamin Brunner 2022-07-28 12:29:17 UTC 
Bulk-re-assigning to the new bootloader-maintainers@suse.de group.
First Last Prev Next    This bug is not in your last search results.