refactor supervisor scripts to use explicit fuel version

Bug #1447567 reported by Matthew Mosesohn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
Undecided
Matthew Mosesohn

Bug Description

dockerctl start $container fails when modifying /etc/fuel/version.yaml during upgrade/rollback in certain circumstances. We should install new supervisor config that has the Fuel version hardcoded in.

Changed in fuel:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/176779
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=d3d4e8bcdfc19858c1f5c627b2772251a4b03ea2
Submitter: Jenkins
Branch: master

commit d3d4e8bcdfc19858c1f5c627b2772251a4b03ea2
Author: Matthew Mosesohn <email address hidden>
Date: Thu Apr 23 17:22:09 2015 +0300

    Run docker containers with explicit version

    Supervisor should start containers based on the
    version of Fuel, not specific to dockerctl. This
    will alleviate some issues with container versioning
    during upgrade and rollback of Fuel Master.

    Change-Id: Ia839cc2aa4e584b7b01793a5738f6542b9a07c8e
    Related-Bug: #1446075
    Closes-Bug: #1447567

Changed in fuel:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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