RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1271152 - [All-Lang][virt-manager] some contents in virt-manager GUI and error messages are not localized
Summary: [All-Lang][virt-manager] some contents in virt-manager GUI and error messages...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.3
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1288337
TreeView+ depends on / blocked
 
Reported: 2015-10-13 09:19 UTC by Xiaodai Wang
Modified: 2016-11-04 01:59 UTC (History)
7 users (show)

Fixed In Version: virt-manager-1.4.0-2.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 01:59:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
p1.png (221.89 KB, image/png)
2016-07-25 10:24 UTC, zhoujunqin 		no flags Details
p2.png (232.14 KB, image/png)
2016-07-25 10:24 UTC, zhoujunqin 		no flags Details
p3.png (277.00 KB, image/png)
2016-07-25 10:25 UTC, zhoujunqin 		no flags Details
p4.png (223.69 KB, image/png)
2016-07-25 10:25 UTC, zhoujunqin 		no flags Details
when create a volume size large than available (171.77 KB, image/png)
2016-09-09 10:30 UTC, zhoujunqin 		no flags Details
p6:ZANATA search result (142.32 KB, image/png)
2016-09-09 10:31 UTC, zhoujunqin 		no flags Details
p7:new issue find (134.31 KB, image/png)
2016-09-09 10:31 UTC, zhoujunqin 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2269 0 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2016-11-03 13:34:19 UTC

Description Xiaodai Wang 2015-10-13 09:19:34 UTC 
Description of problem:
[All-Lang][virt-manager] some contents in virt-manager GUI and error messages are not localized

Version-Release number of selected component (if applicable):
# rpm -q virt-manager
virt-manager-1.2.1-8.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Set local language to russian:
# export LANG=ru_RU.UTF8
# echo $LANG
ru_RU.UTF8

2. Launch virt-manager to install a guest
Step1/5, choose install guest from HTTP, then click forward to next step.
Step2/5, fill a url and go to next step.
Step3/5, as default setting.
Step4/5, change default disk size from 9G to a large size(should larger than host left disk), such as 900G, then go to next step.
Step5/5, in last step choose a available disk size, and this step leave guest name with empty, click forward to install guest.


Actual results:
1. "xx GiB available in the default location", "Ready to begin the installation" are not translated. Please see "02-1.png" and "02-2.png".
2. "The requested volume capacity will exceed the available pool space when the volume is fully allocated.(xxx M requested capacity > xxx availabe)" is not traslated. Please see "03.png".
3. Some items (For example, "Performance", "Memory", "Boot Options", etc) in hardware deatils are not translated. And all items in add new hardware window are not translated. Please see "04.png".


Expected results:
All the string in GUI should be localized correctly.

Additional info:
You can refer bug 1228094 for more details.
Comment 3 Pavel Hrdina 2016-02-02 14:01:25 UTC 
Upstream commits:

commit 2f775b6bf0038fe1690d88c9f99cfc2a68318b73
Author: Cole Robinson <crobinso>
Date:   Wed Sep 23 16:28:46 2015 -0400

    Mark more UI strings as translatable

commit 028ec70fe782ec6c4e8324f5e569e7de3d8a836b
Author: Cole Robinson <crobinso>
Date:   Mon Sep 21 19:16:31 2015 -0400

    details: Mark more HW strings as translatable
    
    Reported-by: João Pirralha <joaopirralha>

commit 5f497b4d79c61179d236aa5147e115db3b2b1ab3
Author: Cole Robinson <crobinso>
Date:   Sun Aug 9 14:01:01 2015 -0400

    Mark a couple strings as translatable

There are still some strings that needs to be translated, this is what is fixed so far.
Comment 4 Pavel Hrdina 2016-02-06 15:27:59 UTC 
Upstream commit:

commit c39592ae7b9d0d09487a964ba75fc21d24b5a03f
Author: Pavel Hrdina <phrdina>
Date:   Fri Feb 5 16:18:16 2016 +0100

    localization: mark several strings as translatable
    
    Signed-off-by: Pavel Hrdina <phrdina>
Comment 5 Mike McCune 2016-03-28 23:17:33 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 7 zhoujunqin 2016-07-25 10:23:40 UTC 
I can reproduce this bug with version:
virt-manager-1.3.2-1.el7.noarch

Then try to verify this bug with new build:
virt-manager-1.4.0-1.el7.noarch
virt-install-1.4.0-1.el7.noarch
virt-manager-common-1.4.0-1.el7.noarch
qemu-kvm-rhev-2.6.0-15.el7.x86_64
libvirt-2.0.0-3.el7.x86_64
libvirt-python-2.0.0-1.el7.x86_64

Steps:

1. Set local language to russian:
# export LANG=ru_RU.UTF8
# echo $LANG
ru_RU.UTF8

2. Launch virt-manager to install a guest
Step1/5, choose install guest from HTTP, then click forward to next step.
Step2/5, fill a url and go to next step.
Step3/5, as default setting.
Step4/5, change default disk size from 9G to a large size(should larger than host left disk), such as 900G, then go to next step.
Step5/5, in last step choose a available disk size, and this step leave guest name with empty, click forward to install guest.

