[RFE] Only show TLS Endpoints dialogue when "Enable TLS" is checked

Bug #1642308 reported by Dan Trainor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

Only show the TLS Endpoints configuration dialogue when the "Enable TLS" checkbox is checked. Otherwise, checking any one of the "TLS Endpoints" checkbox invokes an action that's unable to execute because it can't find the dependencies which would have been provided by clicking the "Enable TLS" checkbox.

Tags: ui
Revision history for this message
Dan Trainor (dtrainor) wrote :
Revision history for this message
Dan Trainor (dtrainor) wrote :
Changed in tripleo:
importance: Undecided → Medium
status: New → Triaged
milestone: none → ocata-2
Revision history for this message
Julie Pichon (jpichon) wrote :

The spec proposed for Ocata at https://review.openstack.org/#/c/393365/ mentions dependencies and collisions between environment, I'm adding a link here for reference for now as I expect it will handle this as well.

Revision history for this message
Jiri Tomasek (jtomasek) wrote :
Changed in tripleo:
milestone: ocata-2 → ocata-3
Changed in tripleo:
milestone: ocata-3 → pike-1
Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.