Bug 2117889

Summary: [IBM Z] test_non_ocs_taint_and_toleration test fails as pods stays in pending state.
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Abdul Kandathil (IBM) <akandath>
Component: odf-operatorAssignee: Nitin Goyal <nigoyal>
Status: CLOSED NOTABUG QA Contact: Martin Bukatovic <mbukatov>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.11CC: ebenahar, jrivera, muagarwa, ocs-bugs, odf-bz-bot
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-29 03:31: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:

Description Abdul Kandathil (IBM) 2022-08-12 12:39:31 UTC
Description of problem (please be detailed as possible and provide log
snippets):

test_non_ocs_taint_and_toleration test fails as pods stays in pending state.

ocs-ci test: tests/manage/z_cluster/nodes/test_non_ocs_taint_and_toleration.py::TestNonOCSTaintAndTolerations::test_non_ocs_taint_and_tolerations


Error:

11:53:55 - MainThread - ocs_ci.ocs.resources.pod - ERROR  - The pod ocs-metrics-exporter-65846777ff-66bnn is in Pending state. Expected = Running
11:54:10 - MainThread - ocs_ci.ocs.resources.pod - ERROR  - The pod ocs-operator-54568ccb48-bkcpn is in Pending state. Expected = Running
11:57:14 - MainThread - ocs_ci.ocs.resources.pod - ERROR  - The pod rook-ceph-operator-bd4c74454-q65lf is in Pending state. Expected = Running
11:58:31 - MainThread - ocs_ci.ocs.resources.pod - ERROR  - The pod rook-ceph-tools-6999b49c9d-tzpv8 is in Pending state. Expected = Running
11:58:31 - MainThread - ocs_ci.ocs.resources.pod - WARNING  - Not all the pods reached status running after 1200 seconds

Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Deploy odf 4.11.0
2. Run ocs-ci test "tests/manage/z_cluster/nodes/test_non_ocs_taint_and_toleration.py::TestNonOCSTaintAndTolerations::test_non_ocs_taint_and_tolerations"



Actual results:

Pods stuck in pending state

Expected results:

Pods in running state.


Additional info:
Logs including must gather log :  https://drive.google.com/file/d/10TpVpGIq8JFuT1GbQiQzzkEmckfsdf-O/view?usp=sharing

Comment 2 Elad 2022-08-15 15:03:11 UTC
Could be due to https://github.com/red-hat-storage/ocs-ci/issues/6330

Comment 3 Mudit Agarwal 2022-10-29 03:31:55 UTC
Not a software issue, please retry after https://github.com/red-hat-storage/ocs-ci/issues/6330 is fixed.