network rendering is not safe for capture -> redeploy

This bug was originally filed in Launchpad as [LP: #1759324](https://bugs.launchpad.net/cloud-init/+bug/1759324)

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = None

date_created = 2018-03-27T16:28:37.937251+00:00

date_fix_committed = None

date_fix_released = None

id = 1759324

importance = medium

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1759324

milestone = None

owner = smoser

owner_name = Scott Moser

private = False

status = confirmed

submitter = smoser

submitter_name = Scott Moser

tags = []

duplicates = []

_Launchpad user **Scott Moser(smoser)** wrote on 2018-03-27T16:28:37.937251+00:00_

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.