Results:
I. Bug issue in Comment 0, already been translated:
1. In Step5/5, "Ready to begin the installation" has been translated to ru_RU.
2. When turn to hardware details page and 'add new hardware window': All translated excepts 'TPM' and 'RNG'

II. Bug issue in Comment 0, always existing:
1. In Step3/5, 'MiB' not translate totally.(p1.png)
2. In Step4/5, 
Not translate
2.1 'xx GiB available in the default location'(p2.png)
2.2 '11.44 GiB Free/138.49 GiB In Use'(p3.png)
2.3 'There is not enough free space on the storage pool to create the volume.('xxx M requested capacity > xxx available)'(p4.png)

so Pavel, about above result please have a look, since according to ZANATA result, not translate to 100%, but issue in p1.png should already translated, since another 'MiB' above has translated, others please help have a look, thanks
Comment 8 zhoujunqin 2016-07-25 10:24:16 UTC 
Created attachment 1183681 [details]
p1.png
Comment 9 zhoujunqin 2016-07-25 10:24:44 UTC 
Created attachment 1183682 [details]
p2.png
Comment 10 zhoujunqin 2016-07-25 10:25:11 UTC 
Created attachment 1183687 [details]
p3.png
Comment 11 zhoujunqin 2016-07-25 10:25:38 UTC 
Created attachment 1183688 [details]
p4.png
Comment 12 Pavel Hrdina 2016-07-26 07:30:56 UTC 
(In reply to zhoujunqin from comment #7)
> 
> Steps:
> 
> 1. Set local language to russian:
> # export LANG=ru_RU.UTF8
> # echo $LANG
> ru_RU.UTF8
> 
> 2. Launch virt-manager to install a guest
> Step1/5, choose install guest from HTTP, then click forward to next step.
> Step2/5, fill a url and go to next step.
> Step3/5, as default setting.
> Step4/5, change default disk size from 9G to a large size(should larger than
> host left disk), such as 900G, then go to next step.
> Step5/5, in last step choose a available disk size, and this step leave
> guest name with empty, click forward to install guest.
> 
> Results:
> I. Bug issue in Comment 0, already been translated:
> 1. In Step5/5, "Ready to begin the installation" has been translated to
> ru_RU.
> 2. When turn to hardware details page and 'add new hardware window': All
> translated excepts 'TPM' and 'RNG'

Those are acronyms and they are not usually translated.

> 
> II. Bug issue in Comment 0, always existing:
> 1. In Step3/5, 'MiB' not translate totally.(p1.png)

This should be fixed.

> 2. In Step4/5, 
> Not translate
> 2.1 'xx GiB available in the default location'(p2.png)

The translation is marked as "fuzzy", but it will be fixed by our translation team.

> 2.2 '11.44 GiB Free/138.49 GiB In Use'(p3.png)

This should be fixed.

> 2.3 'There is not enough free space on the storage pool to create the
> volume.('xxx M requested capacity > xxx available)'(p4.png)

This is translated but there is a small typo in the code, this should be fixed.

> so Pavel, about above result please have a look, since according to ZANATA
> result, not translate to 100%, but issue in p1.png should already
> translated, since another 'MiB' above has translated, others please help
> have a look, thanks

I'll reuse this BZ to backport the patch that will fix those issues.
Comment 17 zhoujunqin 2016-09-09 10:28:21 UTC 
Try to verify this bug with build:
virt-manager-1.4.0-2.el7.noarch
libvirt-2.0.0-8.el7.x86_64
qemu-kvm-rhev-2.6.0-23.el7.x86_64

Steps as Comment 7.

> > II. Bug issue in Comment 0, always existing:
> > 1. In Step3/5, 'MiB' not translate totally.(p1.png)
> 
> This should be fixed.

'MiB' not translated.


> > 2.2 '11.44 GiB Free/138.49 GiB In Use'(p3.png)
> 
> This should be fixed.

Has not translated.

> 
> > 2.3 'There is not enough free space on the storage pool to create the
> > volume.('xxx M requested capacity > xxx available)'(p4.png)
> 
> This is translated but there is a small typo in the code, this should be
> fixed.

Not fixed yet, please according to p5.png and p6.png, i think some word missed, but not sure.

and what's more i also find another question by operation but don't know how to reproduce, please help check p6.png, thanks.
Comment 18 zhoujunqin 2016-09-09 10:30:04 UTC 
Created attachment 1199375 [details]
when create a volume size large than available
Comment 19 zhoujunqin 2016-09-09 10:31:01 UTC 
Created attachment 1199376 [details]
p6:ZANATA search result
Comment 20 zhoujunqin 2016-09-09 10:31:40 UTC 
Created attachment 1199377 [details]
p7:new issue find
Comment 24 errata-xmlrpc 2016-11-04 01:59:59 UTC 
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://rhn.redhat.com/errata/RHBA-2016-2269.html
Note You need to log in before you can comment on or make changes to this bug.