This bug was fixed in the package cloud-init - 0.6.3-0ubuntu1.3
---
cloud-init (0.6.3-0ubuntu1.3) precise-proposed; urgency=low
* debian/patches/lp-1070345-landscape-restart-after-change.patch,
debian/patches/lp-1066115-landscape-install-fix-perms.patch:
fix missing or incor
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manage notifications
Hello Scott, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
h
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
Hello Scott, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
h
** Description changed:
+ === Begin SRU Information ===
+ [Impact]
+ * For systems that have a broken or incorrectly set hardware clock,
+enlistment and commissioning into MAAS will fail. This is because
+ubuntu's system clock is initially seeded by the hardware clock, and
+OAUTH is
** Tags removed: missing-in-quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
There are 2 pieces to this fix, both of which are fixed in 12.10.
a.) cloud-init portion. This fix is in the latest set of precise "released"
ephemeral images. They include cloud-init from 12.10. It accounts for 401 or
403 return.
b.) "maas-signal" portion. maas-signal is used during commissi
I just encountered this in precise MAAS, on brand new metal nodes which
had dates sometime in 2011. Adding the NTP hack to the ephemeral image
helped get around it. (Thanks for the recipe, Jeff! FYI, a public NTP
server can work just as well, ntp.ubuntu.com in my case.)
Scott Moser: "Basically,
** Branch linked: lp:~smoser/ubuntu/precise/cloud-init/sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manage notifications about this
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manage notifications about
** Changed in: maas
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manage notifications about
** Branch linked: lp:~smoser/maas/trunk.maas-signal-clockskew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manage notifications about th
** Changed in: maas
Status: Triaged => In Progress
** Tags added: missing-in-quantal
** No longer affects: maas (Ubuntu)
** No longer affects: maas (Ubuntu Precise)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manage notificat
This seems to be fixed in cloud-init based on the latest daily ephemeral
image. However, it seems that maas-signal (embedded in etc/maas
/commissioning-user-data) also has the same problem. Bumping this to
Critical, as it means that it is very difficult for highbank users to
deploy at all, since th
** Branch linked: lp:ubuntu/cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manage notifications about this bug go to:
https://b
** Changed in: cloud-init (Ubuntu Precise)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu Precise)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/97812
** Also affects: cloud-init (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To ma
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manage notifications about
** Changed in: maas
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manage notifications about this
** Changed in: lomond
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manage notifications about thi
** Changed in: cloud-init
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To manage notifications a
This bug was fixed in the package cloud-init - 0.7.0~bzr677-0ubuntu1
---
cloud-init (0.7.0~bzr677-0ubuntu1) quantal; urgency=low
* add CloudStack to DataSources listed by dpkg-reconfigure (LP: #1002155)
* New upstream snapshot.
* 0440 permissions on /etc/sudoers.d files rather
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
inco
I just committed a fix to trunk that I believe should address this.
Its based on the suggestion in comment 13.
Basically, if we fail by 403 unauthorized, we set a "skew" (skew =
local_current_time - server_response_time) and future requests will have
the oauth header time adjusted by that skew.
*
26 matches
Mail list logo
