Bug 1324813

Summary: Unable to update storage connection of data domain
Product: [oVirt] ovirt-engine Reporter: Raz Tamir <ratamir>
Component: BLL.StorageAssignee: Allon Mureinik <amureini>
Status: CLOSED NOTABUG QA Contact: Aharon Canan <acanan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.6.5.1CC: bugs
Target Milestone: ---Keywords: Automation, Regression, Reopened
Target Release: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-07 14:50:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
engine and vdsm logs none

Description Raz Tamir 2016-04-07 11:04:22 UTC
Created attachment 1144679 [details]
engine and vdsm logs

Description of problem:
When trying to update a storage connection of data domain I'm getting the error:
2016-04-07 13:47:02,841 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetStorageDomainStatsVDSCommand] (ajp-/127.0.0.1:8702-4) [1dec583e] Failed in 'GetStorageDomainStatsVDS' method
2016-04-07 13:47:02,852 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp-/127.0.0.1:8702-4) [1dec583e] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VDSM host_mixed_1 command failed: Error in storage domain action: ('sdUUID=23e52482-aa90-4a7f-8a6f-359cca291cad',)

The flow starts at:
2016-04-07 13:47:00,110 INFO  [org.ovirt.engine.core.bll.storage.UpdateStorageServerConnectionCommand] (ajp-/127.0.0.1:8702-4) [1dec583e] Running command: UpdateStorageServerConnectionCommand internal: false. Entities affected :  ID: aaa00000-0000-0000-0000-123456789aaa Type: SystemAction group CREATE_STORAGE_DOMAIN with role type ADMIN
2016-04-07 13:47:00,112 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (ajp-/127.0.0.1:8702-4) [1dec583e] START, ConnectStorageServerVDSCommand(HostName = host_mixed_1, StorageServerConnectionManagementVDSParameters:{runAsync='true', hostId='4712d1e6-8ed3-4ad9-8dc9-dfcc0f8fa9d4', storagePoolId='00000000-0000-0000-0000-000000000000', storageType='NFS', connectionList='[StorageServerConnections:{id='c8c0dedc-09ec-4cf7-a9e9-6fcd2299fa0d', connection='10.35.64.11:/vol/RHEV/Storage/storage_jenkins_ge5_nfs_3', iqn='null', vfsType='null', mountOptions='null', nfsVersion='V3', nfsRetrans='9', nfsTimeo='900', iface='null', netIfaceName='null'}]'}), log id: 7339aca7



Version-Release number of selected component (if applicable):
rhevm-3.6.5.1-0.1.el6.noarch
vdsm-4.17.25-0.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Have an nfs data domain (not master)
2. On server side, create new share with correct owner perms (36:kvm)
3. Copy the content of nfs domain into the new path
4. Run REST command [1]

[1] PUT api/storageconnections/c8c0dedc-09ec-4cf7-a9e9-6fcd2299fa0d

<storage_connection>
    <address>SERVER_IP</address>
    <type>nfs</type>
    <path>PATH/TO/NEW/NFS/SHARE</path>
    <nfs_version>V3</nfs_version>
    <nfs_timeo>900</nfs_timeo>
    <nfs_retrans>9</nfs_retrans>
    <host>
        <name>HOST_NAME</name>
    </host>
</storage_connection>

Response 400:

<fault>
    <reason>Operation Failed</reason>
    <detail>[Error in storage domain action]</detail>
</fault>

Actual results:


Expected results:


Additional info:

Comment 1 Allon Mureinik 2016-04-07 11:26:15 UTC
(In reply to ratamir from comment #0)

> Steps to Reproduce:
> 1. Have an nfs data domain (not master)
> 2. On server side, create new share with correct owner perms (36:kvm)
> 3. Copy the content of nfs domain into the new path
> 4. Run REST command [1]
This was never supported. In fact, if it used to work, that's the bug there.

Comment 3 Red Hat Bugzilla Rules Engine 2016-04-07 11:33:55 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 6 Red Hat Bugzilla Rules Engine 2016-04-07 12:08:23 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.