openstack_https_frontend.conf was created, but a2ensite and a2enmod ssl,proxy were not executed

Bug #1713944 reported by Nobuto Murata
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack AODH Charm
Confirmed
High
Liam Young

Bug Description

After passing ssl_cert,key and ssl_ca(bug 1713922) and setting os-*-network option (bug 1711422), expected /etc/apache2/sites-available/openstack_https_frontend.conf was created. However, the openstack_https_frontend was not enabled.

I had to run the commands manually:

a2ensite openstack_https_frontend
a2enmod ssl
a2enmod proxy
service apache2 restart

Revision history for this message
Nobuto Murata (nobuto) wrote :

Even after commands below, I still get Proxy error from Apache2. So needs to look into more when I have some time.

a2ensite openstack_https_frontend
a2enmod ssl
a2enmod proxy
service apache2 restart

Chris Gregan (cgregan)
tags: added: cdo-qa-blocker
Revision history for this message
Ryan Beisner (1chb1n) wrote :

Please provide the charm revision information, juju status, and the charm config from the bundle.

Was this the stable/17.02 stable AODH charm? Or was it some other newer or older revision?

Changed in charm-aodh:
status: New → Incomplete
Ryan Beisner (1chb1n)
Changed in charm-aodh:
milestone: none → 17.11
Revision history for this message
Ryan Beisner (1chb1n) wrote :

We will need to repro with current charms and target for next release, possibly a stable backport/update if it meets those requirements. Thank you.

Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

I was able to reproduce this using the current -next version of the aodh charm - 9d7aa38.

Here is my aodh config, using self signed cert:
http://paste.ubuntu.com/25481013/

juju status:
http://paste.ubuntu.com/25481026/

Changed in charm-aodh:
status: Incomplete → New
Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

I was able to get things working by using Nobuto's workaround with the addition of this command:

a2enmod proxy_http

Ryan Beisner (1chb1n)
Changed in charm-aodh:
status: New → Confirmed
milestone: 17.11 → none
Revision history for this message
Ryan Beisner (1chb1n) wrote :

Thanks for the repro.

This appears to be a bug which existed in 16.10 and 17.02 (hence not a new bug). It may similarly impact other reactive charms (which are only the newer greenfield charms).

The bulk of the OpenStack charms are classic (not reactive), and as such there is no new risk over stable/17.02. Based on that, and this not being a regression, I don't see this alone as a blocker to a release which does resolve other issues.

I would like for us to address this and backport the fix ASAP, however.

Ryan Beisner (1chb1n)
Changed in charm-aodh:
importance: Undecided → High
Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

I'd like to add that I had to work around bug 1709475 to reproduce that; perhaps it could be fixed and back ported at the same time, along with the bugs Nobuto mentioned in the description.

Revision history for this message
Ryan Beisner (1chb1n) wrote :

This fix should be batched with fixes for bug 1709475, bug 1713922 and bug 1711422, based on input from the engineers who reproduced.

tags: added: uosci
tags: added: backport-potential
Chris Gregan (cgregan)
tags: added: onsite
Ryan Beisner (1chb1n)
Changed in charm-aodh:
milestone: none → 17.11
Chris Gregan (cgregan)
tags: added: cpe-onsite
removed: onsite
Ryan Beisner (1chb1n)
Changed in charm-aodh:
assignee: nobody → Liam Young (gnuoy)
Revision history for this message
Liam Young (gnuoy) wrote :

Marking as duplicate of 1719331

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.