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

Reply via email to