The images built for Horiozon have their translations missing.
This is a regression of https://bugzilla.redhat.com/show_bug.cgi?id=1729770 which was fixed with https://bugzilla.redhat.com/show_bug.cgi?id=1729770
On OSP15, we had a patch that looks like this: @@ -29,10 +27,12 @@ RUN usermod --append --home /var/lib/horizon --groups kolla horizon \ - -RUN dnf -y install glibc-all-langpacks gettext httpd mod_ssl openstack-dashboar d openstack-heat-ui openstack-ironic-ui openstack-manila-ui openstack-neutron-lb aas-ui openstack-octavia-ui openstack-sahara-ui python3-mod_wsgi \ - && dnf clean all && rm -rf /var/cache/dnf \ - && rpm -ql openstack-dashboard +# Work around missing languages - bug #1729770 +RUN mv /etc/rpm/macros.image-language-conf / \ + && dnf -y install openstack-dashboard \ + && mv /macros.image-language-conf /etc/rpm \ + && dnf -y install gettext httpd mod_ssl openstack-heat-ui openstack-ironic- ui openstack-manila-ui openstack-neutron-lbaas-ui openstack-octavia-ui openstack -sahara-ui python3-mod_wsgi \ + && dnf clean all && rm -rf /var/cache/dnf The problem is we had to move the macro.image-language-conf out of place and move it back so DNF didn't delete the translations.
The macro.image-language-conf tells DNF to delete most of the translations, so you have to move it before the transaction and move it back after. If we were to fix this in openstack-base, a simple solution would be to remove the file.
The problem with removing the file in "base" is that every openstack image will grow in size, potentially a lot. That's why I did the above hack to avoid leaving it "missing".
*** Bug 1784897 has been marked as a duplicate of this bug. ***
*** Bug 1781252 has been marked as a duplicate of this bug. ***
*** Bug 1788410 has been marked as a duplicate of this bug. ***
I'm +1 on moving forward with the workaround to prevent the regression.
This is fixed in the latest puddle.
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, 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-2020:0429