Red Hat Bugzilla – Bug 1402356
Wrong and non-understandable message of oc idle
Last modified: 2017-07-24 10:11 EDT
Description of problem: Wrong and non-understandable message of oc idle Version-Release number of selected component (if applicable): oc v3.4.0.33 How reproducible: Always Steps to Reproduce: 1. Create project. Create app $ oc new-app -f https://raw.githubusercontent.com/openshift/origin/master/examples/sample-app/application-template-stibuild.json 2. Wait database is deployed. Then: $ oc idle database --dry-run=false 3. $ oc get endpoints database NAME ENDPOINTS AGE database <none> 3h Actual results: Though step 3 shows `oc idle` takes effect, step 2 outputs 'dry run': $ oc idle database --dry-run=false Marked service xxia-proj/database to unidle resource DeploymentConfig xxia-proj/database (unidle to 1 replicas) Idled DeploymentConfig xxia-proj/database (dry run) Besides, 'Marked service xxia-proj/database to unidle resource DeploymentConfig xxia-proj/database (unidle to 1 replicas)' is hard to understand. Is it wanting to express 'idle' or 'unilde'? It is obscure that 'unidle' is adj or verb? Expected results: 2. Should remove 'dry run'. 'Marked service xxia-proj/database to unidle resource DeploymentConfig xxia-proj/database (unidle to 1 replicas)' could be simply removed or improved. Additional info:
Related PR: https://github.com/openshift/origin/pull/12718
Verified in oc v3.5.0.31-1. Now step 2 can output clearer message: $ oc idle database --dry-run=false The service "xxia-proj/database" has been marked as idled The service will unidle DeploymentConfig "xxia-proj/database" to 1 replicas once it receives traffic DeploymentConfig "xxia-proj/database" has been idled Besides, tested other scenarios "when idling a service with one or more scalable refs, no scalable refs (or a service that has already been idled), and when idling a service with the --dry-run flag" mentioned in https://github.com/openshift/origin/pull/12718, their output messages are good, as shown in the PR comment. Thx
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-2017:0884