Bug 1476119 - RESTAPI - Updating a storage connection on a VM with status down fails
RESTAPI - Updating a storage connection on a VM with status down fails
Status: NEW
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: ovirt-4.3.0
: ---
Assigned To: Maor
Raz Tamir
: Automation
Depends On:
  Show dependency treegraph
Reported: 2017-07-28 01:40 EDT by Avihai
Modified: 2017-10-18 05:06 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.3+

Attachments (Terms of Use)
engine & vdsm logs (1.58 MB, application/x-gzip)
2017-07-28 01:40 EDT, Avihai
no flags Details

  None (edit)
Description Avihai 2017-07-28 01:40:36 EDT
Created attachment 1305796 [details]
engine & vdsm logs

Description of problem:
Via RESTAPI try to update the storage connection to address from to fails.
REST response is : "Storage connection already exists"

Version-Release number of selected component (if applicable):
Engine - 4.2.0-0.0.master.20170723141021.git463826a.el7.centos
VDSM -  4.20.1-251

How reproducible:

Steps to Reproduce:
Automation TestCase5241:
1) Create NFS domain SD1
2) Create 2 VM's from template , Add to each VM  an additional ISCSI direct lun disk (50G size) to from storage address IP = .(Same storage have also other IP's to same luns as
3) Start both VM's to up & after it's active try to update ISCSI storage connection to address which fails as expected as VM's are active.
4) Change VM's to Down state 
5) VIa RESTAPI Try to update ISCSI storage connection to address .

Actual results:

2017-07-27 17:53:00,468 - MainThread - storageconnections - DEBUG - PUT request content is --  url:/ovirt-engine/api/storageconnections/f58d815a-d70f-4eae-94fc-27f2b2e87191 

2017-07-27 17:53:00,627 - MainThread - api_utils - ERROR - Failed to update element NOT as expected:
        Status: 409
        Reason: Conflict
        Detail: [Cannot edit Storage Connection. Storage connection already exists.]

Expected results:
Update storage connection should succeed .

Additional info:
Before the update ,on the the single host of the current DC you can see current connection to storage is to IP = :
iscsiadm -m session
tcp: [207],1 iqn.2008-05.com.xtremio:xio00153500071-514f0c50023f6c00 (non-flash)

GET REQUEST before&after the update shows the only storage connection did not change:
<storage_connection href="/ovirt-engine/api/storageconnections/f58d815a-d70f-4eae-94fc-27f2b2e87191" id="f58d815a-d70f-4eae-94fc-27f2b2e87191">

2017-07-27 17:53:00,619+03 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-14) [] Operation Failed: [Cannot edit Storage Connection. Storage connection already exists.]

2017-07-27 17:53:00,046+0300 INFO  (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call VM.destroy succeeded in 0.86 seconds (__init__:592)
2017-07-27 17:53:00,058+0300 ERROR (jsonrpc/4) [api] FINISH destroy error=Virtual machine does not exist: {'vmId': '86b4a238-cbd8-4867-9a2b-ad747c63f820'} (api:119)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 117, in method
    ret = func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 301, in destroy
    res = self.vm.destroy(gracefulAttempts)
  File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 129, in vm
    raise exception.NoSuchVM(vmId=self._UUID)
NoSuchVM: Virtual machine does not exist: {'vmId': '86b4a238-cbd8-4867-9a2b-ad747c63f820'}

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