Bug 950684
| Summary: | RHEVM-CLI: on update, send only changed data rather than entire entity | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Barak Dagan <bdagan> | ||||
| Component: | ovirt-engine-cli | Assignee: | Ravi Nori <rnori> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Barak Dagan <bdagan> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.2.0 | CC: | acathrow, alukiano, bazulay, bdagan, iheim, jkt, juan.hernandez, mpastern, oramraz, pstehlik, Rhev-m-bugs, rnori | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | infra | ||||||
| Fixed In Version: | ovirt-3.4.0-alpha1 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1012985 (view as bug list) | Environment: | |||||
| Last Closed: | 2014-06-12 14:03:15 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1012985 | ||||||
| Attachments: |
|
||||||
same behavior for updating host's cluster. 1) set host to maintenance 2) update host using cluster-name 3) verify in the response that the host moved to the new cluster (fails) 4) update host using cluster-id 5) verify in the response that the host remain in the same cluster (passes) *** Bug 959879 has been marked as a duplicate of this bug. *** Verification failed on: # rpm -q ovirt-engine ovirt-engine-3.4.0-0.7.beta2.el6.noarch # rpm -qa | grep ovirt-engine | egrep 'sdk|cli' ovirt-engine-cli-3.4.0.3-1.el6.noarch ovirt-engine-sdk-python-3.4.0.3-1.el6.noarch VM moved from one cluster to the second, but with unrelevnt error: # list clusters id : d041e22a-65cb-436a-a52b-b7b604338f84 name : CL10 id : 1062b685-942f-4843-a736-50f6cbe93336 name : CL10a show vm vm1 | grep cluster cluster-id : 1062b685-942f-4843-a736-50f6cbe93336 # update vm vm1 --cluster-name CL10 ============================================================================================== ERROR =========================================================================================== status: 400 reason: Bad Request detail: There was an attempt to change VM values while the VM is not down. Please shut down the VM in order to modify these properties. ================================================================================================================================================================================================ # show vm vm1 | egrep 'cluster|state' cluster-id : d041e22a-65cb-436a-a52b-b7b604338f84 status-state : down When VM is not dowm, a different error returns: ]# action vm vm1 start job-id : e7b09171-28eb-4381-bcf0-48aeebf520ef status-state: complete vm-id : 23aef281-f08a-4371-8e3d-cbd695b53e99 [oVirt shell (connected)]# update vm vm1 --cluster-name CL10a ============================================================================================== ERROR =========================================================================================== status: 409 reason: Conflict detail: Cannot update a VM in this status. Try stopping the VM first. ================================================================================================================================================================================================ Hi Barak, seems to be working for me with ovirt-engine-3.4.0-0.7.beta2.fc19.noarch ovirt-engine-cli-3.4.0.3-1.fc19.noarch ovirt-engine-sdk-python-3.4.0.3-1.fc19.noarch Can you please check again. Can you repeat the test with the -d option and report the results? Verified on: ovirt-engine-3.4.0-0.7.beta2.el6.noarch ovirt-engine-cli-3.4.0.3-1.el6.noarch ovirt-engine-sdk-python-3.4.0.3-1.el6.noarch Will open a new one regarding that issue. Closing as part of 3.4.0 *** Bug 834202 has been marked as a duplicate of this bug. *** |
Created attachment 733778 [details] engine log Description of problem: When a vm is down, it can be shifted between different clusters under the same datacenter. using CLI this action works using cluster-id but has no affect using cluster-name. Version-Release number of selected component (if applicable): SF13 How reproducible: 100% Steps to Reproduce: setup: add datacenter --name 'test1' --version-minor 2 --version-major 3 --storage_type iscsi add cluster --name 'test1a' --data_center-name 'test1' --cpu-id 'Intel Conroe Family' add cluster --name 'test1b' --data_center-name 'test1' --cpu-id 'Intel Conroe Family' add vm --name 'vm_test1' --cluster-name 'test1a' --template-name 'Blank' REST: PUT /api/vms/ca41ba9b-c099-4afb-9c94-8ccdc3e8f387 HTTP/1.1 Accept: application/xml Content-type: application/xml <vm> <cluster href="/api/clusters/cd91e54b-2b14-4694-9fc4-0bd4222eab3d" id="cd91e54b-2b14-4694-9fc4-0bd4222eab3d" /> </vm> CLI: [RHEVM shell (connected)]# list clusters id : 8c7f0932-8fb9-48a9-a5b0-2ecb33be9ffb name : test1a id : cd91e54b-2b14-4694-9fc4-0bd4222eab3d name : test1b [RHEVM shell (connected)]# show vm vm_test1 | egrep 'name|cluster' name : vm_test1 cluster-id : cd91e54b-2b14-4694-9fc4-0bd4222eab3d [RHEVM shell (connected)]# update vm vm_test1 --cluster-id 8c7f0932-8fb9-48a9-a5b0-2ecb33be9ffb id : 9286fcda-973a-44f3-baf4-edf577d26bf0 name : vm_test1 cluster-id : 8c7f0932-8fb9-48a9-a5b0-2ecb33be9ffb [RHEVM shell (connected)]# show vm vm_test1 | egrep 'name|cluster' name : vm_test1 cluster-id : 8c7f0932-8fb9-48a9-a5b0-2ecb33be9ffb [RHEVM shell (connected)]# update vm vm_test1 --cluster-name 'test1b' id : 9286fcda-973a-44f3-baf4-edf577d26bf0 name : vm_test1 cluster-id : 8c7f0932-8fb9-48a9-a5b0-2ecb33be9ffb Actual results: vm remains on the same cluster when using update --cluster-name Expected results: expecting vm to move to the defined cluster Additional info: