fuel-dev-tools have hardcoded astute gem version

Bug #1514740 reported by Maciej Kwiek on 2015-11-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Maciej Kwiek

Bug Description

When running astute-rsync, you should be able to specify which version of astute gem you want to build. Otherwise you need to reinstall fuel-dev-tools with hardcoded desirable astute version.

Fix proposed to branch: master
Review: https://review.openstack.org/243488

Changed in fuel:
status: New → In Progress
Dmitry Pyzhov (dpyzhov) on 2015-11-10
tags: added: area-python
Changed in fuel:
milestone: none → 8.0

Reviewed: https://review.openstack.org/243488
Committed: https://git.openstack.org/cgit/openstack/fuel-dev-tools/commit/?id=b4b82ddae49911fb304e96cce1c3bce0e10de36d
Submitter: Jenkins
Branch: master

commit b4b82ddae49911fb304e96cce1c3bce0e10de36d
Author: Maciej Kwiek <email address hidden>
Date: Tue Nov 10 10:38:57 2015 +0100

    Add astute-version argument to astute-rsync

    Astute gem filename needs to match the name on master node in order for
    astute container to run updated code.

    Change-Id: I2ad3e4c7e879c3228db3e76a54b19996bc821455
    Closes-Bug: #1514740

Changed in fuel:
status: In Progress → Fix Committed
tags: added: dev-to-verify
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers