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
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
