There is misleading cli output in env levels
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Alexander Kislitsky |
Bug Description
There is a problem that hierarchy levels are show in wrong order.
Is shows that servers are first and then nodes.
Actual:
[root@nailgun tuning-box]# fuel2 config env create -l nodes,servers -i 1
+------
| Field | Value |
+------
| hierarchy_levels | [u'servers', u'nodes'] |
| id | 6 |
| components | [1] |
+------
[root@nailgun tuning-box]# fuel2 config override --env 6 --resource 1 --value '{"a": 1, "b": "144override"}' --level nodes=1 --type json --key key
ResourceOverride for key key was set
[root@nailgun tuning-box]# fuel2 config override --env 6 --resource 1 --value '{"a": 1, "b": "144override"}' --level servers=1 --type json --key key
{u'message': u"Unexpected level name 'servers'. Expected 'nodes'
Expected:
Hierarchy levels represent actual hierarchy.
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
milestone: | 9.1 → 9.2 |
tags: | added: on-verification |
We have wrong hierarchy_levels order in environment creation output only. If you execute 'fuel2 config env show -e ENV_ID' hierarchy levels will be in right order.