Bug 1610255
| Summary: | oc new-app and oc delete return error when interact with service-catalog | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Zihan Tang <zitang> |
| Component: | oc | Assignee: | Juan Vallejo <jvallejo> |
| Status: | CLOSED ERRATA | QA Contact: | Zihan Tang <zitang> |
| Severity: | low | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.11.0 | CC: | aos-bugs, chezhang, jaboyd, jiazha, jokerman, maszulik, mmccomas, zitang |
| Target Milestone: | --- | ||
| Target Release: | 3.11.0 | ||
| 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: | 2018-10-11 07:22:47 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: | |||
|
Description
Zihan Tang
2018-07-31 10:08:56 UTC
Zihan, despite the error message seen when deleting the resource, does the resource actually get deleted? This looks related to recent scheme changes in the cli, will investigate (In reply to Juan Vallejo from comment #1) > Zihan, despite the error message seen when deleting the resource, does the > resource actually get deleted? Yes , the resource is deleted successfully. I had this issue reported separately as https://bugzilla.redhat.com/show_bug.cgi?id=1611691. There is a bug in upstream Service Catalog that causes the error with get -w. It appears to me that in OpenShift 3.11 the delete was modified to do a get -w as part of the delete command. I think this BZ can be marked as a duplicate of 1611691. Thanks Jay, delete does do a watch now, as part of its updated behavior to wait for a resource to be finalized by default. As for the error message being seen in the `new-app` command, this is caused by the ServiceInstance's GroupVersionKind not being registered in the scheme that new-app is using to decode any objects that it creates. We could probably leave this bugzilla open to track a fix for that particular error. We hope this issue that "ServiceInstance's GroupVersionKind not being registered in the scheme" can be fixed ASAP. Form QE side, it's blocking most of automation TCs execution. I'm increasing the priority to "High" and keep severity to "Low". Thanks. *** Bug 1612048 has been marked as a duplicate of this bug. *** Changing status to Modified since ose not ready for test https://github.com/openshift/ose/blob/master/pkg/oc/cli/newapp/newapp.go ose image is ready, change it to ON_QA Verified,
oc new-app command succeed without error.
# oc new-app --file=template.yaml --param=INSTANCE_NAME\=brew-postgresql-apb --param=CLASS_EXTERNAL_NAME\=brew-postgresql-apb --param=PLAN_EXTERNAL_NAME\=dev --param=SECRET_NAME\=brew-postgresql-apb-parameters --param=INSTANCE_NAMESPACE\=test2
warning: Cannot find git. Ensure that it is installed and in your path. Git is required to work with git repositories.
--> Deploying template "post/serviceinstance-template" for "template.yaml" to project post
serviceinstance-template
---------
serviceinstance-template
* With parameters:
* INSTANCE_NAME=brew-postgresql-apb
* INSTANCE_NAMESPACE=test2
* CLASS_EXTERNAL_NAME=brew-postgresql-apb
* PLAN_EXTERNAL_NAME=dev
* SECRET_NAME=brew-postgresql-apb-parameters
--> Creating resources ...
serviceinstance.servicecatalog.k8s.io "brew-postgresql-apb" created
--> Success
Run 'oc status' to view your app.
oc delete serviceinstance still return error, will using bug 1611691 to trace.
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-2018:2652 |