Created attachment 1523019 [details] nova_glance & user settings Description of problem: changing user language settings in horizon dashboard is not reflected in glance image date format whereas same was reflected for nova instances. It seems user settings were not applied to glance images. Version-Release number of selected component (if applicable): How reproducible: changed user settings in horizon dashboard & check date format in instances creation under compute & image date format under images. both date formats are different. Steps to Reproduce: 1.check date format of instance & image 2. change user settings->language preferences from english to british english 3. check again date format of instance & image. Actual results: Date format not changed for glance images but applied(changed) for nova instances. Expected results: Date format should change for glance images also. Additional info:
Hello Ravi, Sorry for the late answer. I do not think Glance records the date in a language-specific format, but rather as a timestamp. My guess is that Horizon is responsible for formatting the date. Could we ping Horizon developers to get their opinion about this?
Moving to Horizon.
As far as I can determine, this is due to the Images view being ported to Angular, and the new Angular code ignoring locale while displaying dates. The instance overview view is still in Python, and it uses correct date handling. This can be worked around by using the old, Python version of that view (see https://docs.openstack.org/horizon/ocata/topics/settings.html#angular-features). I can't really give ETA on this, as we need to figure out a solution upstream that will work correctly for all the Angular-based views.
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 (Red Hat OpenStack Platform 16.1.9 bug fix and enhancement advisory), 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/RHBA-2022:8795