| 2024-04-16 08:57:15 |
Julian Andres Klode |
bug |
|
|
added bug |
| 2024-04-16 08:57:55 |
Julian Andres Klode |
description |
[Impact]
new upstream release; usual dependency updates per Go MIR policy; aligning with snapd 2.62; and support for shim 15.8 per the secboot dependency update.
[Test plan]
* Test suite passes
* Deploy Azure CVM and TPM FDE
* Upgrade to this new package and reboot
* Boot should be successful
* Double check bios_measurements_log to ensure that the newly update shim was used for boot (https://github.com/canonical/tcglog-parser/tree/master/tcglog-dump can be used to extract checksum of the shim binary used at boot and compared to the one shipped in nullboot)
* CPC - build new image with nullboot preinstalled, and attempt to register and boot such an images as first time.
We have set block-proposed to allow testing in noble-proposed to be carried out before migration to noble release pocket.
[Where problems could occur]
Resealing of Azure CVM machines could fail and they would need to be unlocked with a recovery key. |
[Impact]
new upstream release; usual dependency updates per Go MIR policy; aligning with snapd 2.62; and support for shim 15.8 per the secboot dependency update.
Targeted releases:
1. noble
2. jammy; after/when shim 15.8 lands there
3. focal; after/when shim 15.8 lands there
[Test plan]
* Test suite passes
* Deploy Azure CVM and TPM FDE
* Upgrade to this new package and reboot
* Boot should be successful
* Double check bios_measurements_log to ensure that the newly update shim was used for boot (https://github.com/canonical/tcglog-parser/tree/master/tcglog-dump can be used to extract checksum of the shim binary used at boot and compared to the one shipped in nullboot)
* CPC - build new image with nullboot preinstalled, and attempt to register and boot such an images as first time.
We have set block-proposed to allow testing in noble-proposed to be carried out before migration to noble release pocket.
[Where problems could occur]
Resealing of Azure CVM machines could fail and they would need to be unlocked with a recovery key. |
|
| 2024-04-16 08:58:01 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Focal |
|
| 2024-04-16 08:58:01 |
Julian Andres Klode |
bug task added |
|
nullboot (Ubuntu Focal) |
|
| 2024-04-16 08:58:01 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Jammy |
|
| 2024-04-16 08:58:01 |
Julian Andres Klode |
bug task added |
|
nullboot (Ubuntu Jammy) |
|
| 2024-04-16 08:58:01 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Noble |
|
| 2024-04-16 08:58:01 |
Julian Andres Klode |
bug task added |
|
nullboot (Ubuntu Noble) |
|
| 2024-04-16 09:10:44 |
Julian Andres Klode |
nullboot (Ubuntu Noble): status |
New |
Fix Committed |
|
| 2024-04-16 09:11:30 |
Julian Andres Klode |
description |
[Impact]
new upstream release; usual dependency updates per Go MIR policy; aligning with snapd 2.62; and support for shim 15.8 per the secboot dependency update.
Targeted releases:
1. noble
2. jammy; after/when shim 15.8 lands there
3. focal; after/when shim 15.8 lands there
[Test plan]
* Test suite passes
* Deploy Azure CVM and TPM FDE
* Upgrade to this new package and reboot
* Boot should be successful
* Double check bios_measurements_log to ensure that the newly update shim was used for boot (https://github.com/canonical/tcglog-parser/tree/master/tcglog-dump can be used to extract checksum of the shim binary used at boot and compared to the one shipped in nullboot)
* CPC - build new image with nullboot preinstalled, and attempt to register and boot such an images as first time.
We have set block-proposed to allow testing in noble-proposed to be carried out before migration to noble release pocket.
[Where problems could occur]
Resealing of Azure CVM machines could fail and they would need to be unlocked with a recovery key. |
[Impact]
new upstream release; usual vendored dependency updates per Go MIR policy (vendor/ directory is automatically generated by go mod vendor based on go.mod); aligning with snapd 2.62; and support for shim 15.8 per the secboot dependency update.
Targeted releases:
1. noble
2. jammy; after/when shim 15.8 lands there
3. focal; after/when shim 15.8 lands there
[Test plan]
* Test suite passes
* Deploy Azure CVM and TPM FDE
* Upgrade to this new package and reboot
* Boot should be successful
* Double check bios_measurements_log to ensure that the newly update shim was used for boot (https://github.com/canonical/tcglog-parser/tree/master/tcglog-dump can be used to extract checksum of the shim binary used at boot and compared to the one shipped in nullboot)
* CPC - build new image with nullboot preinstalled, and attempt to register and boot such an images as first time.
We have set block-proposed to allow testing in noble-proposed to be carried out before migration to noble release pocket.
[Where problems could occur]
Resealing of Azure CVM machines could fail and they would need to be unlocked with a recovery key. |
|
| 2024-04-16 12:22:50 |
Julian Andres Klode |
tags |
block-proposed |
|
|
| 2024-04-16 13:17:57 |
Launchpad Janitor |
nullboot (Ubuntu Noble): status |
Fix Committed |
Fix Released |
|
| 2024-04-18 17:27:51 |
Julian Andres Klode |
tags |
|
block-proposed |
|
| 2024-04-18 18:54:14 |
Łukasz Zemczak |
nullboot (Ubuntu Noble): status |
Fix Released |
In Progress |
|
| 2024-05-20 20:57:39 |
Jeremy Bícha |
tags |
block-proposed |
jammy noble upgrade-software-version |
|
| 2024-05-20 20:57:58 |
Jeremy Bícha |
tags |
jammy noble upgrade-software-version |
focal jammy noble upgrade-software-version |
|
| 2024-05-20 22:00:19 |
Launchpad Janitor |
nullboot (Ubuntu): status |
In Progress |
Fix Released |
|
