document manual_cache_clean better
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Dan Watkins | ||
Hirsute |
Fix Released
|
Medium
|
Dan Watkins |
Bug Description
LP: #1885527 raised (not for the first time) a general failure of cloud-init's
documentation to cover 'manual_
value not referenced at all in readthedocs, but only in
doc/examples/
https:/
The intent (testing is needed) for manual_cache_clean is:
a.) user-data and system config (/etc/cloud/*.cfg) can set
manual_cache_clean to true or false. As always, user-data overrides system
config. vendor-data should also be able to provide the setting.
b.) cloud-init renders /var/lib/
(path_helper.
c.) on boot, both ds-identify and cloud-init will check
and respect existance of /var/lib/
If that file is present, then cloud-init will not make any
attempts to re-discover a metadata service.
So... "unfreeze", if manual_cache_clean was set is just:
rm -Rf /var/lib/
I think it would be good to both test that my intent/
correct, and document it. Also useful might be documenting use case
that makes this necessary which is described in:
https:/
Related bugs:
* bug 1885527: cloud-init regenerating ssh-keys
* bug 1712680: cloud-init re-generates network config every reboot
Changed in cloud-init (Ubuntu): | |
status: | New → Confirmed |
Changed in cloud-init (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → Medium |
description: | updated |
description: | updated |
Changed in cloud-init (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Dan Watkins (oddbloke) |
https:/ /github. com/canonical/ cloud-init/ pull/568