juju should run apt-get update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
I am attempting to deploy charms on the local provider on IBM Power systems. The charms are failing to install because the apt-get metadata is stale.
The problem does not appear to be related to the use of proxies.
All the charms on the IBM Power system that call "apt-get install" have failed with this error message:
2014-06-30 21:20:06 INFO install E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
2014-06-30 21:20:06 ERROR juju.worker.uniter uniter.go:482 hook failed: exit status 100
The unit log can be found here: http://
I believe this problem is due to apt-get update not getting called in cloud-init. The cloud image on the system has the date of 05/28/2014 (current date is 07/01/2014).
A colleague was getting this same error message on x86 and the local provider presumably because his cloud image was out of date and no apt-get update was run.
Juju should either run apt-get update or download a new cloud image more frequently.
Please let me know if you need any more information.
tags: | added: proxy |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → next-stable |
summary: |
- juju should run apt-get update when using proxies + juju should run apt-get update |
description: | updated |
tags: | added: charm deploy |
Changed in juju-core: | |
importance: | High → Medium |
milestone: | next-stable → none |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
This problem might be more related to the age of the cloud image and not the proxies as I originally thought. In both cases the age of the cloud image was old. Does Juju maintain the freshness of the image?