cloud-init 23.3.1 provides invalid param --break-system-package to pip
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Lunar |
Fix Released
|
Undecided
|
Unassigned | ||
Mantic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
In cloud-init 23.3.1, when cloud-config directives specify that ansible is installed via `install_method: pip` cloud-init leaves ansible uninstalled/
This issue was already addressed in upstream commit [1] by only providing the `--break-
[1] upstream fix https:/
[Test Case]
Use the following script:
#!/bin/bash
for RELEASE in focal jammy lunar mantic; do
if [ "$RELEASE" = "focal" -o "$RELEASE" = "jammy" ]; then
echo "Expect integration test FAILURE on $RELEASE with daily images"
# Run current integration tests are expected to fail path against daily images
CLOUD_
else
echo "Expect integration test SUCCESS on $RELEASE with daily images"
# Run current integration tests are expected to fail path against daily images
CLOUD_
fi
echo "Expect integration test SUCCESS on $RELEASE with SRU version cloud-init 23.3.3"
# Run current integration tests with this proposed SRU upload from ppa:cloud-
CLOUD_
done
[Regression Potential]
This is resolving a bug that broke/regressed only environments with have pip version < 23.0.1 and provide the following custom user-data during VM launch:
ansible:
install_method: pip
...
It is a very specific fix for a targeted use-case and will not regress typical deployments using cloud-init
[Other info]
- Community comment filed against upstream PR indicating this problem
https:/
- Original issue filed against integration test failures https:/
Changed in cloud-init (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in cloud-init (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in cloud-init (Ubuntu Focal): | |
status: | New → In Progress |
Changed in cloud-init (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in cloud-init (Ubuntu Lunar): | |
status: | New → In Progress |
Changed in cloud-init (Ubuntu Mantic): | |
status: | New → Fix Committed |
Changed in cloud-init (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in cloud-init (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in cloud-init (Ubuntu Lunar): | |
status: | In Progress → Fix Committed |
This bug is believed to be fixed in Ubuntu Nobel in cloud-init version 23.4~3g0cb0b80f -0ubuntu1 and later.
If it is still a problem on later releases, please feel free to reopen this bug.