fix oauth time skew. actual implementation was returning 401 not 403.

This fixes (tested) bug 978127.  The server was actually returning a 401
not a 403.  As such, the fix here was insufficient.  This will now take
either of those 2 error codes.  I've also tested it by changing the clock
in the cloud-init upstart job with a stanza like below, and verifying
that we do see the problem and then it resolve itself:

  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

LP: #978127

1 files changed, 4 insertions, 0 deletions

diff --git a/ChangeLog b/ChangeLog
index c5dcd418..cbfba6d0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,4 +1,8 @@
 0.7.0:
+ - add a 'exception_cb' argument to 'wait_for_url'.  If provided, this
+   method will be called back with the exception received and the message.
+ - utilize the 'exception_cb' above to modify the oauth timestamp in 
+   DataSourceMAAS requests if a 401 or 403 is received. (LP: #978127)
  - catch signals and exit rather than stack tracing
  - if logging fails, enable a fallback logger by patching the logging module
  - do not 'start networking' in cloud-init-nonet, but add