MOS 7.0 - Use of HTTPS/TLS with self-signed certs does not allow for change of public.fuel.local to a different name, causing deployment to fail
Bug #1555286 reported by
Bruce Basil Mathews
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Triaged
|
Medium
|
Fuel Documentation Team | ||
| Mitaka |
Won't Fix
|
Medium
|
Fuel Documentation Team | ||
| Newton |
Triaged
|
Medium
|
Fuel Documentation Team | ||
Bug Description
During Environment definition, if you select HTTPS and TLS and select "Self Signed Cert" from the Settings menu and then you change the name of the DNS entry for the VIP from 'public.fuel.local' to some other name such as 'test-vip', the deployment will fail because the SSL certificate is generated against the name 'public.fuel.local' and the connection to MySQL for the controller installation will fail, causing the deployment to fail.
Revision history for this message
| Bogdan Dobrelya (bogdando) wrote | #2 |
| tags: | added: area-docs docs |
| Changed in fuel: | |
| milestone: | none → 9.0 |
| assignee: | nobody → Fuel Documentation Team (fuel-docs) |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| summary: |
- MOS 7.0 - Use of HTTPS/TLS does not allow for change of - public.fuel.local to a different name, causing deployment to fail + MOS 7.0 - Use of HTTPS/TLS with self-signed certs does not allow for + change of public.fuel.local to a different name, causing deployment to + fail |
To post a comment you must log in.
I believe this has to be covered in docs. If one changes a default node's name or DNS entry for a controller's node's VIP, the default self-signed certificate which comes "out of box" will not work, so on has to provide new one as well.