Horizon Container Failing to Start

Bug #2015564 reported by Antony Messerli
This bug report is a duplicate of:  Bug #2011716: horizon container error at start. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Incomplete
Undecided
Unassigned

Bug Description

When deploying kolla-ansible with latest stable/zed, the horizon container is failing to start with the following error:

+ echo 'Running command: '\''/usr/sbin/httpd -DFOREGROUND'\'''
+ exec /usr/sbin/httpd -DFOREGROUND
Running command: '/usr/sbin/httpd -DFOREGROUND'
AH00526: Syntax error on line 85 of /etc/httpd/conf.d/ssl.conf:
SSLCertificateFile: file '/etc/pki/tls/certs/localhost.crt' does not exist or is empty

openstack_release: "zed"
kolla_base_distro: "rocky"

Docker Inspect Output:

            "Image": "quay.io/openstack.kolla/horizon:zed-rocky-9",
            "Labels": {
                "build-date": "20230405",
                "io.buildah.version": "1.28.0",
                "kolla_version": "15.1.1",
                "maintainer": "Kolla Project (https://launchpad.net/kolla)",
                "name": "horizon"
            }

This is a dupe of https://bugs.launchpad.net/kolla/+bug/2011716 but opening a new one since the original was closed and there were multiple people reporting.

Revision history for this message
Michal Nasiadka (mnasiadka) wrote :

Can you please check with latest images? I'm pretty sure we merged the Zed backport recently.

Changed in kolla:
status: New → Incomplete
Revision history for this message
Antony Messerli (antonym) wrote :

Will give a try with the latest image.

For reference if anyone else experiences this, we found ensuring that /tmp/dhparams.pem was removed from all controller nodes before a deploy and then a reconfigure target horizon nodes would fire them back up.

Revision history for this message
Antony Messerli (antonym) wrote :

I see the original bug was re-opened so I'll close this one.

Revision history for this message
Maksim Malchuk (mmalchuk) wrote :

201176 is the vrong bug report.

Revision history for this message
Maksim Malchuk (mmalchuk) wrote :
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.