Bug 1722494 - [DOC] [RFE] In documentation, expected command outcome should be noted
Summary: [DOC] [RFE] In documentation, expected command outcome should be noted
Keywords:
Status: NEW
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: Backlog
Assignee: Anjana Suparna Sriram
QA Contact: Manasa
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-20 13:28 UTC by Michael J. Kidd
Modified: 2023-07-25 18:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-2874 0 None None None 2021-12-25 20:30:32 UTC

Description Michael J. Kidd 2019-06-20 13:28:05 UTC
Description of problem:
 - For process and command executions, especially on maintenance type items, our documentation is missing details on the expected state changes in the cluster.

Example:
 - For upgrades, we recommend setting 'noout' flag, but we fail to annotate that the cluster will go into 'HEALTH_WARN' state with any flag set.

Request documentation provide sample statuses that are expected from command executions, especially when the cluster status moves away from 'HEALTH_OK' as a result of the command.

Comment 1 Giridhar Ramaraju 2019-08-05 13:09:08 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 2 Giridhar Ramaraju 2019-08-05 13:10:28 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 3 Giridhar Ramaraju 2019-08-20 06:58:02 UTC
Level setting the severity of this defect to "High" with a bulk update. Pls refine it to a more closure value, as defined by the severity definition in https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity


Note You need to log in before you can comment on or make changes to this bug.