Bug 1987259

Summary:	Optimize code for must-gather
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Rewant <resoni>
Component:	must-gather	Assignee:	Rewant <resoni>
Status:	CLOSED WONTFIX	QA Contact:	Elad <ebenahar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.8	CC:	muagarwa, ocs-bugs, odf-bz-bot, sabose
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-31 17:31:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rewant 2021-07-29 11:00:45 UTC

Description of problem (please be detailed as possible and provide log
snippests):

Optimize code for must-gather. Must-gather has no way of informing about what command failed and retrying the failed commands. It should implement a retry mechanism for the commands that failed and/or update the logs regarding the command that failed.

Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
3

Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 3 Rewant 2021-07-30 07:28:50 UTC

@yaniv I have updated the description.

Comment 5 Mudit Agarwal 2021-10-06 13:11:07 UTC

Rewant, any plans to fix this in 4.9?

Comment 6 Rewant 2021-10-12 08:22:59 UTC

We can move it to 4.10

Comment 7 Mudit Agarwal 2022-01-31 17:31:44 UTC

No plans to fix it as of now.