TLS everywhere: the apache service wrongly requests certificates for all networks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Harald Jensås | ||
Queens |
Fix Released
|
Critical
|
Harald Jensås | ||
Rocky |
Fix Released
|
Critical
|
Harald Jensås |
Bug Description
we currently do a loop to go through all the networks as follows:
ApacheNetworks:
type: OS::Heat::Value
properties:
value:
# NOTE(jaosorior) Get unique network names to create
# certificates for those. We skip the tenant network since
# we don't need a certificate for that.
- ctlplane
{%- for network in networks %}
{%- if network.name_lower != 'tenant' %}
- {{network.
{%- endif %}
{%- endfor %}
In puppet/
The ApacheNetworks is used later to pass the data to certmonger for certificate generation[2]:
This results, in deployments with the default network setup, with certmonger trying to request a certificate for the management interface, and failing:
Request ID 'httpd-management':
status: CA_REJECTED
ca-error: Server at https:/
stuck: yes
key pair storage: type=FILE,
CA: IPA
issuer:
subject:
expires: unknown
pre-save command:
post-save command: "systemctl reload httpd"
track: yes
auto-renew: yes
[1] https:/
[2] https:/
Changed in tripleo: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
milestone: | none → stein-2 |
Fix proposed to branch: master /review. openstack. org/629835
Review: https:/