-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.18.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Plain pods scheduling gated in namespaces labeled with kueue.openshift.io/managed=true
Version-Release number of selected component (if applicable):
kueue-operator.v0.1.0
Steps to Reproduce:
1. Deploy kueue-operator 0.1.0 and create a Kueue object with the Pod framework enabled 2. Create resource flavor and clusterQueue objects 3. Create namespace. oc create ns kueue-scale 4. Label namespace. oc label ns kueue-scale kueue.openshift.io/managed=true 5. Create pod and observe workload and pod status
Actual results:
$ oc get workload,pod NAME QUEUE RESERVED IN ADMITTED FINISHED AGE workload.kueue.x-k8s.io/pod-kueue-scale-fde47 kueue-scale cluster-queue True 6m16sNAME READY STATUS RESTARTS AGE pod/kueue-scale 0/1 SchedulingGated 0 6m16s
Expected results:
Pod should start
Additional info:
Objects YAMLs are attached
- relates to
-
OCPBUGS-57959 Cannot create Deployments with no kueue label in managed namespace
-
- Closed
-