fuel release don't updated after updating master node

Bug #1621858 reported by Artem Hrechanychenko
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Vitaly Sedelnik

Bug Description

Detailed bug description:
after performing updating master node from 9.0 to 9.1

[root@nailgun ~]# fuel2 fuel-version
api: '1'
auth_required: true
feature_groups: []
openstack_version: mitaka-9.0
release: '9.0'

Steps to reproduce:
1) Deploy any 9.0 env
2) add latest snapshot of mos/centos repo
3) install python-cudet package
4) add latest proposed mos ubuntu repo for cluster
5) deploy new repo to cluster
6) run "update-prepare prepare master, update-prepare prepare env env_id, update-prepare update master"
7) run "fuel2 updates --env env_id --repos test-proposed --restart-rabbit --restart-mysql install
8) check fuel version

Expected results:
version changed from 9.0 to 9.1

Actual result:
release: '9.0'

Tags: area-python
Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
Changed in fuel:
status: New → Confirmed
tags: added: area-python
Revision history for this message
Dmitry Guryanov (dguryanov) wrote :

Fuel version is being taken from /etc/fuel_release, not from /usr/lib/python2.7/site-packages/nailgun/settings.yaml

Changed in fuel:
importance: Medium → High
assignee: Fuel Sustaining (fuel-sustaining-team) → Vitaly Sedelnik (vsedelnik)
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.