Public bug reported:

[Impact]

 * grub-initrd-fallback.service still orders itself after grub-
common.service.

 * grub-common.service was renamed/merged into grub2-common.service, so the
   ordering dependency now points at the wrong unit.

[Test Case]

 * boot a system with the affected grub2-common package installed.

 * observe that grub-initrd-fallback.service references the obsolete
unit:

   $ systemctl cat grub-initrd-fallback.service | grep 'After=grub-
common.service'

 * install the fixed package.

 * observe that grub-initrd-fallback.service is now ordered after
   grub2-common.service:

   $ systemctl cat grub-initrd-fallback.service | grep
'After=grub2-common.service'

 * reboot the system.

 * observe that grub2-common.service and grub-initrd-fallback.service both
   complete successfully, and that grub-initrd-fallback.service runs after
   grub2-common.service.

Check the units order using

$ sudo journalctl -u grub2-common.service -u grub-initrd-
fallback.service -b

the output should be in order, not interleaved, with grub2-common first and then
grub-initrd-fallback.

[Where problems could occur]

 * If grub2-common.service fails or is delayed, grub-initrd-fallback.service 
will
   also be delayed by the intended ordering relationship.

[Other Info]

 * The previous SRU for the original race is LP: #1910815

 * Error messages:
Jun 02 03:47:41 ubuntu-202605-38820 grub-editenv[1846]: /usr/bin/grub-editenv: 
error: invalid environment block.
Jun 02 03:47:41 ubuntu-202605-38820 systemd[1]: grub-initrd-fallback.service: 
Main process exited, code=exited, status=1/FAILURE
Jun 02 03:47:41 ubuntu-202605-38820 systemd[1]: grub-initrd-fallback.service: 
Failed with result 'exit-code'.
Jun 02 03:47:41 ubuntu-202605-38820 systemd[1]: Failed to start 
grub-initrd-fallback.service - GRUB failed boot detection.

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  [Impact]
  
-  * grub-initrd-fallback.service still orders itself after grub-
+  * grub-initrd-fallback.service still orders itself after grub-
  common.service.
  
-  * grub-common.service was renamed/merged into grub2-common.service, so the
-    ordering dependency now points at the wrong unit.
+  * grub-common.service was renamed/merged into grub2-common.service, so the
+    ordering dependency now points at the wrong unit.
  
  [Test Case]
  
-  * boot a system with the affected grub2-common package installed.
+  * boot a system with the affected grub2-common package installed.
  
-  * observe that grub-initrd-fallback.service references the obsolete
+  * observe that grub-initrd-fallback.service references the obsolete
  unit:
  
-    $ systemctl cat grub-initrd-fallback.service | grep 'After=grub-
+    $ systemctl cat grub-initrd-fallback.service | grep 'After=grub-
  common.service'
  
-  * install the fixed package.
+  * install the fixed package.
  
-  * observe that grub-initrd-fallback.service is now ordered after
-    grub2-common.service:
+  * observe that grub-initrd-fallback.service is now ordered after
+    grub2-common.service:
  
-    $ systemctl cat grub-initrd-fallback.service | grep
+    $ systemctl cat grub-initrd-fallback.service | grep
  'After=grub2-common.service'
  
-  * reboot the system.
+  * reboot the system.
  
-  * observe that grub2-common.service and grub-initrd-fallback.service both
-    complete successfully, and that grub-initrd-fallback.service runs after
-    grub2-common.service.
+  * observe that grub2-common.service and grub-initrd-fallback.service both
+    complete successfully, and that grub-initrd-fallback.service runs after
+    grub2-common.service.
  
  Check the units order using
  
  $ sudo journalctl -u grub2-common.service -u grub-initrd-
  fallback.service -b
  
  the output should be in order, not interleaved, with grub2-common first and 
then
  grub-initrd-fallback.
  
  [Where problems could occur]
  
-  * If grub2-common.service fails or is delayed, grub-initrd-fallback.service 
will
-    also be delayed by the intended ordering relationship.
+  * If grub2-common.service fails or is delayed, grub-initrd-fallback.service 
will
+    also be delayed by the intended ordering relationship.
  
  [Other Info]
  
-  * The previous SRU for the original race is LP: #1910815:
-    https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1910815  
+  * The previous SRU for the original race is LP: #1910815
  
-  * Error messages: 
+  * Error messages:
  Jun 02 03:47:41 ubuntu-202605-38820 grub-editenv[1846]: 
/usr/bin/grub-editenv: error: invalid environment block.
  Jun 02 03:47:41 ubuntu-202605-38820 systemd[1]: grub-initrd-fallback.service: 
Main process exited, code=exited, status=1/FAILURE
  Jun 02 03:47:41 ubuntu-202605-38820 systemd[1]: grub-initrd-fallback.service: 
Failed with result 'exit-code'.
  Jun 02 03:47:41 ubuntu-202605-38820 systemd[1]: Failed to start 
grub-initrd-fallback.service - GRUB failed boot detection.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2156423

Title:
  Fix grub-initrd-fallback.service ordering

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2156423/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to