Disabling the "Enable the use of an APT and HTTP/HTTPS proxy" setting did not change the outcome on my system. It still failed at the ntp state.
Interestingly, I did the Commissioning with the checkbox on to "Allow SSH access and prevent machine from turning off". When I log onto the host, the host appears to be fully functional, even though MAAS thinks it has failed. Using the cloud-init command, I ran the ntp state of cloud-init: sudo cloud-init -d single --name ntp --frequency once This completed successfully, so the ntp state itself works. It must be an assumed pre-requisite that is missing or broken at the point ntp is called in the standard config stage. I'll look into that. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
