-
Bug
-
Resolution: Done-Errata
-
Blocker
-
CNV v4.16.0
-
None
-
5
-
False
-
-
False
-
aaq-operator-rhel9-container-v4.16.0-75
-
---
-
---
-
-
High
-
No
Description of problem:
when AAQ enabled - `oc debug` command does not work (even when no any ARQ in the cluster) # AAQ Enabled: $ oc debug node/virt-den-415-4bfl6-worker-0-74h66 The Pod "virt-den-415-4bfl6-worker-0-74h66-debug" is invalid: spec.nodeName: Forbidden: cannot be set until all schedulingGates have been cleared # No ARQ: $ oc get arq -A No resources found # AAQ Disabled: $ oc debug node/virt-den-415-4bfl6-worker-0-74h66 Starting pod/virt-den-415-4bfl6-worker-0-74h66-debug ... . . sh-4.4#may be some other services affected..
Version-Release number of selected component (if applicable):
4.15
How reproducible:
100%
Steps to Reproduce:
1. enable AAQ on the cluster 2. try to run `oc debug` for node or pods 3.
Actual results:
error message: The Pod "virt-den-415-4bfl6-worker-0-74h66-debug" is invalid: spec.nodeName: Forbidden: cannot be set until all schedulingGates have been cleared
Expected results:
debug is working good
Additional info:
- clones
-
CNV-38699 `oc debug` command does not work when AAQ enabled
- Closed
- duplicates
-
CNV-39100 After enabling AAQ there is an error 'x509: certificate signed by unknown authority' occurs when executing 'oc logs' or 'oc exec' commands
- Closed
-
CNV-39878 After enabling AAQ there is an error 'x509: certificate signed by unknown authority' occurs when executing 'oc logs' or 'oc exec' commands
- Closed
- links to
-
RHEA-2023:122979 OpenShift Virtualization 4.16.0 Images
- mentioned on