I'm having difficulties in reproducing the problematic case. I added this to /etc/maas/preseeds/curtin_userdata:
(...) system_upgrade: enabled: True late_commands: (...) Deploying yakkety without -proposed, I don't see any error regarding not finding a datasource, either in the logs, or in the console. Much less at the login screen, which just displays a prompt as usual. Thinking it could have scrolled by too fast, I also deployed elsewhere where I had access to a serial console and could save all the output to a file, but also didn't see such an error there. The console always shows this at the end: (...) [ 87.015604] cloud-init[2751]: Cloud-init v. 0.7.9 running 'modules:final' at Mon, 17 Apr 2017 15:14:24 +0000. Up 74.50 seconds. [ 87.016119] cloud-init[2751]: Cloud-init v. 0.7.9 finished at Mon, 17 Apr 2017 15:14:36 +0000. Datasource DataSourceMAAS [http://10.96.0.10/MAAS/metadata/]. Up 86.09 seconds Ubuntu 16.10 albany ttyS1 albany login: Am I missing some condition to trigger the error? Could it be related to the MAAS version somehow? I tried with 2.1.5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1677710 Title: ds-identify does not find maas datasource To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1677710/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
