This is a clone of issue OCPBUGS-20342. The following is the description of the original issue:
—
Description of problem:
As a part of the forbidden node label e2e test, we execute `oc debug` command to set the forbidden labels on the node. The `oc debug` command is expected to fail while applying the forbidden label.
In our testing, we observed that even though the actual command on the node (kubectl label node/<node> <forbidden_label>) expectedly fails, the `oc debug` command does not carry the return code correctly (it will return 0, even though `kubectl label` fails with error).
Version-Release number of selected component (if applicable):
4.14
How reproducible:
flaky
Steps to Reproduce:
1. Run the test at https://gist.github.com/harche/c9143c382cfe94d7836414d5ccc0ba45 2. Observe that sometimes it flakes at https://gist.github.com/harche/c9143c382cfe94d7836414d5ccc0ba45#file-test-go-L39
Actual results:
oc debug return value flakes
Expected results:
oc debug return value should be consistent.
Additional info:
- clones
-
OCPBUGS-20342 Flaky debug pod return code
- Closed
- is blocked by
-
OCPBUGS-20342 Flaky debug pod return code
- Closed
- links to
-
RHBA-2023:6837 OpenShift Container Platform 4.14.z bug fix update