Description of problem:
Menu item Configure -> Host Groups has been changed to "Host Group" for no obvious reason. The commit with a bad translation is from year 2016 so I have no idea how that happened only for 6.5. However, it seems incorrect, given that the other items are in plural and there seems to be no tracker for this change.
Version-Release number of selected component (if applicable):
Reproduced on 6.5 snap 3.
Discussed this with Ondra who already has a fix.
I believe this and Bug 1651324 share the same root cause. Adding the other one to tracker - they aren't strictly duplicates, but solving one will hopefully solve another.
as you have discussed it and have fix already, can you share how you will fix it and how this happened?
Since source of bad translation seems to be file last updated 2 years ago, I'm afraid something in our build pipeline might be broken. That would be very serious issue that could cause hard to discover bugs in many unrelated parts of Satellite. Can we rule that out?
I don't know a lot about the issue but:
1) msgid="Host Groups"
2) msgstr="Host Group"
3) Vertical navigation has been somehow reworked lately (source: mhulan).
=> I suppose the old one used msgid while the other uses (imo correctly) msgstr. But again, this might not be true at all.
I don't know how that happened, but most likely this is unrelated to vert nav change that dropped HTML id attributes. This look more like a clash between upstream/downstream translations? Perhaps Eric or someone from his team knows, when and how we pull translation files during the build.
Connecting redmine issue http://projects.theforeman.org/issues/25538 from this bug
Upstream bug assigned to firstname.lastname@example.org
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25538 has been resolved.
FailedQA on Sat 6.5 snap 13.
The text is still "Host Group".
Verified with Sat 6.5 snap 20.
The menu item now says "Host Groups".
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.