Bug 1744435 - test-cmd: error: --get-url test is borked
Summary: test-cmd: error: --get-url test is borked
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2.0
Assignee: Maciej Szulik
QA Contact: zhou ying
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-22 07:59 UTC by Tomáš Nožička
Modified: 2019-10-16 06:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:37:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 23649 0 None None None 2019-08-22 09:24:33 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:37:27 UTC

Description Tomáš Nožička 2019-08-22 07:59:04 UTC
Running test/cmd/basicresources.sh:175: executing 'oc set probe -f /var/tests/test/cmd/testdata/hello-openshift/hello-pod.json --local -o yaml --liveness --get-url=https://127.0.0.1:port/path' expecting success and text 'port: port'...
FAILURE after 0.000s: test/cmd/basicresources.sh:175: executing 'oc set probe -f /var/tests/test/cmd/testdata/hello-openshift/hello-pod.json --local -o yaml --liveness --get-url=https://127.0.0.1:port/path' expecting success and text 'port: port': the command returned the wrong error code; the output content test failed
There was no output from the command.
Standard error from the command:
error: --get-url could not be parsed as a valid URL: parse https://127.0.0.1:port/path: invalid port ":port" after host
[ERROR] hack/lib/cmd.sh:241: `return "${return_code}"` exited with status 1.


https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/23567/pull-ci-openshift-origin-master-e2e-cmd/506#0:build-log.txt%3A339

Comment 3 errata-xmlrpc 2019-10-16 06:37:16 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:2922


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