Hide Forgot
Created attachment 796066 [details] test logs (vdsm, engine, server etc.) Description of problem: <port> tag is required when creating an iscsi storage connection. However, when you try the following call: <storage_connection> <target>iqn.1992-04.com.emc:cx.ckm00121000438.b7</target> <type>iscsi</type> <port></port> <address>10.35.160.107</address> </storage_connection> it succeeds and the created connection has port = 0: <storage_connections> <storage_connection href="/api/storageconnections/726a17f2-67c2-41a0-9fbc-9fed23a70271" id="726a17f2-67c2-41a0-9fbc-9fed23a70271"> <address>10.35.160.107</address> <type>iscsi</type> <port>0</port> <target>iqn.1992-04.com.emc:cx.ckm00121000438.b7</target> </storage_connection> </storage_connections> Also, if you try to change existing connection and specified empty tag <port>, it will be set to 0. Version-Release number of selected component (if applicable): is13 How reproducible: 100%, automated tests: http://jenkins.qa.lab.tlv.redhat.com:8080/view/Storage/view/3.3/job/3.3-storage_storage_connections_iscsi-iscsi-rest/54/ Steps to Reproduce: 1. try to create an iscsi storage connection and specify empty <port> tag Actual results: connection is created with port = 0 Expected results: the operation should fail with appropriate error message
Allon, can you merge this change so that Ravi can backport it to 3.4? If not please retarget to 3.4.1 or 3.5.
(In reply to Juan Hernández from comment #3) > Allon, can you merge this change so that Ravi can backport it to 3.4? If not > please retarget to 3.4.1 or 3.5. I merged it upstream. Considering the timing in 3.4's lifecycle and the severity of this issue, I pushed it out to 3.5.
Tried to create a storage connection with no value under port parameter and it failed with the following error: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <fault> <reason>Operation Failed</reason> <detail>[Invalid value for port, should be an integer greater than 0.]</detail> </fault> Verified using ovirt-engine-3.5-beta ovirt-engine-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch ovirt-engine-restapi-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch
oVirt 3.5 has been released and should include the fix for this issue.