-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.20.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-61543. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-61492. The following is the description of the original issue:
—
Description of problem:
managementState to Unmanaged of jobsetoperator/cluster, then edit deployment.apps/jobset-controller-manager replicas to other value, it doesn't take effect，
Version-Release number of selected component (if applicable):
v4.20
How reproducible:
Always
Steps to Reproduce:
1.Set managementState to Unmanaged
{code:java}
spec:
logLevel: Normal
managementState: Unmanaged
operatorLogLevel: Normal
2.Update controller-manager deployment replicas to 3
spec:
progressDeadlineSeconds: 600
replicas: 3
revisionHistoryLimit: 10
selector:
matchLabels:
control-plane: controller-manager
3. Check controller-manager pods, it does not changed.
# oc get pods -n openshift-jobset-operator
NAME READY STATUS RESTARTS AGE
jobset-controller-manager-b877cffb9-qnrsx 1/1 Running 0 54m
Actual results:{code:none}
Pods is still 1
Expected results:
Pods should be 3
Additional info:
lws operator has the same issue.
- clones
-
-
- Verified
-
- is blocked by
-
-
- Verified
-
- links to