Verify with asb: 1.4.2,
when provision and deprovision, it'll not create new networkpolicy, and the network connection between pods is still work.
But when the provision and deprovision succeed, it will try to delete networkpolicy which is not created, and report error:
time="2018-12-04T09:11:43Z" level=error msg="unable to delete the network policy object - networkpolicies.networking.k8s.io \"bundle-e4c1e666-dcce-434c-9331-825f4d88f7d2\" not found"
It's confused for users, it's better to check existence before deleting or downgrade log level. I move back to ASSIGNED.
Fixed by PR https://github.com/openshift/ansible-service-broker/pull/1177 for OpenShift 3.9 (Broker 1.1.19+)
* OpenShift 4.0 (Broker 1.4.x)
Fixed by broker PR https://github.com/openshift/ansible-service-broker/pull/1180 and by bundle-lib PR https://github.com/automationbroker/bundle-lib/pull/178
* OpenShift 3.11 (Broker 1.3.x)
Fixed by broker PR https://github.com/openshift/ansible-service-broker/pull/1181 and by bundle-lib PR https://github.com/automationbroker/bundle-lib/pull/178
* OpenShift 3.10 (Broker 1.2.x)
Fixed by broker PR https://github.com/openshift/ansible-service-broker/pull/1185 and by bundle-lib PR https://github.com/automationbroker/bundle-lib/pull/180
PR is merged in v1.4.5.
the lastest image in downstream is still 1.4.4. Move to Modified.
docker run --entrypoint=asbd reg-aws..../ose-ansible-service-broker:v4.0 --version
According to #comment 10, Move back to modified.
The target release is 4.2, but there's not ose-ansible-service-broker v4.2 image in brew registry.
when using: oc image info ..../openshift/ose-ansible-service-broker:v4.1 --insecure=true,
no commit info for asb
do we still using `asbd --version` to trace code change in asb image?
asb operator image code change can be traced by `oc image info` like:
$ oc image info .../openshift/ose-ansible-service-broker-operator:v4.1 --insecure=true | grep commit
I believe this is the build that you are looking for:
when provision and deprovision, no new networkpolicy created, and no errors when no networkpolicy to delete.
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.