Upgrade from 1.19.3 to 1.19.4 cannot set machineaddress
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
1.20 |
Fix Released
|
Critical
|
Andrew Wilkins |
Bug Description
I have a Juju environment on 1.19.3 which I just tried upgrading to 1.19.4.
The environment is on Precise, backed by MAAS provider. I have a series of Juju machines deployed as LXC containers on machine 0.
machines:
"0":
agent-state: started
agent-version: 1.19.3
dns-name: curie.beretstack
instance-id: /MAAS/api/
series: trusty
containers:
0/lxc/0:
dns-name: 10.1.7.251
series: precise
hardware: arch=amd64
0/lxc/1:
dns-name: 10.1.7.252
series: precise
hardware: arch=amd64
0/lxc/2:
dns-name: 10.1.7.253
series: precise
hardware: arch=amd64
0/lxc/3:
dns-name: 10.1.7.254
series: precise
hardware: arch=amd64
0/lxc/4:
dns-name: 10.1.7.255
series: precise
hardware: arch=amd64
0/lxc/5:
dns-name: 10.1.8.0
series: precise
hardware: arch=amd64
state-
I upgraded using (on a Trusty machine) "juju upgrade-juju" which displayed 1.19.4 as the best version, and then looking in debug-log I saw many hundreds of messages along the lines of:
machine-0-lxc-4: 2014-06-26 17:49:22 ERROR juju.worker runner.go:218 exited "machiner": cannot set machine addresses of machine 0/lxc/4: cannot set machineaddresses for machine 0/lxc/4: state changing too quickly; try again soon
and
machine-0: 2014-06-26 17:49:04 ERROR juju.worker.
too quickly; try again soon
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Wilkins (axwalk) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Triaged |
assignee: | Andrew Wilkins (axwalk) → nobody |
milestone: | 1.20.0 → 1.21-alpha1 |
Changed in juju-core: | |
status: | Triaged → Fix Committed |
assignee: | nobody → Andrew Wilkins (axwalk) |
tags: | added: regression |
tags: | added: landscape |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
This bug may be a duplicate of bug 1334273 which describes upgrade issues on precise local lxc. The common factors in both bugs are precise and lxc and upgrade-juju