Bug 1554624 - should not hard code scalable objects in 'oc status'
Summary: should not hard code scalable objects in 'oc status'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 3.10.0
Assignee: Maciej Szulik
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-13 03:03 UTC by Yadan Pei
Modified: 2019-04-09 23:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-09 23:40:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0620 0 None None None 2019-04-09 23:40:52 UTC

Description Yadan Pei 2018-03-13 03:03:30 UTC
Description of problem:
should not hard code scalable objects in 'oc status', track the issue in https://github.com/openshift/origin/issues/18927

Version-Release number of selected component (if applicable):
v3.9.4

How reproducible:
Always

Steps to Reproduce:
1.Create DeploymentConfig, Deployment
$ oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/deployment/deployment1.json
$ oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/deployment/hello-deployment-1.yaml
2.check project status with "oc status"


Actual results:
2. ..<snipped>..
Errors:
  * hpa/hello-openshift is attempting to scale Deployment/hello-openshift, which doesn't exist

Expected results:
2. Should not report errors because deployment/hello-openshift does exist

Additional info:

Comment 1 Solly Ross 2018-03-13 15:17:44 UTC
This is not an 3.9 bug.  The referenced upstream bug is specifically "what do we do after 3.9".  Moving to 3.10

Comment 4 Maciej Szulik 2019-03-01 21:29:28 UTC
The checks for HPA were removed in https://github.com/openshift/origin/pull/18950 in 3.10, moving to qa.

Comment 5 Yadan Pei 2019-03-04 03:25:25 UTC
# oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/deployment/deployment1.json
deploymentconfig.apps.openshift.io "hooks" created
# oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/deployment/hello-deployment-1.yaml
deployment.extensions "hello-openshift" created

# oc status -v
Flag --verbose has been deprecated, Use --suggest instead.
In project yapei on server https://<master>:8443

dc/hooks deploys docker.io/openshift/hello-openshift:latest 
  deployment #1 deployed 3 minutes ago - 1 pod

deployment/hello-openshift deploys openshift/hello-openshift
  deployment #1 running for 2 minutes - 10 pods

Info:
  * deployment/hello-openshift has no liveness probe to verify pods are still running.
    try: oc set probe deployment/hello-openshift --liveness ...
  * dc/hooks has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/hooks --readiness ...
  * dc/hooks has no liveness probe to verify pods are still running.
    try: oc set probe dc/hooks --liveness ...

View details with 'oc describe <resource>/<name>' or list everything with 'oc get all'.

No HPA info in 'oc status', move to VERIFIED

# oc version
oc v3.10.119
kubernetes v1.10.0+b81c8f8
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://<master>:8443
openshift v3.10.119
kubernetes v1.10.0+b81c8f8

Comment 7 errata-xmlrpc 2019-04-09 23:40:43 UTC
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-2019:0620


Note You need to log in before you can comment on or make changes to this bug.