Description of problem: When an instance name is specified, "svcat unbind instancename" should print deleted bindings Version-Release number of selected component (if applicable): client: v3.10.0-0.56.0;Upstream:v0.1.19 server: v1.10.0+b81c8f8 How reproducible: Always Steps to Reproduce: 1. $ svcat describe instances ups-instance2 2. $ svcat unbind ups-instance2 3. Actual results: "svcat unbind ups-instance2 " command didn't print deleted bindings. [szh@localhost my-new-apn]$ svcat describe instances ups-instance2 Name: ups-instance2 Namespace: szh-project Status: Ready - The instance was provisioned successfully @ 2018-06-01 07:06:08 +0000 UTC Class: user-provided-service Plan: default Parameters: {} Bindings: NAME STATUS +------------------------+--------+ ups-instance1-bind Ready ups-instance2 Ready ups-instance2-binding1 Ready [szh@localhost my-new-apn]$ svcat unbind ups-instance2 [szh@localhost my-new-apn]$ svcat describe instances ups-instance2 Name: ups-instance2 Namespace: szh-project Status: Ready - The instance was provisioned successfully @ 2018-06-01 07:06:08 +0000 UTC Class: user-provided-service Plan: default Parameters: {} Bindings: No bindings defined Expected results: When an instance name is specified, svcat unbind output should print deleted bindings. Additional info:
There is already a PR open that should fix this: https://github.com/kubernetes-incubator/service-catalog/pull/2049
Not a release blocker, we're closing down 3.10, setting target version to 3.10.z.
This has been fixed. Anything built since 18 July will include it, please make certain Service Catalog build is v0.1.24 or later.
Test with # svcat version Client Version: v3.11.0-0.16.0;Upstream:v0.1.27 Server Version: v1.11.0+d4cacc0 # svcat unbind dyan-test deleted dyan-bind could move to verified
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:2376