Comment 9 for bug 1452680

I cannot reproduce this with by pasting these command to start deploys before upgrades start:
    juju bootstrap
    juju deploy -n 2 ubuntu
    juju status

I do see the state-server are 1.22.1. I see the other machines and units come up. I see them all upgrade to 1.22.3. the env is usable. In a second try, I saw the second ubuntu machine and unit in pending and allocating then arrive a 1.22.3. I never saw it as 1.22.1. The env was usable.

This is interesting from IRC:
sparkiegeek> sinzui: looking at the log a bit closer it looks like it falls over when add-machine'ing

I will try
    juju bootstrap
    juju add-machine -n 2
    juju status