Change revision to version in heat-manage db_version command
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
New
|
Undecided
|
Unassigned |
Bug Description
https:/
Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/heat" to a launchpad project name. This indicates that the notify_impact config needs tweaks. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.
commit 1a1cf9dcd69f5e9
Author: Sreeram Vancheeswaran <email address hidden>
Date: Tue Sep 8 12:02:17 2015 +0530
Change revision to version in heat-manage db_version command
In the man page for heat-manage db_version command, revision is getting
printed out instead of version. This has been fixed via this commit.
DocImpact Change-Id: I9c89b83eb60011
Closes-Bug: #1489250
Change-Id: I6f15836e9a0604
Changed in openstack-manuals: | |
assignee: | nobody → venkatamahesh (venkatamaheshkotha) |
assignee: | venkatamahesh (venkatamaheshkotha) → nobody |
affects: | openstack-manuals → heat |
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
It seems "heat-manage db_version" is not documented in openstack-manuals.