> In one way or another, the CloudStack datasource was explicitly enabled. > You or something explicitly configured this datasource on, and to be run > before the Ec2 datasource, so generally its functioning > as designed.
Well it wasn't explicitly disabled :-) > Additionally, its not a 404 that we get as the error, but a Connection Refused. Weird. I know I got 404 errors at one point. Need to redo my testing when I'm back in the office. > there must be a config file in /etc/cloud/ that enables the CloudStack datasource, and lists it before the ConfigDrive datasource, Yes there is. It seems that the list in Debian is in the wrong order. However, I think the actual ordering should be enforced by cloud-init if it is that crucial and breaks otherwise (as seen in this case). -- 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/1298921 Title: cloud-init should give up on 404 errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1298921/+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
