The 'flavor' field is Not available after launching vm

When launching one vm and its status is active, but the 'flavor' field displayed "Not available".

After refreshing the page, got correct flavor.

$ git log
commit 9d1bb3626bc1dbcf29a55aeb094f4350067317cd (HEAD -> master, tag: 20.2.0, origin/master, origin/HEAD)
Author: Akihiro Motoki <email address hidden>
Date: Tue Oct 26 09:18:16 2021 +0900

    Allow both Django 2.2 and 3.2 for smooth transition

    I believe we need the following steps and it is what I did in past
    when we bump the Django minimum version.

    1. (already done) update global-requirements.txt to allow horizon to
       update requirements.txt to include Django 3.2.
    2. specify the required Django version which includes both 2.2 and 3.2
       (at this point upper-constraints uses 2.2)
    3. update upper-constraints.txt in the requirements repo to use Django 3.2
    4. bump the min version of Django in horizon

    (optionally) update non-primary-django tests to include non-primary versions of
    Django. It seems you drops 2.2 support together when we support 3.2, so perhaps
    this step is not the case though.

    https://review.opendev.org/c/openstack/horizon/+/811412 directly updated
    the min version to Django 3.2 which is incompatible with the global
    upper-constraints.txt.
    To avoid this, https://review.opendev.org/c/openstack/horizon/+/815206 made
    almost all tests non-voting. I am not a fan of such approach and believe
    there is a way to make the transition of Django version more smoothly.

    ---

    This commit reverts the zuul configuration changes in
    https://review.opendev.org/c/openstack/horizon/+/815206 and
    https://review.opendev.org/c/openstack/horizon/+/811412.

    horizon-tox-python3-django32 is voting now as we are making it
    the default version.

    Change-Id: I60bb672ef1b197e657a8b3bd86d07464bcb1759f