Fuel 6.1 reports version as string
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Undecided
|
Fuel Python (Deprecated) |
Bug Description
# fuel --fuel-version
api: '1.0'
astute_sha: ed5270bf9c6c123
auth_required: true
build_id: 2015-01-28_22-55-01
build_number: '84'
feature_groups:
- mirantis
fuellib_sha: b2fbaa9ffb74faf
fuelmain_sha: ''
nailgun_sha: 92a85025f0ef9b3
ostf_sha: c9100263140008a
production: docker
python-
release: '6.1'
release_versions:
2014.2-6.1:
VERSION:
api: '1.0'
astute_sha: ed5270bf9c6c123
build_id: 2015-01-28_22-55-01
build_number: '84'
feature_
- mirantis
fuellib_sha: b2fbaa9ffb74faf
fuelmain_sha: ''
nailgun_sha: 92a85025f0ef9b3
ostf_sha: c9100263140008a
production: docker
python-
release: '6.1'
Fuel report his version as string in quotes, and such behavior may break automation scripts.
Also Nailgun API reports ugly build name:
{
"changes": [],
"fuel_version": "6.1",
"grouping": "roles",
"id": 1,
"is_
"mode": "ha_compact",
"name": "Build-'6.1'-84",
"net_provider": "neutron",
"pending_
"release_id": 1,
"status": "operational"
}
Note "Build-'6.1'-84"
Changed in fuel: | |
milestone: | none → 6.1 |
assignee: | nobody → Fuel Python Team (fuel-python) |
status: | New → Triaged |
Changed in fuel: | |
status: | Triaged → Confirmed |
Changed in fuel: | |
status: | Incomplete → Invalid |
Fuel version IS a string. For example, '6.0.1' or '6.1-tp'. Please YAML parsers instead of regexp.
I agree that build name does not look well. Moving bug to the devops team to fix it.