Maintenance Update does not update #fuel --version

[Michael Petersen]

Fuel --version will let me know which version of Fuel I am using, however after a Maintenance Update it's not letting me know which real version I am on. The expected output would include a MU version so that I can track updates.

# fuel --version
7.0.0

Expected results would show the MU, or at least some information about the current release I'm actually on.

[Javier Diaz Jr (javierdiazcharles)]

I agree. As of now support engineers and customers are left to checking package versions to verify if a particular MU has been applied to an environment.

Perhaps updating the output of #fuel --version as Michael has suggested would help. Updating /etc/fuel/version.yaml as well.

[Dmitry Pyzhov (dpyzhov)]

Moved to 9.0 for permanent fix. We need a fix for 7.0-updates and possibly for 8.0-updates. No changes are required in 8.0 release because it is not a maintenance update.

[Vladimir Kozhukalov (kozhukalov)]

let's introduce /etc/fuel_issue file that is to be provided by fuel-release package,
then we can patch fuelclient so it reads /etc/fuel_issue instead of /etc/fuel_release.
Please avoid changing the format of /etc/fuel_release since the content of this file is used in many places and I'm afraid some of these places will fail to deal with 9.0-mu-*

[Vitaly Sedelnik (vsedelnik)]

That cannot be fixed just by introducing /etc/fuel_issue file. There going to be a feature in 10.0 to determine which MU is applied to master and slave nodes and report version accordingly. We could look at backporting this to older releases too.

I think we should leave this issue as Confirmed for now and retarget to 9.0-updates.

[Vitaly Sedelnik (vsedelnik)]

Raising to Critical for 9.1 as wrong Fuel version is major UX issue.

[Anton Chevychalov (achevychalov)]

There is confusion about version parameters of fuel and fuel2 cli interfaces.

fuel --version return version of that utility (it's just a command line interface to fuel)
fuel --fuel-version return release of all Fuel software.

[root@localhost fuelclient]# fuel2 --version
fuel2 9.0.0

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

[Anton Chevychalov (achevychalov)]

Solution for 9.1:

https://review.fuel-infra.org/#/c/26504/
https://review.fuel-infra.org/#/c/26503/

[Vitaly Sedelnik (vsedelnik)]

Fix Committed for 9.1, the patches are:

https://review.fuel-infra.org/#/c/26503/
https://review.fuel-infra.org/#/c/26536/

[TatyanaGladysheva (tgladysheva)]

Verified on 9.1 snapshot #287.

[Vladimir Kozhukalov (kozhukalov)]

https://bugs.launchpad.net/fuel/+bug/1625099/

[Vitaly Sedelnik (vsedelnik)]

Downgrading to High for 9.x, retargeting to 9.2

[Denis Meltsaykin (dmeltsaykin)]

Won't Fix for 7.0/8.0, since with given nailgun architecture it is impossible to change the version in a maintenance update.

[Denis Meltsaykin (dmeltsaykin)]

Moving to Won't Fix for 9.2 since in 9.2 fuel --fuel-version shows correctly the nailgun's version, and the 'fuel --version' cmd shows only the version of the CLI tool, which is not a problem.