Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3145
** Bug watch added: github.com/canonical/cloud-init/issues #3145 https://github.com/canonical/cloud-init/issues/3145 ** Changed in: cloud-init Status: Confirmed => Expired -- 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/1759324 Title: network rendering is not safe for capture -> redeploy Status in cloud-init: Expired Bug description: This was somewhat known, but raised in merge proposal at https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/342102 At least the sysconfig renderer, and possibly others don't clean up old files that were rendered by cloud-init. This means you may get stale files causing issues in a capture -> redeploy scenario if the user does not take care to clean them. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1759324/+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
