Bug 2012326

Summary:	run dbginfo debugging script as part of must-gather and install gather
Product:	OpenShift Container Platform	Reporter:	Prashanth Sundararaman <psundara>
Component:	Documentation	Assignee:	Silke Niemann <sniemann>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Philip Chan <chanphil>
Severity:	medium	Docs Contact:	Latha S <lmurthy>
Priority:	medium
Version:	4.10	CC:	aos-bugs, danili, erich
Target Milestone:	---
Target Release:	4.10.0
Hardware:	s390x
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-02 12:38:02 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 Prashanth Sundararaman 2021-10-08 20:32:10 UTC

In the OCP docs for installing OCP on IBM Z, in the "Collecting debugging information" section, it asks the user to oc debug into the node to execute the dbginfo script: https://access.redhat.com/documentation/en-us/openshift_container_platform/4.8/html/installing/installing-with-rhel-kvm-on-ibm-z-and-linuxone. This script : https://github.com/ibm-s390-linux/s390-tools/blob/master/scripts/dbginfo.sh is part of the s390-utils rpm package included as part of RHCOS and collects system related information on a Z system.

But the user should not be required to go into the node and run a script. the collection of this information should be made a part of the must-gather and the installer gather (for debugging bootstrap failures through installer).

Comment 1 Dan Li 2021-10-11 14:51:33 UTC

Hi Prashanth, do you think this bug will progress past ON_QA before the end of the current sprint (Oct 16th)? If not, we might want to set the "reviewed-in-sprint" flag.

Comment 3 Dan Li 2021-10-13 14:07:35 UTC

Adding "reviewed-in-sprint" as we are waiting for PR

Comment 4 Dan Li 2021-11-01 13:35:12 UTC

Hi Prashanth, do you think this bug will progress past POST by the end of this sprint (Nov 6th)? If not, I'd like to set the "reviewed-in-sprint" flag.

Comment 5 Dan Li 2021-11-02 11:10:44 UTC

Adding "reviewed-in-sprint+" as this story is in Sprint 21

Comment 6 Dan Li 2021-11-22 21:15:51 UTC

Adding "reviewed-in-sprint" as this bug was moved to the next sprint.

Comment 7 Dan Li 2022-01-04 20:17:09 UTC

Hi Prashanth, do you think this bug will be resolved before the end of this sprint (January 8th)? If not, I'd like to set "reviewed-in-sprint"

Comment 8 Dan Li 2022-01-06 19:36:02 UTC

As discussed during Sprint planning, this bug is moved to S23. Therefore won't be resolved in S22. Setting flag.

Comment 9 Dan Li 2022-01-24 18:11:42 UTC

Hi Prashanth, do you think this bug will be resolved before the end of this sprint (January 29th)? If not, I'd like to set "reviewed-in-sprint"

Comment 10 Prashanth Sundararaman 2022-01-27 15:15:12 UTC

depends on https://bugzilla.redhat.com/show_bug.cgi?id=2039483. we need the dbginfo script added to the s390utils-core package so it can be made available in RHCOS.

Comment 11 Dan Li 2022-01-28 13:22:25 UTC

Thanks Prashanth - adding reviewed-in-sprint

Comment 12 Dan Li 2022-02-14 18:49:41 UTC

Hi Prashanth, seems that BZ 2039483 has closed, do you know if this bug will be resolved before the end of this sprint (Feb 19th) as well? If not, I'd like to set "reviewed-in-sprint"

Comment 13 Prashanth Sundararaman 2022-02-14 19:54:34 UTC

So I had a conversation with Eric Rich and the conclusion was that the debugging info that needs to be collected as part of dbginfo can be done through sos-report. the ability to collect debug info through sos report for zVMs have been added through https://github.com/sosreport/sos/pull/2514 which is available in sosreport version 4.2
This bug now needs to be a docs bug which points the customer to use sosreport instead of dbginfo.

Comment 14 Dan Li 2022-02-16 13:38:14 UTC

Since Comment 13 indicates that this bug is related to documentation, I'm re-assigning this bug to Silke to look further on this bug from the documentation side.

Comment 15 Silke Niemann 2022-03-02 12:38:02 UTC

Setting this to done. I've removed the IBM Z debugging procedure from the 4.10 docs and now link to the SOSREPORT. 

See these two PRs, which are already merged:  

https://github.com/openshift/openshift-docs/pull/41848

https://github.com/openshift/openshift-docs/pull/42430