Bug 1462075 - It's not properly translated CPU_HOTPLUG_TOPOLOGY_INVALID, and also similar for MAX_THREADS_PER_CPU
It's not properly translated CPU_HOTPLUG_TOPOLOGY_INVALID, and also similar f...
Status: NEW
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt (Show other bugs)
4.1.3.2
x86_64 Linux
medium Severity medium (vote)
: ---
: ---
Assigned To: Michal Skrivanek
Pavel Stehlik
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-16 02:19 EDT by jiyan
Modified: 2018-03-14 05:31 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: i18n
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description jiyan 2017-06-16 02:19:49 EDT
Description of problem:
It's not properly translated CPU_HOTPLUG_TOPOLOGY_INVALID, and also similar for MAX_THREADS_PER_CPU.

Version-Release number of selected component (if applicable):
RHV-M server:
rhevm-4.1.3.2-0.1.el7.noarch
ovirt-engine-setup-plugin-ovirt-engine-4.1.3.2-0.1.el7.noarch

RHV-M register host:
qemu-kvm-rhev-2.9.0-9.el7.x86_64
libvirt-3.2.0-9.el7.x86_64
kernel-3.10.0-679.el7.x86_64
vdsm-4.19.18-1.el7ev.x86_64


How reproducible:
100%

Steps to Reproduce:
1.Edit the 'MAX_THREADS_PER_CPU' parameter with wrong value,the error message about "MAX_THREADS_PER_CPU" as following:

Operation Canceled
Error while executing action: 
vm3:
ACTION_TYPE_FAILED_MAX_THREADS_PER_CPU

2.Edit the four parameters of 'CPU_HOTPLUG_TOPOLOGY' with wrong value, The error message about "CPU_HOTPLUG_TOPOLOGY" as following:

Operation Canceled
Error while executing action: 
vm1:
CPU_HOTPLUG_TOPOLOGY_INVALID


Actual results:
Refer to the steps.


Expected results:
The error message above is supposed to be translated into a proper sentence.


Additional info:
Comment 1 Sandro Bonazzola 2017-06-16 02:24:07 EDT
(In reply to jiyan from comment #0)
> Description of problem:
> It's not properly translated CPU_HOTPLUG_TOPOLOGY_INVALID, and also similar
> for MAX_THREADS_PER_CPU.

what's "it"? The engine web admin interface?


> Version-Release number of selected component (if applicable):
> RHV-M server:
> rhevm-4.1.3.2-0.1.el7.noarch
> ovirt-engine-setup-plugin-ovirt-engine-4.1.3.2-0.1.el7.noarch
> 
> RHV-M register host:
> qemu-kvm-rhev-2.9.0-9.el7.x86_64
> libvirt-3.2.0-9.el7.x86_64
> kernel-3.10.0-679.el7.x86_64
> vdsm-4.19.18-1.el7ev.x86_64
> 
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1.Edit the 'MAX_THREADS_PER_CPU' parameter with wrong value,the error
> message about "MAX_THREADS_PER_CPU" as following:

Edit where?


> Operation Canceled
> Error while executing action: 
> vm3:
> ACTION_TYPE_FAILED_MAX_THREADS_PER_CPU
> 
> 2.Edit the four parameters of 'CPU_HOTPLUG_TOPOLOGY' with wrong value, The
> error message about "CPU_HOTPLUG_TOPOLOGY" as following:

Edit where?


> 
> Operation Canceled
> Error while executing action: 
> vm1:
> CPU_HOTPLUG_TOPOLOGY_INVALID
> 
> 
> Actual results:
> Refer to the steps.
> 
> 
> Expected results:
> The error message above is supposed to be translated into a proper sentence.
> 
> 
> Additional info:
Comment 2 jiyan 2017-06-16 02:50:32 EDT
Sorry for a unclear description.

> Description of problem:
> It's not properly translated CPU_HOTPLUG_TOPOLOGY_INVALID, and also similar
> for MAX_THREADS_PER_CPU.
> what's "it"? The engine web admin interface?

Yes, I mean the error info in RHV-M GUI web page.



> 2.Edit the four parameters of 'CPU_HOTPLUG_TOPOLOGY' with wrong value, The
> error message about "CPU_HOTPLUG_TOPOLOGY" as following:
> Edit where?

I mean the configuration for a vm in RHV-M, you can edit the vm, in 'system' configuration, 'Total Virtual CPUs', 'Virtual Sockets', 'Cores per Virtual Socket' and 'threads per Core' four parameters.

For example:
A vm can running normally with the configuration that the values of 'Total Virtual CPUs', 'Virtual Sockets', 'Cores per Virtual Socket' and 'threads per Core' are 8, 2, 1, 4.
Then change the values of 'Total Virtual CPUs', 'Virtual Sockets', 'Cores per Virtual Socket' and 'threads per Core' to 64, 16, 1, 4.
It will raise error as above, such error info is not easy to read, and should be translated into a proper sentence.

And same to the Step-1 for "MAX_THREADS_PER_CPU".

Note You need to log in before you can comment on or make changes to this bug.