Comment 10 for bug 1452680

Again I cannot make juju fail. pasteing:
    juju bootstrap
    juju add-machine -n 2
    juju status

I can instrument deployments before the 1.22.1 upgrade to 1.22.3. Everything does upgrade. the env is usable. There is about an extra 1 minute delay until is see everything at 1.22.3

Could a specific charm be changing networking on a machine to prevent an upgrade? If so we have a larger problem than micro-versions of juju.

Starting with 1.21.x+, the rules where agents are downloaded from changed. First the state-server upgrades using the agents found in streams. Once it completes, I tells each machine and unit to upgrade using the cached agent on the state-server. Agents are not downloaded form streams, but from the state server that is assumed every unit can talk to. Each unit can call home, so each unit should be able to download an agent.