Bug 1540526
Summary: | HPA controller was unable to get the target's current scale: no matches for /, Kind=DeploymentConfig | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | DeShuai Ma <dma> |
Component: | Node | Assignee: | Solly Ross <sross> |
Status: | CLOSED ERRATA | QA Contact: | DeShuai Ma <dma> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.9.0 | CC: | aos-bugs, avagarwa, jokerman, mmccomas, sjenning, wjiang, yufchang |
Target Milestone: | --- | Keywords: | OnlineDedicated, OnlinePro, OnlineStarter |
Target Release: | 3.9.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-03-28 14:24:57 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
DeShuai Ma
2018-01-31 10:02:44 UTC
Yeah, looks like `oc autoscale` is generating an HPA with the old deploymentconfig group version, which isn't understandable by most discovery-based clients -- we need to fill in an actual group. Wonder why `oc autoscale` isn't filling in the new group name. Is this an old client? Will try to repro locally and see whats going on. Yep, looks like we're prefering /oapi ATM, which is causing issues. Will talk to the master and/or cli teams to figure out the best way forward. (FWIW, `oc autoscaling dc.apps.openshift.io/foo` works fine, it's just the form that's unqualified by a group name that doesn't work). Checked with # openshift version openshift v3.9.0-0.47.0 kubernetes v1.9.1+a0ce1bc657 etcd 3.2.8 and can not reproduce this issue now. 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:0489 |