Bug 1463607
| Summary: | Cannot create thirdpartyresource | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Zhang Cheng <chezhang> |
| Component: | Node | Assignee: | Derek Carr <decarr> |
| Status: | CLOSED NOTABUG | QA Contact: | DeShuai Ma <dma> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.6.1 | CC: | aos-bugs, dma, jliggitt, jokerman, mmccomas |
| 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: | 2017-06-22 13:47:30 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: | |
| Embargoed: | |||
ThirdPartyResource objects are not supported in any version of OpenShift |
Description of problem: Cannot create thirdpartyresource error: unable to recognize "resource.yaml": no matches for stable.example.com/, Kind=CronTab Version-Release number of selected component (if applicable): v3.6.121 How reproducible: Everytime Steps to Reproduce: [root@ip-172-18-15-196 dma]# oc create -f tpr.yaml thirdpartyresource "cron-tab.stable.example.com" created [root@ip-172-18-15-196 dma]# cat tpr.yaml apiVersion: extensions/v1beta1 kind: ThirdPartyResource metadata: name: cron-tab.stable.example.com description: "A specification of a Pod to run on a cron style schedule" versions: - name: v1 [root@ip-172-18-15-196 dma]# oc get thirdpartyresource -o json { "apiVersion": "v1", "items": [ { "apiVersion": "extensions/v1beta1", "description": "Managed Alertmanager cluster", "kind": "ThirdPartyResource", "metadata": { "creationTimestamp": "2017-06-21T01:58:01Z", "name": "alertmanager.monitoring.coreos.com", "namespace": "", "resourceVersion": "3554", "selfLink": "/apis/extensions/v1beta1/thirdpartyresources/alertmanager.monitoring.coreos.com", "uid": "0e77bb54-5625-11e7-ba7d-0e7d5f65f2c4" }, "versions": [ { "name": "v1alpha1" } ] }, { "apiVersion": "extensions/v1beta1", "description": "A specification of a Pod to run on a cron style schedule", "kind": "ThirdPartyResource", "metadata": { "creationTimestamp": "2017-06-21T09:53:22Z", "name": "cron-tab.stable.example.com", "namespace": "", "resourceVersion": "28071", "selfLink": "/apis/extensions/v1beta1/thirdpartyresources/cron-tab.stable.example.com", "uid": "765aeffa-5667-11e7-ba7d-0e7d5f65f2c4" }, "versions": [ { "name": "v1" } ] }, { "apiVersion": "extensions/v1beta1", "description": "Managed Prometheus server", "kind": "ThirdPartyResource", "metadata": { "creationTimestamp": "2017-06-21T01:58:01Z", "name": "prometheus.monitoring.coreos.com", "namespace": "", "resourceVersion": "3555", "selfLink": "/apis/extensions/v1beta1/thirdpartyresources/prometheus.monitoring.coreos.com", "uid": "0e785bd7-5625-11e7-ba7d-0e7d5f65f2c4" }, "versions": [ { "name": "v1alpha1" } ] }, { "apiVersion": "extensions/v1beta1", "description": "Prometheus monitoring for a service", "kind": "ThirdPartyResource", "metadata": { "creationTimestamp": "2017-06-21T01:58:01Z", "name": "service-monitor.monitoring.coreos.com", "namespace": "", "resourceVersion": "3553", "selfLink": "/apis/extensions/v1beta1/thirdpartyresources/service-monitor.monitoring.coreos.com", "uid": "0e7770c1-5625-11e7-ba7d-0e7d5f65f2c4" }, "versions": [ { "name": "v1alpha1" } ] } ], "kind": "List", "metadata": {}, "resourceVersion": "", "selfLink": "" } [root@ip-172-18-15-196 dma]# oc create -f resource.yaml error: unable to recognize "resource.yaml": no matches for stable.example.com/, Kind=CronTab [root@ip-172-18-15-196 dma]# cat resource.yaml apiVersion: "stable.example.com/v1" kind: CronTab metadata: name: my-new-cron-object cronSpec: "* * * * /5" image: my-awesome-cron-image Actual results: thirdpartyresource create fail Expected results: thirdpartyresource should be created successful Additional info: None