Description of problem: If trying to deploy the kubevirt APB for the second time (with the same registry) it fails with a meaningless error Version-Release number of selected component (if applicable): 0.7.0-alpha.2 How reproducible: 100% Steps to Reproduce: 1. deploy kubevirt once 2. try to deploy for the second time with the same registry 3. Actual results: Error provisioning ServiceInstance of ClusterServiceClass (K8S: "fd9b21a9caa8bf8b42b27bb0c90d3b74" ExternalName: "dh-virtualization") at ClusterServiceBroker "ansible-service-broker": Status: 400; ErrorMessage: <nil>; Description: not found; ResponseError: <nil> Expected results: should give a meaningful error message Additional info:
While I was able to reproduce the issue with v0.7.0-alpha.2 ... the issue appears to have been resolved with release v0.7.0. Repeated deployments of the kubevirt-apb to the same namespace will complete/provision successfully without error.
https://github.com/kubevirt/kubevirt-ansible/pull/314
Ryan, Looks like that PR was for 0.7.0, do we need a backport for 0.6.*
I branched after it was merged so 0.6.2 already has it.
@ryan, I tried it on the latest d/s build, and getting Error provisioning ServiceInstance of ClusterServiceClass (K8S: "fd9b21a9caa8bf8b42b27bb0c90d3b74" ExternalName: "dh-virtualization") at ClusterServiceBroker "ansible-service-broker": Status: 400; ErrorMessage: <nil>; Description: not found; ResponseError: <nil> are you sure the fix is in?
It worked for me yesterday. Are you using 'brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/cnv11-tech-preview/kubevirt-apb:1.1' ?
Created attachment 1475589 [details] oc get serviceinstances --all-namespaces -o yaml
I was able to create two service instances without any error. [root@cnv-executor-lbednar-master1 ~]# oc get serviceinstances -n kube-system NAME AGE kubevirt 21m kubevirt2 5m
Based on https://bugzilla.redhat.com/show_bug.cgi?id=1597259#c8 moving back to assigned.
is this bug about a meaningless error being reported or that we should error meaningfully on a second deployment? If it's the former, then we can close this.
I didn't experience with any meaningless error, it just let me to provision two kubevirt service instances (https://bugzilla.redhat.com/show_bug.cgi?id=1597259#c8) . I don't know what is proper solution, but I believe that have multiple service instances of kubevirt deployed is not appropriate.
The broker doesn't have a mechanism to block this. We would have to implement something on the kubevirt-apb side. I think we can close this at least for the 1.3 timeframe.