newly created LXD container has apparent corrupt apt hashes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned |
Bug Description
juju 2.4.5 via snap
Offline - air gapped environment
Created a local ubuntu mirror for bionic and xenial
Created a local LXD mirror and juju agents mirror
When deploying LXD containers for openstack cloud from a bundle, all charms fail inside o the LXD containers. We are seeing python error about installing apt packages.
Running apt update inside of the container gives the folowing errors (this is a secure environment and I cannot copy files off, so I had to retype this by hand)
---
Get:10 http://<mirror ip>:<port>/ubuntu bionic-
Err:10 http://<mirror ip>:<port>/ubuntu bionic-
Get:11 http://<mirror ip>:<port>/ubuntu bionic-
Err:11 http://<mirror ip>:>port>/ubuntu bionic-
Fetched 242 kb in 0s (498kb/s)
Reading package lists... Done
E: Failed to fetch http://<mirror ip>:<port>
ackages.xz File has unexpected size (557052 != 571124). Mirror sync in Progress? [IP: <mirror ip> >port>]
Hashes of expected file::
- Filesize:571124 [weak]
- SHA256:<hash>
- SHA1:<hash>
- MD5Sum:>hash>
Release file created at: Thu, 01 Nov 2018 20:25:49 +000
---
Not just bionic-security gives this, but a few others do as well, i just didn't retype the entire thing.
Bare-metal hosts being deployed do not have this issue. We have set the container-
If we run 'rm -rf /var/lib/
So tha tells me the sources.list being passed is good, but something is corrupting the apt cache as the container is being created.
I will be limited in what information I can pull out of this environment, but feel free to ask and I can try.
tags: | added: field-critical |
Changed in juju: | |
milestone: | none → 2.4.7 |
Changed in juju: | |
milestone: | 2.4.7 → 2.4.8 |
Changed in juju: | |
importance: | Critical → Medium |
Changed in juju: | |
milestone: | 2.4.8 → none |
We redeployed the cloud adding the cleaning of /var/lib/apt/lists and apt clean to juju cloud-init postruncmds and charms appear to have no issue upon initial LXD creation and installation.