[Bug 978127] Re: incorrect time on node causes failed oauth

[Scott Moser]

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.

** Attachment added: "modify-ephemeral image script"
   https://bugs.launchpad.net/ubuntu/precise/+source/cloud-init/+bug/978127/+attachment/3458662/+files/modify-image

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/978127

Title:
  incorrect time on node causes failed oauth

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/978127/+subscriptions