Bug 1463607 - Cannot create thirdpartyresource
Cannot create thirdpartyresource
Status: CLOSED NOTABUG
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
3.6.1
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: Derek Carr
DeShuai Ma
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-21 06:09 EDT by Zhang Cheng
Modified: 2017-06-22 22:41 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-06-22 09:47:30 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Zhang Cheng 2017-06-21 06:09:07 EDT
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
Comment 1 Jordan Liggitt 2017-06-22 09:47:30 EDT
ThirdPartyResource objects are not supported in any version of OpenShift

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