Comment 2 for bug 1980865

Hi George Campbell,

Thank you for taking the time to report this bug! It looks like two bugs:

1. We shouldn't run `systemctl start ubuntu-advantage.service` ever during a `ua auto-attach`
2. `systemctl start ubuntu-advantage.service` should always exit immediately, especially when not on GCP like you mentioned.

We'll be sure to address these in the next version.

A question to help me reproduce this issue: from looking at the code, this is the scenario I'm imagining might cause this:
1. Launch an Ubuntu Pro image from the aws marketplace
2. Make changes to the instance and create a new custom image based on that instance.
3. Launch the new custom image

Is that roughly what you did to trigger this bug?

As a workaround in the mean time, I think masking ubuntu-advantage.service and rebooting will allow everything to continue:

sudo systemctl mask ubuntu-advantage.service

And if you need to run that early on first-boot, I think a cloud-init bootcmd would work: https://cloudinit.readthedocs.io/en/latest/topics/modules.html#bootcmd