[RFE]: warn the user if tls-endpoints-public-*.yaml wasn't selected

Bug #1645237 reported by Udi Kalifon on 2016-11-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Wishlist
Unassigned

Bug Description

If you include "Enable TLS" in your deployment you have to also include one of the following environment files:
environments/tls-endpoints-public-ip.yaml
environments/tls-endpoints-public-dns.yaml

Forgetting to include one of these options will result with an overcloud that has no reachable public endpoints. The deployment passes with no errors so the user will have a hard time guessing what went wrong. We need a way to clearly log a warning (or even error) if the user selected TLS and didn't select which flavor.

Alternatively, we might consider defaulting to one of the options unless the user selected something else (just a suggestion...).

I am tagging this bug as "ui" and "validations", although it really deserves a fix in the template level or the flows.

Julie Pichon (jpichon) wrote :

This is somewhat related to bug 1642308 and I suspect this will also be improved with the blueprint at https://blueprints.launchpad.net/tripleo/+spec/update-capabilities-map-to-map-environment-dependencies . I'll link them too.

Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
Changed in tripleo:
importance: Medium → Wishlist
Emilien Macchi (emilienm) wrote :

This bug was last updated over 180 days ago, as tripleo is a fast moving project and we'd like to get the tracker down to currently actionable bugs, this is getting marked as Invalid. If the issue still exists, please feel free to reopen it.

Changed in tripleo:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers