Failed to start the admin server after upgrade from pre-mod-wsgi based keystone

[Alvaro Uria]

Ubuntu Trusty 14.04.4
Juju 1.25.5
OpenStack Charms 16.04
Mitaka

As described on release notes, for Liberty and above the Keystone interface is now served using the Apache mod_wsgi module (/etc/apache2/sites-enabled/wsgi-keystone.conf) rather than as a standalone service.

However, /etc/keystone/keystone.conf uses templates/kilo/keystone.conf, which configures admin-port on :35347. Such port cannot be bound because Apache2 is already using it.

I think template file should be updated for Liberty and above, to avoid getting "Failed to start the admin server" error on keystone.log.

Cheers,
-Alvaro.

[James Page (james-page)]

I think the keystone standalone process should be disabled by the charm to ensure that the required ports can be bound under apache/mod_wsgi

[Alvaro Uria (aluria)]

Hi James,

You're right. keystone is disabled by creating /etc/init/keystone.override (service_pause). However, when charm and openstack are upgraded from previous versions,
1) keystone service is not stopped (in favor of apache2+mod_wsgi)
2) nrpe alerts are not removed from /var/lib/nagios/export and /etc/nagios/nrpe.d/check_keystone.cfg (a nagios user would expect a malfunction because he would receive an alert on "keystone is not running")

As to bug description, I don't see the need to update templates/kilo/keystone.conf as other logic in the charm would disable keystone service.

Cheers,
-Alvaro.

[Alex Kavanagh (ajkavanagh)]

Liberty is no longer supported by the charm.