Public bug reported: When IBMCloud deploys from a template, artifacts from the provisioning stage are normally cleaned up. Cloud-init relied' on that behavior to determine the provisioning boot from the subsequent post-provisioning boot.
However, when testing, the provisioning stage will leave artifacts in place (/root/provisioningConfiguration.cfg). This caused cloud-init to permenantly believe that it was in the provisioning stage. ** Affects: cloud-init Importance: Medium Status: Confirmed ** Affects: cloud-init (Ubuntu) Importance: Medium Status: Confirmed ** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1767166 Title: IBMCloud datasource does not recognize provisioning in debug mode. Status in cloud-init: Confirmed Status in cloud-init package in Ubuntu: Confirmed Bug description: When IBMCloud deploys from a template, artifacts from the provisioning stage are normally cleaned up. Cloud-init relied' on that behavior to determine the provisioning boot from the subsequent post-provisioning boot. However, when testing, the provisioning stage will leave artifacts in place (/root/provisioningConfiguration.cfg). This caused cloud-init to permenantly believe that it was in the provisioning stage. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1767166/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp