Description of problem: Octavia amphora certificate files are being created in an unexpected path and with invalid content [root@controller-2 log]# ls /var/lib/config-data/puppet-generated/ | grep octavia octavia octaviaca_cert_path octaviaca_private_key_path octaviaclient_cert_path octavia.md5sum [root@controller-2 log]# cat /var/lib/config-data/puppet-generated/octaviaca_cert_path ca_cert_content[root@controller-2 log]# cat /var/lib/config-data/puppet-generated/octaviaca_private_key_path private_key_content[root@controller-2 log]# cat /var/lib/config-data/puppet-generated/octaviaclient_cert_path service_pem_content[root@controller-2 log]# Version-Release number of selected component (if applicable): RHOS_TRUNK-15.0-RHEL-8-20190520.n.2 How reproducible: 100% Steps to Reproduce: 1. Deploy OSP 15 with Octavia enabled 2. Create amphora load balancer Actual results: Load balancer will not be created successfully. It will go into ERROR provisioning_status Expected results: Amphora load balancer would be successfully provisioned and go ACTIVE.
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/RHEA-2019:2811