Bug 1395588 - [RFE] Provide Director Command History [NEEDINFO]
Summary: [RFE] Provide Director Command History
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Angus Thomas
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks: 1480409
TreeView+ depends on / blocked
 
Reported: 2016-11-16 09:34 UTC by Tomas Dosek
Modified: 2020-08-24 05:36 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1480409 (view as bug list)
Environment:
Last Closed: 2018-09-24 13:57:26 UTC
Target Upstream Version:
dmatthew: needinfo? (tdosek)

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 521859 0 None MERGED Add each command to the history file 2020-08-24 05:34:40 UTC

Description Tomas Dosek 2016-11-16 09:34:05 UTC 
Understanding the exact order of director deployment commands or the most recent successful or unsuccessful deployment command and its arguments would greatly improve troubleshooting and support. 


To our knowledge there is no way to get a history of command invocations  their arguments and results other than the shell history and logging. Shell history is unreliable method for the commands itself and shell logging would be the only way to get the results.
Comment 2 Jaromir Coufal 2017-08-10 19:44:25 UTC 
It seems there is partial implementation already available: https://review.openstack.org/#/c/446617/

Dan can we make sure we have it in docs?

Follow up implementation seems to be in Workflows (re comment in ^^).
Comment 7 Dougal Matthews 2018-07-23 13:34:57 UTC 
An upstream patch added history for tripleoclient in a previous release. https://review.openstack.org/#/c/521859/

Is that sufficient or do we need a unified history with the actions of the CLI and GUI users?
Note You need to log in before you can comment on or make changes to this bug.