We have seen this bug quite often on AWS when the customer is using imported VMs. This means that cloud-init was initialized before the image being imported to AWS, therefore, customers get that error when converting to Pro. It has been quite a headache to be honest and while the workaround works, we could have a more reliable way to detect the cloud (or at least throw a better error output).
I was able to reproduce this bug by installing Ubuntu server on virtual box, exporting the image in OVM format, importing it with vmimport and then, upgrading to Pro using AWS License manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067059 Title: Auto-attach image support is not available on none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2067059/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
