Bug 2255240
| Summary: | Must gather in 4.15 is not collected in 35 mins | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Petr Balogh <pbalogh> |
| Component: | must-gather | Assignee: | Niraj Yadav <niryadav> |
| Status: | CLOSED ERRATA | QA Contact: | Oded <oviner> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.15 | CC: | kbg, muagarwa, niryadav, odf-bz-bot, oviner, vavuthu, ypadia |
| Target Milestone: | --- | Keywords: | Automation, Regression |
| Target Release: | ODF 4.15.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 4.15.0-112 | Doc Type: | If docs needed, set a value |
| Doc Text: |
.Must gather logs not collected after upgrade
Previously, the `must-gather` tool failed to collect logs after the upgrade as `Collection started <time> was seen twice.
With this fix, the `must-gather` tool was updated to run the pre-install script only once. As a result, the tool is able to collect the logs successfully after upgrade.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-03-19 15:25:55 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2246375 | ||
|
Description
Petr Balogh
2023-12-19 13:22:26 UTC
I tested mg on ODF4.15 [odf-operator.v4.15.0-98.stable] $ time oc adm must-gather --image=quay.io/rhceph-dev/ocs-must-gather:latest-4.15 .... [must-gather ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-s5j5q deleted Reprinting Cluster State: When opening a support case, bugzilla, or issue please include the following summary data along with any other requested information: ClusterID: fce1583c-d2b1-44a7-9345-ee787616b50b ClusterVersion: Stable at "4.15.0-0.nightly-2023-12-25-100326" ClusterOperators: All healthy and stable real 7m3.801s user 0m1.896s sys 0m0.672s Niraj, Can I test it on "latest-4.15" image? ocs-operator.v4.15.0-100.stable must gather is still failing to collect: 2024-01-03 08:27:57 02:57:56 - ThreadPoolExecutor-5_0 - ocs_ci.ocs.utils - INFO - Must gather image: quay.io/rhceph-dev/ocs-must-gather:latest-4.15 will be used. 2024-01-03 08:27:57 02:57:56 - ThreadPoolExecutor-5_0 - ocs_ci.ocs.utils - INFO - OCS logs will be placed in location /home/jenkins/current-cluster-dir/logs/testcases_1704249707/vavuthuupq1/ocs_must_gather 2024-01-03 08:27:57 02:57:56 - ThreadPoolExecutor-5_0 - ocs_ci.utility.utils - INFO - Executing command: oc --kubeconfig /home/jenkins/current-cluster-dir/openshift-cluster-dir/auth/kubeconfig adm must-gather --image=quay.io/rhceph-dev/ocs-must-gather:latest-4.15 --dest-dir=/home/jenkins/current-cluster-dir/logs/testcases_1704249707/vavuthuupq1/ocs_must_gather 2024-01-03 09:03:04 03:32:56 - ThreadPoolExecutor-5_0 - ocs_ci.ocs.utils - ERROR - Failed during must gather logs! Error: Command '['oc', '--kubeconfig', '/home/jenkins/current-cluster-dir/openshift-cluster-dir/auth/kubeconfig', 'adm', 'must-gather', '--image=quay.io/rhceph-dev/ocs-must-gather:latest-4.15', '--dest-dir=/home/jenkins/current-cluster-dir/logs/testcases_1704249707/vavuthuupq1/ocs_must_gather']' timed out after 2100 secondsMust-Gather Output: job ( upgrade from 4.14 to 4.15 ): https://url.corp.redhat.com/024bded must gather ( not collected ): https://url.corp.redhat.com/54ddfd5 We need not to wait for a cluster or for a job. Don't we have any cluster with the latest 4.15 image installed. This is just must-gather collection which we can simply verify, why to make it so complicated? can you check my test procedure? Do I need to test it after tier1? Test process: 1.upgrade osd 4.14->4.15 $ oc get csv -A NAMESPACE NAME DISPLAY VERSION REPLACES PHASE openshift-operator-lifecycle-manager packageserver Package Server 0.0.1-snapshot Succeeded openshift-storage mcg-operator.v4.15.0-113.stable NooBaa Operator 4.15.0-113.stable mcg-operator.v4.14.4-rhodf Succeeded openshift-storage ocs-operator.v4.15.0-113.stable OpenShift Container Storage 4.15.0-113.stable ocs-operator.v4.14.4-rhodf Succeeded openshift-storage odf-csi-addons-operator.v4.15.0-113.stable CSI Addons 4.15.0-113.stable odf-csi-addons-operator.v4.14.4-rhodf Succeeded openshift-storage odf-operator.v4.15.0-113.stable OpenShift Data Foundation 4.15.0-113.stable odf-operator.v4.14.4-rhodf Succeeded 2.Collect MG $ time oc adm must-gather --image=quay.io/rhceph-dev/ocs-must-gather:latest-4.15 real 3m29.078s user 0m0.819s sys 0m0.373s tier1 is a suite with many tests. So after tier1 suite there is a lot of data on the cluster and that's we can simulate a "customer cluster" I will move this bz to the verified state because this test https://bugzilla.redhat.com/show_bug.cgi?id=2255240#c20 I will try to find a method to create a cluster like a customer. [with a lot of data and operators] Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:1383 |