Change revision to version in heat-manage db_version command

Bug #1493762 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
New
Undecided
Unassigned

Bug Description

https://review.openstack.org/221198

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 1a1cf9dcd69f5e9c4f2668c63731e9a430d15b85
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: I9c89b83eb60011d34c0b473a11f83bd8833d755e
    Closes-Bug: #1489250

    Change-Id: I6f15836e9a0604d592647363008268437b95b4e6

Tags: heat
Changed in openstack-manuals:
assignee: nobody → venkatamahesh (venkatamaheshkotha)
assignee: venkatamahesh (venkatamaheshkotha) → nobody
Revision history for this message
Atsushi SAKAI (sakaia) wrote :

It seems "heat-manage db_version" is not documented in openstack-manuals.

Lana (loquacity)
affects: openstack-manuals → heat
Rico Lin (rico-lin)
Changed in heat:
milestone: none → no-priority-tag-bugs
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.