Description of problem: Not possible change vm cpu pinning via cli, so if you run this command: update vm test_vm --cpu-cpu_tune-vcpu_pin "vcpu_pin.vcpu=0, vcpu_pin.cpu_set=0" you will receive error: ERROR " vcpu_pin.cpu_set=0" is invalid segment at option "--cpu-cpu_tune-vcpu_pin". ================================================================================ Version-Release number of selected component (if applicable): av6 How reproducible: Always Steps to Reproduce: 1. See above 2. 3. Actual results: When trying to change cpu pinning under vm, appear error Expected results: vm updated success with new cpu pinning Additional info:
Note that spaces aren't allowed the value of the "--cpu-cpu_tune-vcpu_pin" option.
Artyom, Can you re-test the cli command without the space between parameters and determine if that resolves the issue?
My mistake, it update fine without space, but is still have problem when I try to run something like this: via UI 0#0-3,^1 works fine via CLI: update vm cpupin_vm1 --cpu-cpu_tune-vcpu_pin "vcpu_pin.vcpu=0,vcpu_pin.cpu_set=0-3,^1" "^1" is invalid segment at option "--cpu-cpu_tune-vcpu_pin". and also this one failed: update vm test_vm --cpu-cpu_tune-vcpu_pin "vcpu_pin.vcpu=0,vcpu_pin.cpu_set=1,2,3" UI parameters: 0#1,2,3
The problem is that the commas inside the value of the option confuse the parser. The solution in the proposed patch is to use the backslash character to escape the comma as separator, so if the value of the "cpu_set" item includes commas it can be written as follows: # update vm test_vm --cpu-cpu_tune-vcpu_pin "vcpu_pin.vcpu=0,vcpu_pin.cpu_set=1\,2\,3"
This issue has been fixed in version 3.5.0.0 of the upstream CLI. It will be fixed downstream with the next rebase.
This fix is contained in rhevm-cli-3.5.0.0-1.el6_5, already available in brew.
Can you please say me if patch already included to ovirt-engine-cli-3.5.0.2-1.el6.noarch? Because I see that command of format: update vm cpupin_vm1 --cpu-cpu_tune-vcpu_pin "vcpu_pin.vcpu=0,vcpu_pin.cpu_set=0\,1" Not really do any change on vm.
Yes, the change is included in that version of the package. However there is a different issue with the latest version of the Python SDK (bug 1122546) that basically means that all updates fail. If you want to test this bug you will need to downgrade the Python SDK to the previous version.
Verified on ovirt-engine-cli-3.5.0.4-1.20140820.git374a657.el6.noarch
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-2015-0185.html