| 2022-01-21 07:35:22 |
sandeep kumar pabboj |
bug |
|
|
added bug |
| 2022-01-21 07:35:22 |
sandeep kumar pabboj |
attachment added |
|
RSOD_error.png https://bugs.launchpad.net/bugs/1958623/+attachment/5556070/+files/RSOD_error.png |
|
| 2022-01-21 07:41:27 |
sandeep kumar pabboj |
attachment added |
|
grub_commissioned.png https://bugs.launchpad.net/dellserver/+bug/1958623/+attachment/5556071/+files/grub_commissioned.png |
|
| 2022-01-21 08:31:24 |
sandeep kumar pabboj |
bug |
|
|
added subscriber Sujith Pandel |
| 2022-01-21 08:32:25 |
Sujith Pandel |
information type |
Private Security |
Private |
|
| 2022-01-21 08:32:44 |
Sujith Pandel |
bug |
|
|
added subscriber Michael Reed |
| 2022-01-25 08:59:36 |
sandeep kumar pabboj |
bug |
|
|
added subscriber Narendra K |
| 2022-02-02 14:55:40 |
Michael Reed |
information type |
Private |
Public |
|
| 2022-02-11 18:28:06 |
Michael Reed |
bug task added |
|
grub2 (Ubuntu) |
|
| 2022-02-11 18:41:47 |
Matthieu Clemenceau |
tags |
|
fr-2047 |
|
| 2022-02-16 16:30:44 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/415681 |
|
| 2022-02-16 16:30:44 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/415682 |
|
| 2022-02-16 21:35:17 |
Michael Reed |
grub2 (Ubuntu): importance |
Undecided |
Medium |
|
| 2022-02-21 21:31:51 |
Launchpad Janitor |
grub2 (Ubuntu): status |
New |
Fix Released |
|
| 2022-02-23 19:17:25 |
Jeff Lane |
nominated for series |
|
Ubuntu Focal |
|
| 2022-02-23 19:17:25 |
Jeff Lane |
bug task added |
|
grub2 (Ubuntu Focal) |
|
| 2022-02-23 19:17:25 |
Jeff Lane |
nominated for series |
|
Ubuntu Bionic |
|
| 2022-02-23 19:17:25 |
Jeff Lane |
bug task added |
|
grub2 (Ubuntu Bionic) |
|
| 2022-02-23 19:28:22 |
Julian Andres Klode |
bug task added |
|
grub2-unsigned (Ubuntu) |
|
| 2022-02-23 19:28:33 |
Julian Andres Klode |
bug task deleted |
grub2 (Ubuntu Bionic) |
|
|
| 2022-02-23 19:29:06 |
Julian Andres Klode |
bug task deleted |
grub2 (Ubuntu Focal) |
|
|
| 2022-02-23 19:29:15 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-02-23 19:29:15 |
Julian Andres Klode |
bug task added |
|
grub2 (Ubuntu Jammy) |
|
| 2022-02-23 19:29:15 |
Julian Andres Klode |
bug task added |
|
grub2-unsigned (Ubuntu Jammy) |
|
| 2022-02-23 19:29:28 |
Julian Andres Klode |
grub2-unsigned (Ubuntu Jammy): status |
New |
Fix Released |
|
| 2022-02-23 19:29:37 |
Julian Andres Klode |
bug task added |
|
grub2-signed (Ubuntu) |
|
| 2022-02-23 19:30:16 |
Julian Andres Klode |
grub2-signed (Ubuntu Jammy): status |
New |
Fix Released |
|
| 2022-03-23 17:53:54 |
Jeff Lane |
tags |
fr-2047 |
fr-2047 servcert-224 |
|
| 2022-03-23 17:57:47 |
Jeff Lane |
tags |
fr-2047 servcert-224 |
fr-2047 servcert-224 servcert-225 |
|
| 2022-03-23 17:59:15 |
Jeff Lane |
tags |
fr-2047 servcert-224 servcert-225 |
fr-2047 servcert-224 servcert-225 servcert-226 |
|
| 2022-03-23 18:05:48 |
Jeff Lane |
tags |
fr-2047 servcert-224 servcert-225 servcert-226 |
fr-2047 servcert-224 servcert-225 servcert-226 servcert-227 |
|
| 2022-03-23 18:27:12 |
Jeff Lane |
tags |
fr-2047 servcert-224 servcert-225 servcert-226 servcert-227 |
fr-2047 servcert-224 servcert-225 servcert-226 servcert-227 servcert-228 |
|
| 2022-03-23 18:27:50 |
Jeff Lane |
tags |
fr-2047 servcert-224 servcert-225 servcert-226 servcert-227 servcert-228 |
fr-2047 |
|
| 2022-03-31 08:32:15 |
Julian Andres Klode |
summary |
encounter RSOD while pxe booting from MaaS server |
encounter general protection fault while pxe booting from MaaS server |
|
| 2022-03-31 08:36:37 |
Julian Andres Klode |
description |
Observing RSOD when ubuntu installed server setup with MaaS application as per below procedure and pointing out different OS images from grub to deploying OS for connected server.
certification-static.canonical.com/docs/MAAS_Advanced_Network_Installation_And_Configuration.pdf)
Steps to reproduce the issue,
1. Have a server with ubuntu OS and MAAS 2.9.2 application installed
2. Make sure remote server is configured with PXE and enlisted into MAAS application.
[In remote server enable PXE boot in the BIOD network settings and also configure uEFI boot mode and PXE boot device in BIOS settings]
4. Go to MAAS server and use curl command to check the current grub configuration for new enlisted server and make sure current grub configuration mapping to the "MAC address of NIC which is pointing to the CentOS image to deploy or to install into remote server which is enlisted into MAAS. [please refer "grub_commission" snapshot for more details]
5. After above check power on the new enlisted server and run the PXE boot via NIC port.
RSOD should be able to triggered at stage of "booting under maas direction.." [please refer "RSOD_error" snapshot for mroe details]
6. In step 4, if groub config for commissioned machine is pointing to ubuntu boot kernel the RSOD wont be triggered. |
[Impact]
grub can cause a general protection fault in EFI by freeing the wrong number of bytes for an address it allocated, causing the machine not to boot.
[Test plan]
TBD
[Where problems could occur]
We could free too little or too much memory if the code is wrong? Basically all this does is change a free() call to use sizeof() instead of a hardcoded value that was used previously to allocate the buffer. Which should lead to the same result as now in the worst case.
[Original bug report]
Observing RSOD when ubuntu installed server setup with MaaS application as per below procedure and pointing out different OS images from grub to deploying OS for connected server.
certification-static.canonical.com/docs/MAAS_Advanced_Network_Installation_And_Configuration.pdf)
Steps to reproduce the issue,
1. Have a server with ubuntu OS and MAAS 2.9.2 application installed
2. Make sure remote server is configured with PXE and enlisted into MAAS application.
[In remote server enable PXE boot in the BIOD network settings and also configure uEFI boot mode and PXE boot device in BIOS settings]
4. Go to MAAS server and use curl command to check the current grub configuration for new enlisted server and make sure current grub configuration mapping to the "MAC address of NIC which is pointing to the CentOS image to deploy or to install into remote server which is enlisted into MAAS. [please refer "grub_commission" snapshot for more details]
5. After above check power on the new enlisted server and run the PXE boot via NIC port.
RSOD should be able to triggered at stage of "booting under maas direction.." [please refer "RSOD_error" snapshot for mroe details]
6. In step 4, if groub config for commissioned machine is pointing to ubuntu boot kernel the RSOD wont be triggered. |
|
| 2022-04-06 13:35:20 |
Sujith Pandel |
description |
[Impact]
grub can cause a general protection fault in EFI by freeing the wrong number of bytes for an address it allocated, causing the machine not to boot.
[Test plan]
TBD
[Where problems could occur]
We could free too little or too much memory if the code is wrong? Basically all this does is change a free() call to use sizeof() instead of a hardcoded value that was used previously to allocate the buffer. Which should lead to the same result as now in the worst case.
[Original bug report]
Observing RSOD when ubuntu installed server setup with MaaS application as per below procedure and pointing out different OS images from grub to deploying OS for connected server.
certification-static.canonical.com/docs/MAAS_Advanced_Network_Installation_And_Configuration.pdf)
Steps to reproduce the issue,
1. Have a server with ubuntu OS and MAAS 2.9.2 application installed
2. Make sure remote server is configured with PXE and enlisted into MAAS application.
[In remote server enable PXE boot in the BIOD network settings and also configure uEFI boot mode and PXE boot device in BIOS settings]
4. Go to MAAS server and use curl command to check the current grub configuration for new enlisted server and make sure current grub configuration mapping to the "MAC address of NIC which is pointing to the CentOS image to deploy or to install into remote server which is enlisted into MAAS. [please refer "grub_commission" snapshot for more details]
5. After above check power on the new enlisted server and run the PXE boot via NIC port.
RSOD should be able to triggered at stage of "booting under maas direction.." [please refer "RSOD_error" snapshot for mroe details]
6. In step 4, if groub config for commissioned machine is pointing to ubuntu boot kernel the RSOD wont be triggered. |
[Impact]
grub can cause a general protection fault in EFI by freeing the wrong number of bytes for an address it allocated, causing the machine not to boot.
[Test plan]
1. Have a Dell 14G server with ubuntu OS and MAAS 2.9.2 application installed. Configure MaaS Deploy Settings to Centos7.
2. Configure another Dell 14G SUT with PXE on boot and enlist it in MAAS.
3. Deploy Centos7 in SUT through MaaS.
4. Power off the system after Centos deployment.
5. Power on the system, SUT goes to MaaS-PXE and we now should be able to boot to installed Centos-7 (Issue is RSOD here).
[Where problems could occur]
We could free too little or too much memory if the code is wrong? Basically all this does is change a free() call to use sizeof() instead of a hardcoded value that was used previously to allocate the buffer. Which should lead to the same result as now in the worst case.
[Original bug report]
Observing RSOD when ubuntu installed server setup with MaaS application as per below procedure and pointing out different OS images from grub to deploying OS for connected server.
certification-static.canonical.com/docs/MAAS_Advanced_Network_Installation_And_Configuration.pdf)
Steps to reproduce the issue,
1. Have a server with ubuntu OS and MAAS 2.9.2 application installed
2. Make sure remote server is configured with PXE and enlisted into MAAS application.
[In remote server enable PXE boot in the BIOD network settings and also configure uEFI boot mode and PXE boot device in BIOS settings]
4. Go to MAAS server and use curl command to check the current grub configuration for new enlisted server and make sure current grub configuration mapping to the "MAC address of NIC which is pointing to the CentOS image to deploy or to install into remote server which is enlisted into MAAS. [please refer "grub_commission" snapshot for more details]
5. After above check power on the new enlisted server and run the PXE boot via NIC port.
RSOD should be able to triggered at stage of "booting under maas direction.." [please refer "RSOD_error" snapshot for mroe details]
6. In step 4, if groub config for commissioned machine is pointing to ubuntu boot kernel the RSOD wont be triggered. |
|
| 2022-09-11 23:54:08 |
Matthieu Clemenceau |
tags |
fr-2047 |
foundations-todo fr-2047 |
|
| 2022-09-11 23:54:21 |
Matthieu Clemenceau |
bug |
|
|
added subscriber Ubuntu Foundations Team |
| 2022-09-15 15:41:13 |
Matthieu Clemenceau |
removed subscriber Ubuntu Foundations Team |
|
|
|
| 2022-09-15 15:41:20 |
Matthieu Clemenceau |
bug |
|
|
added subscriber Ubuntu Foundations Bugs |
| 2022-10-10 14:56:04 |
Julian Andres Klode |
grub2-unsigned (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2022-10-10 14:56:06 |
Julian Andres Klode |
grub2-unsigned (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2022-10-10 14:56:12 |
Julian Andres Klode |
grub2-unsigned (Ubuntu Bionic): status |
New |
Triaged |
|
| 2022-10-10 14:56:14 |
Julian Andres Klode |
grub2-unsigned (Ubuntu Focal): status |
New |
Triaged |
|
| 2023-01-30 17:34:55 |
Launchpad Janitor |
grub2-unsigned (Ubuntu Focal): status |
Triaged |
Fix Released |
|
| 2023-01-30 17:34:55 |
Launchpad Janitor |
cve linked |
|
2022-2601 |
|
| 2023-01-30 17:34:55 |
Launchpad Janitor |
cve linked |
|
2022-3775 |
|
| 2023-01-30 18:39:34 |
Launchpad Janitor |
grub2-unsigned (Ubuntu Bionic): status |
Triaged |
Fix Released |
|
| 2023-06-02 15:25:09 |
Benjamin Drung |
tags |
foundations-todo fr-2047 |
fr-2047 |
|
