SonarQube showing internal element names after upgrade

On our self-hosted instance of SonarQube running in a docker container, we recently upgraded from 8.9.0-community to 9.2.4-enterprise and the web ui is now showing some internal element names. It looks like it’s perhaps specific to anything new that’s been added by upgrading to Enterprise, but not I’m not 100% sure on that. The DB migration after the upgrade succeeded with no issues. I do not see any pertinent information in the web or main logs. We are using a Postgres 13.3 RDS instance for the DB.

Here is an example of what we’re seeing:

image

Is there somewhere else I should be looking to troubleshoot this? Or any other ideas. It seems related to the upgrade, but I didn’t see any special notes needed in the documentation for upgrading.

1 Like

Anyone have any thoughts? We’re in a trial period and this really ruins the elegant look of the SonarQube UI and my chances of convincing anyone to use this product.

Hi,

Welcome to the community!

First, thanks for your kind words about the UI!

Regarding the localization strings, this should just work. I wonder if there are any errors in your browser console? Also, have you tired doing a force-refresh? I believe the localization string data comes from a web service. Maybe your browser is caching it?

 
Ann

Hi Ann,

I’ve tried using an incognito window within Chrome, force-reshing, using Edge and all have the same results. I also have other users seeing the same and this only showed up after the upgrade. Certain areas have more of this than others. The entire audit logs section shows like this:

image

Another note - I actually just did a fresh install of 9.2.4-enterprise on a branch new ec2 instance, with a brand new EBS volume and brand new postgres RDS instance and am getting the same issue. Perhaps this is actually a bug in this version? I will try upgrading as I believe something newer than 9.2.4 is out now.

Upgrading to 9.3.0 fixed this issue, so this appears to be a bug with 9.2.4 (at least).

1 Like

Hi,

I wasn’t able to reproduce this with either the zip or Docker distributions of 9.2.4 Enterprise.

But I’m glad you solved it. (And glad you upgraded to latest! :smiley: )

 
Ann

1 Like

Hi,
I git the same issue on sonarqube-9.6.1.59531, upgrade to sonarqube-9.7.1.62043 didn’t fix the problem.

Example of translation keys that show up:

  • project_activity.graphs.choose_type
  • issues.facet.period
  • hotspots.status_option.ACKNOWLEDGED

No js errors.

Hi @obriat,

What 3rd-party plugins do you have installed? My memory is fuzzy, but I believe there’s one that triggers this behavior for some reason.

 
Ann