+++ This bug was initially created as a clone of Bug #1590106 +++ Description of problem: When create app from image, and set hpa at the same time, on the page "/create/fromimage?", after creation, the hpa has incorrect ref apiversion and could not work normally Version-Release number of selected component (if applicable): openshift v3.10.0-0.64.0 kubernetes v1.10.0+b81c8f8 How reproducible: Always Steps to Reproduce: 1.Create app from image, and set auto scaling in advanced options 2.Check ref apiversion in hpa. 3.Check event. Actual results: 2.$ oc get hpa pytest -o yaml |grep scaleTargetRef -A 3 scaleTargetRef: apiVersion: extensions/v1beta1 kind: DeploymentConfig name: pytest 3. Check on the events page, there is warning info: pytest Horizontal Pod Autoscaler Warning Failed Get Scale no matches for kind "DeploymentConfig" in group "extensions" Expected results: 2.Should have correct ref apiversion Additional info: --- Additional comment from Samuel Padgett on 2018-06-13 12:22:20 EDT --- https://github.com/openshift/origin-web-console/pull/3024 --- Additional comment from openshift-github-bot on 2018-06-13 12:47:03 EDT --- Commits pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/22684c2a29e0e6c84a6c0dd00f69ef2e419b07fe Bug 1590106 - Fix HPA target resource for new app flow Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1590106 https://github.com/openshift/origin-web-console/commit/0360c0443d760bbcb342d1476f0199761ee6f330 Merge pull request #3024 from spadgett/fix-hpa Bug 1590106 - Fix HPA target resource for new app flow
https://github.com/openshift/origin-web-console/pull/3026
The latest bump e5d692e for current latest build 3.9.31-1 doesn't include the PR 3016, need a new puddle
OpenShift Master: v3.9.33 Kubernetes Master: v1.9.1+a0ce1bc657 OpenShift Web Console: v3.9.33 Tested on OCP env with above versio. Created hpa with new app flow on web console, the target resource api version is "apps.openshift.io/v1". The bug has been fixed, so move it to Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2213