Description of problem: The number of pods did not increase with autoscaler handling. Version-Release number of selected component (if applicable): openshift v3.6.116 kubernetes v1.6.1+5115d708d7 How reproducible: Always Steps to Reproduce: 1. Create a project and DC, expose svc $ oc create -f https://raw.githubusercontent.com/mdshuai/testfile-openshift/master/hpa/dc-hello-hpa.yaml $ oc expose rc hello-hpa-1 --port=8080 2.Go to DC page -> hello-hpa -> Add autoscaler Set Min Pods: 2 Set Max Pods: 10 Set CPU Request Target: 1% Click "Save" Actual results: $oc describe hpa $HPA_NAME ... ... Events: FirstSeen LastSeen Count From SubObjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 44m 25s 88 horizontal-pod-autoscaler Warning FailedGetScale User "system:serviceaccount:kube-system:horizontal-pod-autoscaler" cannot get deploymentconfigs/scale.extensions in project "<project-name>" Expected results: 3. After some time, pod on number are increased, the max pod number is 10 Additional info: the while loop did not increse pods Whether due to the above event
FYI, to make clarity, the error "system:serviceaccount:kube-system:horizontal-pod-autoscaler" can be seen in `oc describe hpa $HPA_NAME` after the HPA is just created (no matter through CLI or web console). i.e. the error message is unrelated to increasing traffic to the app because the message is seen before user increases traffic to autoscale pod number
Same root issue as https://bugzilla.redhat.com/show_bug.cgi?id=1458663#c1 The HPA controller is not being started with a client that knows how to look for origin resources, so it is looking for them in the extensions API group https://github.com/openshift/origin/pull/14678 will resolve this
*** This bug has been marked as a duplicate of bug 1458663 ***