[Bug 978127] Re: incorrect time on node causes failed oauth
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 incorrect imports (LP: #1070345, LP: #1066115). cloud-init (0.6.3-0ubuntu1.2) precise-proposed; urgency=low * debian/patches/lp-978127-maas-oauth-fix-bad-clock.patch: fix usage of oauth in maas data source if local system has a bad clock (LP: #978127) * debian/cloud-init.preinst: fix bug where user data scripts re-ran on upgrade from 10.04 versions (LP: #1049146) * debian/patches/lp-974509-detect-dns-server-redirection.patch: detect dns server redirection and disable searching dns for a mirror named 'ubuntu-mirror' (LP: #974509) * debian/patches/lp-1018554-shutdown-message-to-console.patch: write a message to the console on system shutdown. (LP: #1018554) * debian/patches/lp-1066115-landscape-install-fix-perms.patch: install landscape package if needed which will ensure proper permissions on config file (LP: #1066115). * debian/patches/lp-1070345-landscape-restart-after-change.patch: restart landscape after modifying config (LP: #1070345) * debian/patches/lp-1073077-zsh-workaround-for-locale_warn.patch: avoid warning when user's shell is zsh (LP: #1073077) * debian/patches/rework-mirror-selection.patch: improve mirror selection by: * allowing region/availability-zone to be part of mirror (LP: #1037727) * making mirror selection arch aware (LP: #1028501) * allow specification of a security mirror (LP: #1006963) -- Scott Moser smo...@ubuntu.com Thu, 13 Dec 2012 12:16:56 -0500 ** Changed in: cloud-init (Ubuntu Precise) Status: Fix Committed = Fix Released -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done ** Tags added: verification-needed -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Tags removed: missing-in-quantal -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** 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 used for authentication with the maas server. If the client +clock differs by more than 5 minutes from the server clock, +authentication will fail, and subsequently enlistment or commisioning +will fail. +This is also a problem after installation of the system as the same +process for authentication is used. + * There is a need to backport this change in order to fully utilize 12.04 +and MAAS. + * The change in cloud-init is essentially this: +If a request for access to the MAAS metadata service returns 401 or +403 (unauthorized), then subsequent re-tries will modify the +timestamp in the OAUTH request so that it matches the server. + + [Test Case] + * To recreate the bug, you first need to get MAAS set up +(http://maas.ubuntu.com/docs), and start a system for enlistment that would +have an invalid clock. To force an invalid clock, do one of: +* boot to a system bios and change the bios clock +* modify the ephemeral image so that the clock is broken during boot. + This can be accomplished by appending the following to + /etc/init/cloud-init.conf inside an ephemeral image. + | pre-start script + | offset=10 minutes ago + | past=$(date -R --date $offset) + | date --set $past + | echo = set date to $past [$offset] = || + | echo = failed to set date to $past [$offset] + | end script +This is actually more complex than that, because the ephemeral images +already have this fix inside of them. So in order to reproduce, you have +to downgrade the version of cloud-init inside the 12.04 ephemeral image +to the version available in the ubuntu archive (0.6.3-0ubuntu1.1) + * After a sufficiently broken system is obtained, boot the system. +If this fix is not present, enlistment or commissioning will fail +to do anything as it will not have access to the metadata. + * Errors will be written to the MAAS server's /var/log/apache/error.log + * When the fix is applied, a single failure will occur, and then cloud-init +will modify future requests. + + [Regression Potential] + * Regression is limited to the MAAS datasource, which is not enabled by +default for cloud-init. Thus, only a user that is using MAAS or otherwise +takes explicit action to enable it will be affected. + + [Other Info] + * This bug has essentially been fixed in maas enlistment and commissioning +environments outside of the SRU process. The ephemeral images downloaded +for MAAS have 12.10's version of cloud-init installed inside them. +This all works reliably. We want to properly SRU the change so that +installed systems will also be resilient to a bad hardware clock. + + === End SRU Information === + + + + === original bug report === In this simple scenario: - a. hardware installed - b. hardware booted and enlisted - c. commissioning - d. install to hardware - e. cloud-init boot + a. hardware installed + b. hardware booted and enlisted + c. commissioning + d. install to hardware + e. cloud-init boot At this point steps 'b' and 'e' do OAUTH to get user-data. If the clock on the system is sufficiently off, then oauth will fail as shown in the attached screenshot. it seems to make sense that 'b' would set the clock. Once the user enlists the systme to MAAS, it seems OK to start changing their hardware settings. There is still a potential for really bad hardware clock that could forget its settings on reboot, or somehow get off between 'b' and 'c'. If we were really interested in fixing that, cloud-init could read a kernel command line parameter pointing to a system that ran an ntp server and just run that very early in boot to set the local date. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
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 commissioning, and it reports commissioning results back. maas-signal is part of maas (/etc/maas/commissioning-user-data). This was fixed in revision 1242 [1]. The behavior that I would expect in 12.04 with broken hardware clocks at this point is for enlistment to work, commissioning to get user-data, but then to failto report home as done. I think for 12.04 I would recommend the modification of the ephemeral image to include the running of 'ntp-date' as described in comment 5. -- [1] http://bazaar.launchpad.net/~maas-maintainers/maas/trunk/revision/1242 -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
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, 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. Here's the problem though. From what I saw, the MAAS server was returning 401 because of the skewed oauth, not 403. I can provide tcpdump captures if desired. -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Branch linked: lp:~smoser/ubuntu/precise/cloud-init/sru -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
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 they don't necessarily know how to set their hardware clock. ** Changed in: maas Status: Fix Released = Triaged ** Changed in: maas Importance: High = Critical ** Changed in: maas Assignee: (unassigned) = Scott Moser (smoser) -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Also affects: maas (Ubuntu) Importance: Undecided Status: New -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** 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 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Branch linked: lp:~smoser/maas/trunk.maas-signal-clockskew -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Changed in: maas Status: In Progress = Fix Committed -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Changed in: maas Status: Fix Committed = Fix Released -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Also affects: cloud-init (Ubuntu Precise) Importance: Undecided Status: New -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** 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 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Branch linked: lp:ubuntu/cloud-init -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Changed in: maas Status: Triaged = Fix Committed -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Changed in: maas Status: Fix Committed = Fix Released -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
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 than 0644 * get host ssh keys to the console (LP: #1055688) * MAAS DataSource adjust timestamp in oauth header to one based on the timestamp in the response of a 403. This accounts for a bad local clock. (LP: #978127) * re-start the salt daemon rather than start to ensure config changes are taken. * allow for python unicode types in yaml that is loaded. * cleanup in how config modules get at users and groups. -- Scott Moser smo...@ubuntu.com Sun, 30 Sep 2012 14:29:04 -0400 ** Changed in: cloud-init (Ubuntu) Status: Triaged = Fix Released -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Changed in: cloud-init Status: In Progress = Fix Released -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** Changed in: lomond Status: Triaged = Fix Released -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
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. ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** 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 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 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
