Created attachment 1571567 [details] jpn_managed_block_unlocalized Description of problem: The strings on storage -> disks -> add ->managed block section. The section name as well as the warning message "There are no available Managed Block storage domains that you have permissions to create a disk on in the relevant Data Center." is not localized for all locales. Version-Release number of selected component (if applicable): 4.3 How reproducible: always Steps to Reproduce: 1. Login to admin portal with any non-English locale 2. Go to storage -> disks -> add -> managed block 3. Observe the section name and the warning message at the bottom. Actual results: Mentioned Strings are not localized Expected results: all the strings should be localized. Additional info: Please refer attached screenshot.
BZ1737612, the latest translation update, contains the translation updates that will fix this bug. The text in question is already localizable but translations had not yet been included in any previous translation update.
(In reply to Scott Dickerson from comment #1) > BZ1737612, the latest translation update, contains the translation updates > that will fix this bug. The text in question is already localizable but > translations had not yet been included in any previous translation update. can we mark this BZ as modified now that https://gerrit.ovirt.org/#/c/102990/ is merged.
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No relevant external trackers attached] For more info please contact: infra
Moved to ON_QA since BZ1737612, which fixes this BZ, is also ON_QA.
All of the mentioned strings are localized for all supported languages, therefore verified. It is not localized for Czech though, that's why I'm creating a new BZ 1750293 for the community.
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.