| 2021-02-09 06:18:57 |
Stepan |
bug |
|
|
added bug |
| 2021-02-09 06:21:07 |
Stepan |
attachment added |
|
installer.tgz https://bugs.launchpad.net/ubuntu/+bug/1915114/+attachment/5461536/+files/installer.tgz |
|
| 2021-02-09 06:42:16 |
Stepan |
affects |
ubuntu |
ubiquity (Ubuntu) |
|
| 2021-02-09 13:43:25 |
Dimitri John Ledkov |
ubiquity (Ubuntu): status |
New |
Triaged |
|
| 2021-02-09 13:43:27 |
Dimitri John Ledkov |
ubiquity (Ubuntu): importance |
Undecided |
Critical |
|
| 2021-02-09 13:43:34 |
Dimitri John Ledkov |
bug task added |
|
oem-qemu-meta (Ubuntu) |
|
| 2021-02-09 13:43:39 |
Dimitri John Ledkov |
oem-qemu-meta (Ubuntu): status |
New |
Triaged |
|
| 2021-02-09 13:43:42 |
Dimitri John Ledkov |
oem-qemu-meta (Ubuntu): importance |
Undecided |
High |
|
| 2021-02-09 13:48:58 |
Dimitri John Ledkov |
description |
I was installing ubuntu on my fresh new notebook and found that kernel packages wasn't installed. As workaround to run the system I had to chroot into /target to complete installation.
I have one disk and it was partitioned as GPT.
Initialy I thought it was a problem with boot loader but I had installed debian without issue(except it not provide proper firmware).
Then I tried to boot into ubuntu from debian's grub and found that there are no kernels.
It took me 2 days(((
|
[Impact]
* Certain SKUs of laptops; when networking is enabled; complete the installation successfully, without installing any kernel on the system rendering it unbootable.
[Test Case]
* Start install on a relevant SKU
* Enable networking on
* Ensure that after the installation kernel packages are installed in /target
* Reboot to observe that installed
[Where problems could occur]
* Hopefully we will not remove kernels again.... especially the one we want to boot.
[Other Info]
* Original bug report
I was installing ubuntu on my fresh new notebook and found that kernel packages wasn't installed. As workaround to run the system I had to chroot into /target to complete installation.
I have one disk and it was partitioned as GPT.
Initialy I thought it was a problem with boot loader but I had installed debian without issue(except it not provide proper firmware).
Then I tried to boot into ubuntu from debian's grub and found that there are no kernels.
It took me 2 days((( |
|
| 2021-02-09 13:49:46 |
Dimitri John Ledkov |
description |
[Impact]
* Certain SKUs of laptops; when networking is enabled; complete the installation successfully, without installing any kernel on the system rendering it unbootable.
[Test Case]
* Start install on a relevant SKU
* Enable networking on
* Ensure that after the installation kernel packages are installed in /target
* Reboot to observe that installed
[Where problems could occur]
* Hopefully we will not remove kernels again.... especially the one we want to boot.
[Other Info]
* Original bug report
I was installing ubuntu on my fresh new notebook and found that kernel packages wasn't installed. As workaround to run the system I had to chroot into /target to complete installation.
I have one disk and it was partitioned as GPT.
Initialy I thought it was a problem with boot loader but I had installed debian without issue(except it not provide proper firmware).
Then I tried to boot into ubuntu from debian's grub and found that there are no kernels.
It took me 2 days((( |
Ubiquity
[Impact]
* Certain SKUs of laptops; when networking is enabled; complete the installation successfully, without installing any kernel on the system rendering it unbootable.
[Test Case]
* Start install on a relevant SKU
* Enable networking on
* Ensure that after the installation kernel packages are installed in /target
* Reboot to observe that installed
[Where problems could occur]
* Hopefully we will not remove kernels again.... especially the one we want to boot.
[Other Info]
* Original bug report
I was installing ubuntu on my fresh new notebook and found that kernel packages wasn't installed. As workaround to run the system I had to chroot into /target to complete installation.
I have one disk and it was partitioned as GPT.
Initialy I thought it was a problem with boot loader but I had installed debian without issue(except it not provide proper firmware).
Then I tried to boot into ubuntu from debian's grub and found that there are no kernels.
It took me 2 days(((
===
oem-qemu-meta
* To ensure this doesn't happen again, we must update the test oem-qemu-meta package to match the behaviour of the other similar packages in the oem archive. |
|
| 2021-02-09 13:59:58 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-02-09 13:59:58 |
Dimitri John Ledkov |
bug task added |
|
ubiquity (Ubuntu Hirsute) |
|
| 2021-02-09 13:59:58 |
Dimitri John Ledkov |
bug task added |
|
oem-qemu-meta (Ubuntu Hirsute) |
|
| 2021-02-09 13:59:58 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Focal |
|
| 2021-02-09 13:59:58 |
Dimitri John Ledkov |
bug task added |
|
ubiquity (Ubuntu Focal) |
|
| 2021-02-09 13:59:58 |
Dimitri John Ledkov |
bug task added |
|
oem-qemu-meta (Ubuntu Focal) |
|
| 2021-02-09 14:00:10 |
Dimitri John Ledkov |
ubiquity (Ubuntu Focal): importance |
Undecided |
Critical |
|
| 2021-02-09 14:00:12 |
Dimitri John Ledkov |
ubiquity (Ubuntu Focal): status |
New |
In Progress |
|
| 2021-02-09 14:00:14 |
Dimitri John Ledkov |
ubiquity (Ubuntu Hirsute): status |
Triaged |
Fix Committed |
|
| 2021-02-09 14:00:19 |
Dimitri John Ledkov |
oem-qemu-meta (Ubuntu Focal): status |
New |
Confirmed |
|
| 2021-02-09 14:00:23 |
Dimitri John Ledkov |
oem-qemu-meta (Ubuntu Focal): status |
Confirmed |
Triaged |
|
| 2021-02-09 14:00:25 |
Dimitri John Ledkov |
oem-qemu-meta (Ubuntu Focal): importance |
Undecided |
High |
|
| 2021-02-09 14:39:40 |
Łukasz Zemczak |
ubiquity (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2021-02-09 14:39:42 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-02-09 14:39:45 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2021-02-09 14:40:48 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-focal |
|
| 2021-02-09 16:06:07 |
Joshua Peisach |
bug |
|
|
added subscriber Joshua Peisach |
| 2021-02-09 17:08:17 |
Iain Lane |
description |
Ubiquity
[Impact]
* Certain SKUs of laptops; when networking is enabled; complete the installation successfully, without installing any kernel on the system rendering it unbootable.
[Test Case]
* Start install on a relevant SKU
* Enable networking on
* Ensure that after the installation kernel packages are installed in /target
* Reboot to observe that installed
[Where problems could occur]
* Hopefully we will not remove kernels again.... especially the one we want to boot.
[Other Info]
* Original bug report
I was installing ubuntu on my fresh new notebook and found that kernel packages wasn't installed. As workaround to run the system I had to chroot into /target to complete installation.
I have one disk and it was partitioned as GPT.
Initialy I thought it was a problem with boot loader but I had installed debian without issue(except it not provide proper firmware).
Then I tried to boot into ubuntu from debian's grub and found that there are no kernels.
It took me 2 days(((
===
oem-qemu-meta
* To ensure this doesn't happen again, we must update the test oem-qemu-meta package to match the behaviour of the other similar packages in the oem archive. |
[Workaround]
If you install while completely offline (do not connect WiFi, do not plug in network cable) then the bug doesn't happen. You can then connect in the installed system just fine.
[Impact]
* Certain SKUs of laptops; when networking is enabled; complete the installation successfully, without installing any kernel on the system rendering it unbootable.
[Test Case]
* Start install on a relevant SKU
* Enable networking on
* Ensure that after the installation kernel packages are installed in /target
* Reboot to observe that installed
[Where problems could occur]
* Hopefully we will not remove kernels again.... especially the one we want to boot.
[Other Info]
* Original bug report
I was installing ubuntu on my fresh new notebook and found that kernel packages wasn't installed. As workaround to run the system I had to chroot into /target to complete installation.
I have one disk and it was partitioned as GPT.
Initialy I thought it was a problem with boot loader but I had installed debian without issue(except it not provide proper firmware).
Then I tried to boot into ubuntu from debian's grub and found that there are no kernels.
It took me 2 days(((
===
oem-qemu-meta
* To ensure this doesn't happen again, we must update the test oem-qemu-meta package to match the behaviour of the other similar packages in the oem archive. |
|
| 2021-02-09 17:45:36 |
Launchpad Janitor |
ubiquity (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-02-09 23:48:55 |
Dean Henrichsmeyer |
bug |
|
|
added subscriber Dean Henrichsmeyer |
| 2021-02-10 06:56:17 |
Ikuya Awashiro |
bug |
|
|
added subscriber Ikuya Awashiro |
| 2021-02-19 23:08:10 |
Launchpad Janitor |
ubiquity (Ubuntu Hirsute): status |
Fix Committed |
Fix Released |
|
| 2022-01-20 22:41:19 |
Brian Murray |
oem-qemu-meta (Ubuntu Hirsute): status |
Triaged |
Won't Fix |
|
