yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1915319@xxxxxxxxxxxxxxxxxx>]

[Expired for MAAS because there has been no activity for 60 days.]

** Changed in: maas
       Status: Incomplete => Expired

-- 
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/1915319

Title:
  clock sync via NTP causes commissioning or deployment failures

Status in cloud-init:
  Expired
Status in MAAS:
  Expired

Bug description:
  We have a mixed OS environment under MAAS control. When we release a
  system in MAAS previously running windows, the hardware clock will be
  set to local time (CST) which is just what Windows does natively. When
  we go to recommission the system and then redeploy it with Ubuntu, it
  PXE boots into Ubuntu and then timedatectl will sync with NTP, causing
  the clock to skip ahead 5 hours, which in turn causes cloud-init to
  fail and thus the commissioning or deployment task will fail. Here's
  an example log:

  2021-02-03T14:51:38+00:00 2HQCR33 cloud-init[2249]: 2021-02-03 14:51:38,922 - util.py[WARNING]: Running module apt-configure (<module 'cloudinit.config.cc_apt_configure' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_apt_configure.py'>) failed
  2021-02-03T14:51:38+00:00 2HQCR33 systemd[1]: Stopping Network Time Synchronization...
  2021-02-03T14:51:38+00:00 2HQCR33 systemd[1]: Stopped Network Time Synchronization.
  2021-02-03T14:51:38+00:00 2HQCR33 systemd[1]: Starting Network Time Synchronization...
  2021-02-03T14:51:39+00:00 2HQCR33 systemd[1]: Started Network Time Synchronization.
  2021-02-03T19:51:38+00:00 2HQCR33 systemd-timesyncd[3449]: Synchronized to time server 10.130.1.120:123 (time.simulprod.com).
  2021-02-03T19:51:38+00:00 2HQCR33 systemd[1]: cloud-config.service: Main process exited, code=exited, status=1/FAILURE
  2021-02-03T19:51:38+00:00 2HQCR33 systemd[1]: cloud-config.service: Failed with result 'exit-code'.
  2021-02-03T19:51:38+00:00 2HQCR33 systemd[1]: Failed to start Apply the settings specified in cloud-config.
  2021-02-03T19:51:38+00:00 2HQCR33 systemd[1]: Starting Execute cloud user/final scripts...

  At this moment, MAAS will immediately mark the task as failed, even if
  the later commissioning or deployment steps do continue to run on the
  host.

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