Cisco Openstack

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

  1. Series grizzly
  2. Bug #1206201
Bug #1206201 reported by Robert Starmer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cisco Openstack
New
Undecided
Unassigned
Grizzly
New
Undecided
Unassigned

Bug Description

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.

Revision history for this message
subconscious (subconscious) wrote :

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

Revision history for this message
Chris Ricker (chris-ricker) wrote :

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)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.