@Anh Vo,
Thanks for looking at this.
It almost seemed too perfect for me to believe the pre-provisioning
stuff kicked in, and that there were exactly zero journal entries in
almost 9 days.
I would think it'd be nice for cloud-init to clearly state "pre-
provisioned system waited X seconds" or something, but not a big deal.
I guess there are two things that are not perfect here, but I don't really know
how big a deal they are:
a.) I would expect others to be confused by 'uptime' of days on a newly
provisioned machine. (and it feels like 9 days of system-idle is a heavy cost
of optimization for a few seconds of boot time)
b.) I just selected "Ubuntu 18.04" from the "new vm" dialog series. I'd hope
that if there was a new image available those that were in the pre-provisioned
queue would be cleared. Ie, if I ask for "Ubuntu 18.04" today, that isn't
necessarily the same as having done so 9 days earlier.
overall, though, Thanks and this looks like it is working well.
I'll close this issue.
Scott
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880704
Title:
jump in kernel clock during boot on azure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1880704/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
