-
Story
-
Resolution: Done
-
Major
-
CNV v4.16.0, CNV v4.17.0, CNV v4.18.0, CNV v4.19.0, CNV v4.20.0
Description of problem:
The storage checkup documentation (https://docs.redhat.com/en/documentation/openshift_container_platform/4.15/html/virtualization/monitoring#virt-checking-storage-configuration_virt-running-cluster-checkups) lacks a documented flow of what to do if the storage checkup fails. To improve usability, we suggest including steps to help users collect the necessary information for failure analysis to share them with engineering: - Document the available skipTearDown modes, and recommend enabling the onfailure mode so resources are retained after a failed checkup for easier debugging. (See https://github.com/kiagnose/kubevirt-storage-checkup/blob/main/README.md#skipteardown-modes). - Add an optional step after “6. Review the results of the checkup …” that explains what to do if the checkup fails. This should include a link to must-gather documentation so users can collect the relevant resources for debugging and investigate the failed resources.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- relates to
-
CNV-44993 Data collection workflow for kubevirt-storage-checkup analysis
-
- Closed
-
- links to
(10 links to)