** Description changed: + [Impact] + LXC containers under the MAAS provider never startup + + [Test Case] + configure a maas environment + juju bootstrap + juju add-machine lxc:0 + (machine appears in status output but never starts). + + [Regression Potential] + Restructuring of the way cloud-init data is constructed and the new API call to allow the correct secrets to be retrieved as potentially wide impact. + + [Original Bug Report] Machines are shown as pending and never start. There is an error parsing the config returned from the API call. - ERROR juju.worker environ.go:50 loaded invalid environment configuration: malformed maas-oauth (3 items separated by colons) + ERROR juju.worker environ.go:50 loaded invalid environment configuration: malformed maas-oauth (3 items separated by colons) maas-oauth is listed as a secret. Although I have not fully investigated yet, I believe that this is a regression that was introduced when the provisioner task was moved to the API, and the environment config is also returned over the API. I posit that the secrets are removed from the environment config before returning them over the API. This makes the configuration invalid, so the "wait for a valid config" just hangs, and the provider fails to enter the main loop.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1246556 Title: lxc containers broken with maas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1246556/+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
