The intent was not to change LTS behavior, so yes, we will modify the
behavior accordingly.

Can you help me understand your use case so we know what needs to
change? Previous to this LXD Datasource, we expected LXD containers to
be identified to cloud-init using the NoCloud datasource. It sounds like
in your case, they're identifying as a different datasource. You mention
Openstack but also an EC2-compatible metadata. Do you know which
datasource is being identified and how this is being accomplished?

I looked at the attached logs, and I currently only see logs from a
machine that identified the LXD datasource. Is there a possibility of
obtaining cloud-init logs from a machine that hasn't been upgraded and
doesn't identify the LXD datasource? To do so, run "cloud-init collect-
logs" and upload the resulting tarball to this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959118

Title:
  LTS upgrade to v21 breaks in LXD containers in OpenStack (nova-
  compute-lxd)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1959118/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to