I've verified this by setting up maas, then:
bzr branch lp:~smoser/+junk/backdoor-image cd backdoor-image img=/var/lib/maas/ephemeral/precise/ephemeral/amd64/20121008/disk.img sudo ./mount-callback-umount --system-resolvconf -v $img -- \ sh -c 'chroot "$1" /bin/sh' -- < ~/bin/modify-image
sudo ./backdoor-image --password=ubuntu $
where modify-image is attached patch.
Then started a machine (kvm) and watched it boot. It successfully enlisted. This is actually normal. Then, accept the node, and boot again
The node successfully commissions, and shows: 2012-12-12 20:36:35,682 - util.py[WARNING]: 'http://10.55.60.142/MAAS/metadata//2012-03-01/meta-data/instance-id' failed [0/120s]: http error [401] 2012-12-12 20:36:35,690 - DataSourceMAAS.py[WARNING]: set oauth clockskew to 602
in the /var/log/cloud-init.log, indicating that the fix was applied.
I've verified this by setting up maas, then:
bzr branch lp:~smoser/+junk/backdoor-image lib/maas/ ephemeral/ precise/ ephemeral/ amd64/20121008/ disk.img callback- umount --system-resolvconf -v $img -- \
cd backdoor-image
img=/var/
sudo ./mount-
sh -c 'chroot "$1" /bin/sh' -- < ~/bin/modify-image
sudo ./backdoor-image --password=ubuntu $
where modify-image is attached patch.
Then started a machine (kvm) and watched it boot. It successfully enlisted. This is actually normal.
Then, accept the node, and boot again
The node successfully commissions, and shows: 10.55.60. 142/MAAS/ metadata/ /2012-03- 01/meta- data/instance- id' failed [0/120s]: http error [401] py[WARNING] : set oauth clockskew to 602
2012-12-12 20:36:35,682 - util.py[WARNING]: 'http://
2012-12-12 20:36:35,690 - DataSourceMAAS.
in the /var/log/ cloud-init. log, indicating that the fix was applied.