Bug 1402294 - Cannot create resource by file which contains slash (compatibility oc v3.4 VS openshift v3.1.1.10)
Summary: Cannot create resource by file which contains slash (compatibility oc v3.4 VS...
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Maciej Szulik
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 08:26 UTC by XiaochuanWang
Modified: 2019-08-21 09:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-21 09:12:14 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description XiaochuanWang 2016-12-07 08:26:13 UTC
Description of problem:
When resource file contains slash, failed to `oc create -f <resource_file>`

Version-Release number of selected component (if applicable):
openshift v3.1.1.10
oc 3.4.0.33

How reproducible:
always

Steps to Reproduce:
1. # oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/deployment/deployment1.json  --loglevel=8I1207 15:02:26.092971    3389 loader.go:354] Config loaded from file /root/.kube/config
I1207 15:02:26.102382    3389 round_trippers.go:296] GET https://xxx.rdu2.redhat.com:8443/oapi
I1207 15:02:26.102413    3389 round_trippers.go:303] Request Headers:
I1207 15:02:26.102424    3389 round_trippers.go:306]     Accept: application/json, */*
I1207 15:02:26.102433    3389 round_trippers.go:306]     User-Agent: oc/v3.4.0.33+71c05b2 (linux/amd64) openshift/71c05b2
I1207 15:02:26.102442    3389 round_trippers.go:306]     Authorization: Bearer ENsMxxxGoUFG0u1YfftlWyQsQ
I1207 15:02:27.221981    3389 round_trippers.go:321] Response Status: 200 OK in 1119 milliseconds
I1207 15:02:27.222011    3389 round_trippers.go:324] Response Headers:
I1207 15:02:27.222021    3389 round_trippers.go:327]     Date: Wed, 07 Dec 2016 07:02:27 GMT
I1207 15:02:27.222031    3389 round_trippers.go:327]     Content-Length: 32
I1207 15:02:27.222039    3389 round_trippers.go:327]     Cache-Control: no-store
I1207 15:02:27.222049    3389 round_trippers.go:327]     Content-Type: application/json
I1207 15:02:27.222136    3389 request.go:908] Response Body: {
  "versions": [
    "v1"
  ]
}
I1207 15:02:27.222688    3389 cached_discovery.go:80] returning cached discovery info from /root/.kube/xxx.rdu2.redhat.com_8443/servergroups.json
I1207 15:02:27.222918    3389 cached_discovery.go:38] returning cached discovery info from /root/.kube/xxx.rdu2.redhat.com_8443/extensions/v1beta1/serverresources.json
I1207 15:02:27.223310    3389 cached_discovery.go:38] returning cached discovery info from /root/.kube/xxx.rdu2.redhat.com_8443/v1/serverresources.json
I1207 15:02:27.223812    3389 cached_discovery.go:80] returning cached discovery info from /root/.kube/xxx.rdu2.redhat.com_8443/servergroups.json
I1207 15:02:27.223931    3389 cached_discovery.go:38] returning cached discovery info from /root/.kube/xxx.rdu2.redhat.com_8443/extensions/v1beta1/serverresources.json
I1207 15:02:27.224306    3389 cached_discovery.go:38] returning cached discovery info from /root/.kube/xxx.rdu2.redhat.com_8443/v1/serverresources.json
I1207 15:02:27.535804    3389 decoder.go:203] decoding stream as JSON
F1207 15:02:27.536324    3389 helpers.go:115] error: unable to recognize "https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/deployment/deployment1.json": no matches for /, Kind=DeploymentConfig



Actual results:
error: unable to recognize "https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/deployment/deployment1.json": no matches for /, Kind=DeploymentConfig

Expected results:
Should be created successful. 

Additional info:
Both oc v3.4.0.33 against openshift v3.4.0.33 and oc v3.1.1.10 against openshfit v3.1.1.10 do not reproduce.

Comment 1 Yadan Pei 2016-12-08 06:24:12 UTC
Hi Fabiano,

For oc compatibility issues, how should we determine the priority and severity? I saw this was changed to L/L. 

We found that lots of resources such as Services & Pods couldn't be created successfully either on OpenShift 3.1 using OC 3.4.0.33 caused by this issue

Comment 2 Juan Vallejo 2017-01-26 21:55:46 UTC
I think the reason why the error "error: unable to recognize "https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/deployment/deployment1.json": no matches for /, Kind=DeploymentConfig" is happening is not because of a "slash" in the filename (in fact, it works fine on newer versions of oc), but rather because the server that you are using does not support "DeploymentConfig" resource kinds.

Comment 3 Maciej Szulik 2019-08-21 09:12:14 UTC
Closing due to age.


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