changing the release tarrget in puppet_modules.py doesn't actually change the release target if you had previously run the script.

[Robert Starmer]

IfI ran puppet_modules.py, and then decide to change the release target, I need to delete the /etc/apt/sources.list.d/cisco-openstack-mirror_grizzly.list file or I won't change the release target.

This behaviour seems counter-intuitive, and perhaps we should just overwrite the file.

[subconscious (subconscious)]

I saw this behavior before, but wasn't able to replicate it afterward. If it's true, it appears intermittant.

[Chris Ricker (chris-ricker)]

puppet_modules.py is just to bootstrap - the contents of the repo config are actually managed by puppet after that. So you have to edit the manifests to change the release being targeted

(yeah it's ugly. yaml config to the rescue)