cmd test flake: oc login returned the wrong error code

[jsafrane]

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/15725/test_pull_request_origin_cmd/2647/

=== BEGIN TEST CASE ===
hack/test-cmd.sh:112: executing 'oc login --server='https://172.17.0.2:28443' --certificate-authority='/tmp/openshift/test-cmd/openshift.local.config/master/ca.crt' -u test-user -p anything' expecting success
FAILURE after 58.161s: hack/test-cmd.sh:112: executing 'oc login --server='https://172.17.0.2:28443' --certificate-authority='/tmp/openshift/test-cmd/openshift.local.config/master/ca.crt' -u test-user -p anything' expecting success: the command returned the wrong error code
There was no output from the command.
Standard error from the command:
error: The server was unable to respond - verify you have provided the correct host and port and that the server is currently running.
=== END TEST CASE ===

Might be related to #15453

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close