Description of problem: RHOSP 16.1 horizon container is missing mysql driver, which some customers rely on for django session storage. It appears the mysql driver was there in OSP13 horizon image, but got removed in RHOSP 16.1. This causes issues for the customers during the upgrade from RHOSP 13 to 16.1. Version-Release number of selected component (if applicable): rhosp-rhel8/openstack-horizon:16.1 How reproducible: Configure local_settings to include: SESSION_ENGINE = 'django.contrib.sessions.backends.db' along with DB connection info. Actual results: This fails due to the lack of mysql driver in the horizon container image. Expected results: The db backend option for django session storage continues to work. Additional info:
If there driver was there previously, I think this is a regression, not an RFE.
This is apparently a side-effect of https://github.com/openstack/kolla/commit/0e2fc8a3b18c3d31b0ecdbfd3ac353d3643b1f5f#diff-8ca905493838c7cf8226d6d359915e973ec22fb23a45427eb49aec714aedcc77 It affects all releases based on train or later. I agree with the change itself, but also understand the desire to use database backed sessions. IMHO it'd make sense to add a package to support mariadb/mysql.
Raising severity due to the Regression keyword
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:4577