Public bug reported:
I'm using MAAS 2.1.1 hosted on 16.04. When I use 16.04 for Commissioning
or Deployment, it always fails due to config-ntp failing. However, when
I use 14.04 for Commissioning and Deployment, both succeed. I'd like to
be able to use 16.04 for Deployment.
I am aware of bug #1628337, and my ephemeral image is using the newly
fixed version of cloud-init and I still have a problem with the ntp
state causing my 16.04 commissioning and deployment actions to fail.
During cloud-init, it appears that the ntp stage tries to call "apt-get
update" twice. The first time succeeds, but the second time fails. I am
not sure what is causing the failure.
The rsyslog contents from the maas server during the attempted commissioning
are in attachment maas_rsyslog_messages.txt
- 10.4.3.3 is the maas server
- apt.example.com is the apt-cache I have (example.com replaces my own domain)
- Starting at line 354 the ntp stage begins. Lines 521-528 is where it fails
and dumps a python traceback.
The host's mass UI event logs from both commissioning and deployment
attempts are in latest_machine_events.txt.
The packages on the 16.04 ephemeral image are listed in attachment
packages_on_16.04_node.txt.
I've attached the cloud-init.log and the associated cloud-init-
output.log.
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "cloud-init.log"
https://bugs.launchpad.net/bugs/1643116/+attachment/4779713/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643116
Title:
16.04 image commissioning/installation failure due to config-ntp
failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1643116/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
