| Summary: | Cannot create resource by file which contains slash (compatibility oc v3.4 VS openshift v3.1.1.10) | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | XiaochuanWang <xiaocwan> |
| Component: | oc | Assignee: | Maciej Szulik <maszulik> |
| Status: | CLOSED EOL | QA Contact: | Xingxing Xia <xxia> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 3.4.0 | CC: | aos-bugs, ffranz, jokerman, mmccomas, wmeng, yapei |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-21 09:12:14 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
XiaochuanWang
2016-12-07 08:26:13 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 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. Closing due to age. |