1. Proposed title of this feature request
Include additional info into must-gather directory
2. What is the nature and description of the request?
Include the version of the oc binary used, and the logs generated by the command into the must-gather directory when running the oc adm must-gather command.
- The version of the oc binary can help to identify if an issue could be caused because the oc version is different than the version of the cluster.
- The logs generated by the oc adm must-gather command will help to identify if some information could not be collected, and also the exact image used (while the image used is currently in the directory name, I think it could be better to use a short directory name, specially for customers running oc on Windows, as the too long directory name can cause issues there).
The version of the oc binary could be included in the oc adm must-gather output [1], and if it's 2 or more minor versions than the running cluster, a warning should be shown.
4. List any affected packages or components.
oc
- causes
-
OCPBUGS-24197 [release-4.14] Add client version in must-gather summary
- Closed
-
OCPBUGS-24199 [release-4.15] Add client version in must-gather summary
- Closed
- is related to
-
WRKLDS-1012 oc adm must-gather: pull gather container logs
- Closed
-
OCPSTRAT-1114 Include the version of the oc binary used, and the logs generated by the command into the must-gather directory
- Closed
- relates to
-
WRKLDS-259 must-gather improvements
- New
-
RFE-1576 Compress must-gather by default
- Under Review
-
OCPBUGS-31628 [OC] Version captured by must-gather into the version file and the oc client binary running on the machine is not the same
- Closed
- links to