Service apache2 not started
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard Charm |
Confirmed
|
Critical
|
Billy Olsen |
Bug Description
Hi,
I have an issue with my Openstack deployment, from time to time, in a "haclustered" configuration, some openstack-dashboard units fails to start with a message saying the apache2 service is not running.
Fixing the issue is pretty easy, either start the service by hand or reboot the unit.
There is no error that I can spot, it just seems that restarting service during deployment, probably after configuring the certificates relation to vault, the service fails to start for unknown reason and the charm doesn't try to restart it from time to time.
Would it be possible to make that service status check a bit more solid in order to avoid manual steps during deployment ?
Here is my deployment ocnfiguration :
=======
series: focal
applications:
openstack-
charm: cs:openstack-
channel: stable
num_units: 3
to:
- lxd:3
- lxd:4
- lxd:5
options:
enforce-ssl: false
offline-
openstack
secret: iS6aV6dY1kC6gS1j
use-syslog: false
vip: 192.168.111.220
worker-
openstack-
charm: cs:hacluster-76
channel: stable
options:
cluster_
openstack-
charm: cs:mysql-router-10
channel: stable
relations:
- - openstack-
- openstack-
- - openstack-
- keystone:
- - openstack-
- openstack-
- - openstack-
- mysql-innodb-
- - vault:certificates
- openstack-
=======
Changed in charm-openstack-dashboard: | |
status: | New → Confirmed |
Changed in charm-openstack-dashboard: | |
assignee: | nobody → Billy Olsen (billy-olsen) |
importance: | Undecided → Critical |
We are seeing this with SQA too.
From the logs it seems that something has gone wrong with the certificates:
apachectl[103299]: SSLCertificateFile: file '/etc/apache2/ ssl/horizon/ cert_10. 246.173. 14' does not exist or is empty
Crashdumps can be found here: /oil-jenkins. canonical. com/artifacts/ e71d99fb- 68a6-443e- b5fd-51f42322e4 ec/index. html
https:/