Post login services region is not set

[Gabriel Samfira]

In a multi-region OpenStack deployment, horizon fails to remember the selected services region post-login. The cookie is properly set, but it's never used in the login_view to set the request.session['services_region'] value. The result is that the selected region is reset to whichever region is first in the list, even though the services_region cookie is different. Clicking on the available regions and switching to the correct one, will leave the services_region cookie intact, but properly set the value in the session.

This causes confusion for users that log in and find themselves on a different region than previously selected.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/horizon/+/899228

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/horizon/+/899228
Committed: https://opendev.org/openstack/horizon/commit/66b5713296e7bd9caabe8dd84bde644435b7712a
Submitter: "Zuul (22348)"
Branch: master

commit 66b5713296e7bd9caabe8dd84bde644435b7712a
Author: Gabriel Adrian Samfira <email address hidden>
Date: Wed Oct 25 10:37:35 2023 +0300

    Properly set session value for services_region

    Currently, the value stored in the services_region cookie is ignored
    when logging into horizon. This causes confusion for users that have
    previously selected one region, to find themselves in a different
    region after their token expires and are forced to log in again.

    This change sets the services_region session value to the value present
    in the cookie, with a fallback to the login region.

    Closes-bug: #2040455

    Change-Id: I051648844bf8dffce792ff553e9949285b1be6d4
    Signed-off-by: Gabriel Adrian Samfira <email address hidden>

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/horizon 24.0.0 release.