Description of problem: After executing the octavia upgrade procedure the loadbalancers are not updated as expected. $ kubectl -n openshift-kuryr annotate cm kuryr-config networkoperator.openshift.io/kuryr-octavia-provider- $ kubectl get -n openshift-kuryr cm/kuryr-config -o jsonpath='{.metadata.annotations.networkoperator\.openshift\.io/kuryr-octavia-provider}' ovn [waiting a reasonable time] $ openstack loadbalancer list -c provider -f value | grep amphora | wc -l 52 $ openstack loadbalancer list -c provider -f value | grep ovn | wc -l 0 Version-Release number of selected component (if applicable): 4.6.0-0.nightly-2020-09-05-015624 How reproducible: Always Steps to Reproduce: https://docs.openshift.com/container-platform/4.5/networking/load-balancing-openstack.html Actual results: Expected results: Additional info: kuryr-controller logs on http://file.rdu.redhat.com/rlobillo/octavia_upgrade/ocp4.6.0-0.nightly-2020-08-27-005538/
Verified on 4.6.0-0.nightly-2020-09-21-030155 over RHOS-16.1-RHEL-8-20200903.n.0 Jenkins job with flag '--octaviaupdate yes' on the installation runs successfully. Logs attached (ir-openshift-install.log) Tests run with expected results. Attached.
Created attachment 1715669 [details] octavia update logs (automated on infrared)
Created attachment 1715670 [details] test results
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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196