@Mohammed, I would do a 'rm -Rf /var/lib/waagent' before migrating future images. And I'd suggest that you can probably just 'touch /var/lib/cloud/instance/warnings/.skip'. But your system is in a wierd state.
@Cloud-init devs, What happened here was: a.) instance booted on Azure b.) instance captured and moved to EC2 c.) new instance on EC2 had: 1. ds-identify recognize that it was on EC2 2. python code path use the old Azure content (seed=/var/lib/waagent). d.) since c.1 and c.2 differed, cloud-init complained. Added to that set of events was that this cloud-init iidentifies itself as 0.7.9. cloud-init version 17.1 (17.1-17-g45d361cb-0ubuntu1_16.04.1) was released to xenial in October of 2017. So this system has not been updated in at least 2 years. I'm not sure if this is bug is still present or not, and I believe that it would not be seen if ds-identify was enabled. But it does seem that in this old version there is discrepency in ds-identify detection of azure and the python path. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868077 Title: A new feature in cloud-init identified possible datasources for this system as:['Ec2', 'None']. However, the datasource used was: Azure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1868077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
