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).
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.
Adding "reviewed-in-sprint" as we are waiting for PR
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.
Adding "reviewed-in-sprint+" as this story is in Sprint 21
Adding "reviewed-in-sprint" as this bug was moved to the next sprint.
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"
As discussed during Sprint planning, this bug is moved to S23. Therefore won't be resolved in S22. Setting flag.
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"
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.
Thanks Prashanth - adding reviewed-in-sprint
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"
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.
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.
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