Upgrade from 1.19.3 to 1.19.4 cannot set machineaddress

[Adam Collard]

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/1.0/nodes/node-2b6ec142-e295-11e3-83e9-782bcb8e566b/
    series: trusty
    containers:
      0/lxc/0:
        agent-state: started
        agent-version: 1.19.3
        dns-name: 10.1.7.251
        instance-id: juju-machine-0-lxc-0
        series: precise
        hardware: arch=amd64
      0/lxc/1:
        agent-state: started
        agent-version: 1.19.3
        dns-name: 10.1.7.252
        instance-id: juju-machine-0-lxc-1
        series: precise
        hardware: arch=amd64
      0/lxc/2:
        agent-state: started
        agent-version: 1.19.3
        dns-name: 10.1.7.253
        instance-id: juju-machine-0-lxc-2
        series: precise
        hardware: arch=amd64
      0/lxc/3:
        agent-state: started
        agent-version: 1.19.3
        dns-name: 10.1.7.254
        instance-id: juju-machine-0-lxc-3
        series: precise
        hardware: arch=amd64
      0/lxc/4:
        agent-state: started
        agent-version: 1.19.3
        dns-name: 10.1.7.255
        instance-id: juju-machine-0-lxc-4
        series: precise
        hardware: arch=amd64
      0/lxc/5:
        agent-state: started
        agent-version: 1.19.3
        dns-name: 10.1.8.0
        instance-id: juju-machine-0-lxc-5
        series: precise
        hardware: arch=amd64
    state-server-member-status: has-vote

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.instanceupdater updater.go:267 cannot set addresses on "0": cannot set addresses of machine 0: cannot set addresses for machine 0: state changing
 too quickly; try again soon

[Curtis Hovey (sinzui)]

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