Description of problem: Tracking the test coverage for 16.1 to 16.2 with TLS-e and pre-exisiting workloads. This is based around the coverage needed for [1]. High level procedure: 1. Have a 16.1 TLS-e as the source; and a 16.2 TLS-e (as dest) 2. Create a few Nova instancesa 3. Upgrade the 16.1 setup to 16.2; this brings in libvirt-6.10. 4. Make sure to have the client certificate available on the source host in /etc/libvirt/pki/ directory. Just a symlink of the server-cert.pem to client-cert.pem should suffice, because, the server certificate generated by TripleO is valid for client _and_ server: Key Purpose (not critical): TLS WWW Server. TLS WWW Client. 5. Now live-migrate an instance created in step-2 — now running upgraded 16.2 setup — on the source host to the destination 16.2 host. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1945760#c13 Additional info: This is the second area of verification based around https://bugzilla.redhat.com/show_bug.cgi?id=1945760
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 (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement 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/RHEA-2021:3483