@Mohammed,
I was hoping for /var/lib/cloud contents *before* running 'cloud-init clean'.
The other logs look fine.
@Other cloud-init devs,
I'd like someone else to hazard a guess at what went on here.
The general issue is:
* very old cloud-init (0.7.9) booted on azure
* migrated to ec2, still thought it was on azure
* upgraded and it still happened
* cloud-init clean --logs --seed and rm -Rf /var/lib/waagent fixed it.
I don't see in code how the issue shoudl have occurred after upgrade. but two things stick out:
a.) _is_viable_platform will attempt to log an event even if not on azure. maybe that shouldnt happen.
b.) _is_viable_platform will return true even if asset_tag failed, but /var/lib/waagent/ovf-env.xml existed.
@Mohammed,
I was hoping for /var/lib/cloud contents *before* running 'cloud-init clean'.
The other logs look fine.
@Other cloud-init devs,
I'd like someone else to hazard a guess at what went on here.
The general issue is:
* very old cloud-init (0.7.9) booted on azure
* migrated to ec2, still thought it was on azure
* upgraded and it still happened
* cloud-init clean --logs --seed and rm -Rf /var/lib/waagent fixed it.
I don't see in code how the issue shoudl have occurred after upgrade. but two things stick out:
a.) _is_viable_platform will attempt to log an event even if not on azure. maybe that shouldnt happen. waagent/ ovf-env. xml existed.
b.) _is_viable_platform will return true even if asset_tag failed, but /var/lib/
that seems wrong