tripleo doesn't set the secure_proxy_ssl_header for nova.conf
Bug #1606863 reported by
Marios Andreou
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Marios Andreou |
Bug Description
As discussed at https:/
On master this can go in to the nova-api service definition whilst in stable/mitaka (which is what the reference BZ is opened against) it would go into controller hiera I think.
Reviews incoming. One note is that I can't see secure_
[1] http://
Changed in tripleo: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/347749
Review: https:/