Need certificates-relation-departed code to reconfigure certs

Bug #1879995 reported by Ryan Farrell
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard Charm
Triaged
Medium
Unassigned

Bug Description

Currently the charm is configured to take ssl certificates from the certificates relation, if it exists. This takes precedence over the certificate data defined in charms config.

When removing the certificates relation however, there is no relation-departed code which re-configures openstack dashboard to use ssl certs defined in the config data.

The workaround currently is to remove the relation, then --reset the ssl_cert in the charm's config, and then set the value again.

Tags: scaleback
Revision history for this message
Ryan Farrell (whereisrysmind) wrote :

To reproduce the issue:
1) Setup a cloud with vault:certificates openstack-dashboard:certificates relation
2) Add config values for ssl_ca, ssl_cert, ssl_key to openstack-dashboard
3) Remove the certificates relation

description: updated
Changed in charm-openstack-dashboard:
status: New → Triaged
importance: Undecided → Medium
Ryan Beisner (1chb1n)
tags: added: scaleback
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.