Comment 3 for bug 1403200

Here are the steps that were taken to setup the environment.
The dummy-source and dummy-sink charms are charms we use with our tests.
This was done using KVM guests running a MaaS.

juju --show-log bootstrap -e my_maas
export JUJU_REPOSITORY=/home/jog/src/juju-ci-tools_repository/
======= Machine-1 not seen in the logs because a precise charm was tried and removed ========
juju --show-log deploy -e my_maas local:precise/dummy-source
juju --show-log remove-service -e my_maas dummy-source
juju --show-log remove-machine -e my_maas --force 1
==============================================================================
juju --show-log deploy -e my_maas local:trusty/dummy-source
juju --show-log deploy -e my_maas local:trusty/dummy-sink
juju --show-log status -e my_maas
juju --show-log add-relation -e my_maas dummy-source dummy-sink
juju --show-log expose -e my_maas dummy-sink
mkdir -p /home/jog/tmp/2178/extracted
cd /home/jog/tmp/2178
wget http://juju-ci.vapour.ws:8080/view/Release,%20package,%20publish/job/publish-revision/1296/artifact/juju-core_1.21-beta4-0ubuntu1%7E14.04.1%7Ejuju1_amd64.deb
dpkg -x juju-core_1.21-beta4-0ubuntu1~14.04.1~juju1_amd64.deb extracted
/home/jog/tmp/2178/extracted/usr/lib/juju-1.21-beta4/bin/juju --show-log upgrade-juju -e my_maas --upload-tools --version 1.21-beta4