Comment 5 for bug 1868077

@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.