[2.5, enhancement] cloud-init reports failures if local mirror is behind what is included in a MAAS image
Bug #1791185 reported by
Mike Pontillo
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
Since MAAS images update so frequently, I often hit intermittent failures due to hash mismatches (because the apt list cached in the image is more recent than the apt list on my local mirror).
I have found two ways to work around this:
(1) Temporarily switch back to the official Ubuntu archive
(2) Add the following snippet to the cloud-config:
bootcmd:
- [ 'sh', '-c', 'rm -rf /var/lib/
It might be nice if a workaround could be incorporated into MAAS, or cloud-init itself.
This problem also affects LXD images when used with a cloud-config that specifies additional apt packages to be installed.
description: | updated |
summary: |
- [2.5] cloud-init reports failures if local mirror is behind MAAS images + [2.5] cloud-init reports failures if local mirror is behind what is + included in a MAAS image |
description: | updated |
summary: |
- [2.5] cloud-init reports failures if local mirror is behind what is - included in a MAAS image + [2.5, enhancement] cloud-init reports failures if local mirror is behind + what is included in a MAAS image |
To post a comment you must log in.
images.maas.io gets its images from cloud-images. ubuntu. com/daily so this effects all cloud-image users, not just MAAS. I think we should have a larger discussion with foundations as to whether the image should include the apt list cache.
Also instead of removing the current apt cache we could force apt-get update to be run on first boot[1]. We need to be careful not to do this in the ephemeral environment as in some situations the ephemeral environment can be used without using apt at all currently.
[1] https:/ /cloudinit. readthedocs. io/en/latest/ topics/ examples. html?highlight= apt#update- apt-database- on-first- boot