yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

Public bug reported:

in the python3 port, we moved from python-oauth to python-oauthlib.
That change lost the functionality added to solve bug 978127 (http://pad.lv/978127).

We really need to have this in order to do oauth from systems that do
not have a clock that retains time across reboots.

** Affects: cloud-init
     Importance: High
         Status: Confirmed

** Affects: cloud-init (Ubuntu)
     Importance: High
         Status: Confirmed

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu)
       Status: New => Confirmed

** Changed in: cloud-init
       Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => High

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1427939

Title:
  oauthlib code does not adjust timestamp

Status in Init scripts for use on cloud images:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed

Bug description:
  in the python3 port, we moved from python-oauth to python-oauthlib.
  That change lost the functionality added to solve bug 978127 (http://pad.lv/978127).

  We really need to have this in order to do oauth from systems that do
  not have a clock that retains time across reboots.

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