neutron api tls issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Michele Baldessari |
Bug Description
There are two tls issues currently in neutron:
A) neutron_api is doing bind mounting tls certs directly from the host and then chowning them from then container.
"Source": "/etc/pki/
"Destination": "/etc/pki/
"Source": "/etc/pki/
"Destination": "/etc/pki/
And then it thinks it can chown it inside the container via the kolla script:
[root@controller-0 stdouts]# more /var/lib/
...
{
"path": "/etc/pki/
"perm": "0644"
},
{
"path": "/etc/pki/
"perm": "0644"
}
What needs to happen here is that we drop the bind mounts, and copy in the certs via kolla and put them in /var/lib/
This typically breaks the updating of the certs, but that is currently not working for neutron_ovn anyway since the cert has no post-command in certmonger:
Request ID 'neutron_ovn':
status: MONITORING
stuck: no
key pair storage: type=FILE,
CA: IPA
issuer: CN=Certificate Authority,
subject: CN=controller-
expires: 2021-11-14 15:44:20 UTC
dns: controller-
principal name: <email address hidden>
key usage: digitalSignatur
eku: id-kp-serverAut
pre-save command:
post-save command:
track: yes
auto-renew: yes
Also fun fact, it would not even work with bind mounts because a new cert would create a new inode and when you bind mount a single file and change the inode on the host the container will not see any changes at all.
B) The logging in the neutron_
Fix proposed to branch: master /review. opendev. org/694614
Review: https:/