oauthlib code does not adjust timestamp

Bug #1427939 reported by Scott Moser on 2015-03-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
High
Unassigned
cloud-init (Ubuntu)
High
Unassigned

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.

Related branches

Scott Moser (smoser) on 2015-03-04
Changed in cloud-init (Ubuntu):
status: New → Confirmed
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → High
Changed in cloud-init (Ubuntu):
importance: Undecided → High
Scott Moser (smoser) wrote :

Just for clarity, here is the change that did the python3 / oauthlib code for maas datasource;
 http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/1054#cloudinit/sources/DataSourceMAAS.py
As it is right now, oauth_headers is just ignoring timestamp entirely.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-init - 0.7.7~bzr1078-0ubuntu1

---------------
cloud-init (0.7.7~bzr1078-0ubuntu1) vivid; urgency=medium

  * New upstream snapshot.
    * run snappy module only on snappy (LP: #1428495)
    * MAAS: adjust timestamp on oauthlib when needed (LP: #1427939)
 -- Scott Moser <email address hidden> Thu, 05 Mar 2015 15:22:53 -0500

Changed in cloud-init (Ubuntu):
status: Confirmed → Fix Released
Scott Moser (smoser) on 2015-03-06
Changed in cloud-init:
status: Confirmed → Fix Committed
Scott Moser (smoser) wrote :

This is fixed in cloud-init 0.7.7

Changed in cloud-init:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers