| 2023-12-14 18:46:28 |
Alberto Contreras |
bug |
|
|
added bug |
| 2023-12-14 18:47:02 |
Alberto Contreras |
nominated for series |
|
Ubuntu Focal |
|
| 2023-12-14 18:47:02 |
Alberto Contreras |
bug task added |
|
cloud-init (Ubuntu Focal) |
|
| 2023-12-14 18:47:02 |
Alberto Contreras |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-12-14 18:47:02 |
Alberto Contreras |
bug task added |
|
cloud-init (Ubuntu Jammy) |
|
| 2023-12-14 18:47:02 |
Alberto Contreras |
nominated for series |
|
Ubuntu Mantic |
|
| 2023-12-14 18:47:02 |
Alberto Contreras |
bug task added |
|
cloud-init (Ubuntu Mantic) |
|
| 2023-12-14 18:47:02 |
Alberto Contreras |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-12-14 18:47:02 |
Alberto Contreras |
bug task added |
|
cloud-init (Ubuntu Lunar) |
|
| 2023-12-14 20:48:41 |
James Falcon |
description |
`cloud-init status` checks systemctl to ensure the reported status is accurate. However, systemctl can fail if dbus isn't yet ready, and those exceptions are not handled in cloud-init.
For more info, see:
Upstream bug: https://github.com/canonical/cloud-init/issues/4676
Upstream commit: https://github.com/canonical/cloud-init/commit/d29b744e742d12e41e9490fb05e74537b4b768d7 |
=== Begin SRU Template ===
[Impact]
`cloud-init status` checks systemctl to ensure the reported status is accurate. However, systemctl can fail if dbus isn't yet ready, and those exceptions are not handled in cloud-init.
[Test Case]
Note that cloud-init developers have been unable to reproduce the problem. To simulate the issue, create a script that errors anytime "systemctl show" is used, but passes through to the real "systemctl" for any other commands used by cloud-init. Example script (here the real "systemctl" has been renamed to "systemctl2"):
#!/bin/bash
# Check if the first argument is 'show'
if [ "$1" == "show" ]; then
echo "'show' not allowed"
exit 1
fi
/usr/bin/systemctl2 "$@"
Then:
1. Ensure `cloud-init status --wait` exits successfully when cloud-init has finished running with no errors.
2. Edit "/run/cloud-init/status.json". Change the "finished" time of "modules-final" to be "null". Ensure "cloud-init status --wait" blocks while printing dots on the CLI.
3. Edit "/run/cloud-init/status.json". Change the "finished" time of "modules-final" to be "null". Add an arbitrary string to the "errors" list of "modules-final". Ensure "cloud-init status --wait" blocks but does not print dots. Replace the hand-made "systemctl" script with the real systemctl binary. Ensure the "cloud-init status --wait" call made earlier now starts printing dots.
[Regression Potential]
Given that this relates only to the "cloud-init status" command, the regression potential is fairly limited. It's possible a script blocking on "cloud-init status --wait" could exit early or that a "cloud-init status" command will run forever. Either case wouldn't be more than an inconvenience that can be easily worked around.
[Other Info]
Upstream bug: https://github.com/canonical/cloud-init/issues/4676
Upstream commit: https://github.com/canonical/cloud-init/commit/d29b744e742d12e41e9490fb05e74537b4b768d7 |
|
| 2023-12-14 20:50:07 |
James Falcon |
description |
=== Begin SRU Template ===
[Impact]
`cloud-init status` checks systemctl to ensure the reported status is accurate. However, systemctl can fail if dbus isn't yet ready, and those exceptions are not handled in cloud-init.
[Test Case]
Note that cloud-init developers have been unable to reproduce the problem. To simulate the issue, create a script that errors anytime "systemctl show" is used, but passes through to the real "systemctl" for any other commands used by cloud-init. Example script (here the real "systemctl" has been renamed to "systemctl2"):
#!/bin/bash
# Check if the first argument is 'show'
if [ "$1" == "show" ]; then
echo "'show' not allowed"
exit 1
fi
/usr/bin/systemctl2 "$@"
Then:
1. Ensure `cloud-init status --wait` exits successfully when cloud-init has finished running with no errors.
2. Edit "/run/cloud-init/status.json". Change the "finished" time of "modules-final" to be "null". Ensure "cloud-init status --wait" blocks while printing dots on the CLI.
3. Edit "/run/cloud-init/status.json". Change the "finished" time of "modules-final" to be "null". Add an arbitrary string to the "errors" list of "modules-final". Ensure "cloud-init status --wait" blocks but does not print dots. Replace the hand-made "systemctl" script with the real systemctl binary. Ensure the "cloud-init status --wait" call made earlier now starts printing dots.
[Regression Potential]
Given that this relates only to the "cloud-init status" command, the regression potential is fairly limited. It's possible a script blocking on "cloud-init status --wait" could exit early or that a "cloud-init status" command will run forever. Either case wouldn't be more than an inconvenience that can be easily worked around.
[Other Info]
Upstream bug: https://github.com/canonical/cloud-init/issues/4676
Upstream commit: https://github.com/canonical/cloud-init/commit/d29b744e742d12e41e9490fb05e74537b4b768d7 |
=== Begin SRU Template ===
[Impact]
`cloud-init status` checks systemctl to ensure the reported status is accurate. However, systemctl can fail if dbus isn't yet ready, and those exceptions are not handled in cloud-init.
[Test Case]
Note that cloud-init developers have been unable to reproduce the problem. To simulate the issue, create a script that errors anytime "systemctl show" is used, but passes through to the real "systemctl" for any other commands used by cloud-init. Example script (here the real "systemctl" has been renamed to "systemctl2"):
#!/bin/bash
# Check if the first argument is 'show'
if [ "$1" == "show" ]; then
echo "'show' not allowed"
exit 1
fi
/usr/bin/systemctl2 "$@"
Then, with this script being used:
1. Ensure `cloud-init status --wait` exits successfully when cloud-init has finished running with no errors.
2. Edit "/run/cloud-init/status.json". Change the "finished" time of "modules-final" to be "null". Ensure "cloud-init status --wait" blocks while printing dots on the CLI.
3. Edit "/run/cloud-init/status.json". Change the "finished" time of "modules-final" to be "null". Add an arbitrary string to the "errors" list of "modules-final". Ensure "cloud-init status --wait" blocks but does not print dots. Replace the hand-made "systemctl" script with the real systemctl binary. Ensure the "cloud-init status --wait" call made earlier now starts printing dots.
[Regression Potential]
Given that this relates only to the "cloud-init status" command, the regression potential is fairly limited. It's possible a script blocking on "cloud-init status --wait" could exit early or that a "cloud-init status" command will run forever. Either case wouldn't be more than an inconvenience that can be easily worked around.
[Other Info]
Upstream bug: https://github.com/canonical/cloud-init/issues/4676
Upstream commit: https://github.com/canonical/cloud-init/commit/d29b744e742d12e41e9490fb05e74537b4b768d7 |
|
| 2024-01-25 10:37:00 |
Alberto Contreras |
cloud-init (Ubuntu Lunar): status |
New |
Won't Fix |
|
| 2024-01-25 10:37:19 |
Alberto Contreras |
cloud-init (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2024-01-25 10:37:23 |
Alberto Contreras |
cloud-init (Ubuntu Focal): status |
New |
In Progress |
|
| 2024-01-25 10:37:25 |
Alberto Contreras |
cloud-init (Ubuntu Jammy): status |
New |
In Progress |
|
| 2024-01-25 10:37:28 |
Alberto Contreras |
cloud-init (Ubuntu Mantic): status |
New |
In Progress |
|
| 2024-02-02 20:27:38 |
Chad Smith |
tags |
|
regression-proposed |
|
| 2024-02-02 21:02:31 |
Chad Smith |
cloud-init (Ubuntu): status |
Fix Released |
Triaged |
|
| 2024-02-02 21:03:02 |
Chad Smith |
nominated for series |
|
Ubuntu Noble |
|
| 2024-02-02 21:03:02 |
Chad Smith |
bug task added |
|
cloud-init (Ubuntu Noble) |
|
| 2024-02-03 01:39:34 |
Launchpad Janitor |
cloud-init (Ubuntu Noble): status |
Triaged |
Fix Released |
|
| 2024-02-07 14:25:40 |
Alberto Contreras |
tags |
regression-proposed |
regression-proposed verification-failed-jammy verification-failed-mantic verification-needed-focal |
|
| 2024-02-07 14:26:03 |
Alberto Contreras |
tags |
regression-proposed verification-failed-jammy verification-failed-mantic verification-needed-focal |
regression-proposed verification-failed-focal verification-failed-jammy verification-failed-mantic |
|
| 2024-02-08 19:23:04 |
Andreas Hasenack |
cloud-init (Ubuntu Mantic): status |
In Progress |
Fix Committed |
|
| 2024-02-08 19:23:06 |
Andreas Hasenack |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-02-08 19:23:18 |
Andreas Hasenack |
bug |
|
|
added subscriber SRU Verification |
| 2024-02-08 19:23:21 |
Andreas Hasenack |
tags |
regression-proposed verification-failed-focal verification-failed-jammy verification-failed-mantic |
regression-proposed verification-failed-focal verification-failed-jammy verification-needed verification-needed-mantic |
|
| 2024-02-08 19:24:15 |
Andreas Hasenack |
cloud-init (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2024-02-08 19:24:20 |
Andreas Hasenack |
tags |
regression-proposed verification-failed-focal verification-failed-jammy verification-needed verification-needed-mantic |
regression-proposed verification-failed-focal verification-needed verification-needed-jammy verification-needed-mantic |
|
| 2024-02-08 19:25:10 |
Andreas Hasenack |
cloud-init (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2024-02-08 19:25:15 |
Andreas Hasenack |
tags |
regression-proposed verification-failed-focal verification-needed verification-needed-jammy verification-needed-mantic |
regression-proposed verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic |
|
| 2024-02-09 14:38:09 |
Alberto Contreras |
attachment added |
|
lp2046483-23.4.3-verification.tar.xz https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2046483/+attachment/5745449/+files/lp2046483-23.4.3-verification.tar.xz |
|
| 2024-02-09 14:38:52 |
Alberto Contreras |
tags |
regression-proposed verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic |
regression-proposed verification-failed-focal verification-failed-jammy verification-failed-mantic |
|
| 2024-02-09 14:50:15 |
Alberto Contreras |
tags |
regression-proposed verification-failed-focal verification-failed-jammy verification-failed-mantic |
regression-proposed verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic |
|
| 2024-02-12 16:38:09 |
Alberto Contreras |
attachment added |
|
lp2046483_.tar.xz https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2046483/+attachment/5745957/+files/lp2046483_.tar.xz |
|
| 2024-02-15 17:53:17 |
James Falcon |
tags |
regression-proposed verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic |
regression-proposed verification-done verification-done-focal verification-done-jammy verification-done-mantic |
|
| 2024-02-22 20:47:38 |
Launchpad Janitor |
cloud-init (Ubuntu Mantic): status |
Fix Committed |
Fix Released |
|
| 2024-02-22 20:47:48 |
Andreas Hasenack |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2024-02-22 20:49:51 |
Launchpad Janitor |
cloud-init (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2024-02-22 20:50:09 |
Launchpad Janitor |
cloud-init (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
