VMware Solutions Discussions

XML Error creating NFS Datastore

Sebastian_Goetze
3,120 Views

Hi All,

we're trying to create a NFS datastore in our lab: VSC 4.2, ONTAP 7m 8.2 sim, ESX 5.1u1, vCenter 5.1u1.

We do have 2 sims in the environment, different serials, both possible to add to the VSC, no problems there.

One sim exhibits the following problem:

(Malformed XML)


On the console we see:

Thu Sep 26 17:11:06 CEST [SC2:app.log.err:error]: vc: Provisioning and Cloning Capability 4.2: (0)  : Failed to export volume

Thu Sep 26 17:13:02 CEST [SC2:app.log.info:info]: vc: Provisioning and Cloning Capability 4.2: (0)  : Provisioning and Cloning Capability v4.2 createDatastore: vcUserId: Administrator VMware Version:5.1.0 Build: 1064983 API: 5.1 datastoreName: newDatastore datastoreSizeInMB: 20480 autoGrow: false growIncrement: null maxGrowSize: null containerName: aggr_data thinProvision: true protocol: NFS datastore cluster: null lun prefix: null

Thu Sep 26 17:13:03 CEST [SC2:app.log.info:info]: vc: Provisioning and Cloning Capability 4.2: (0)  : About to create flexvol(s) for NFS based datastores.

Thu Sep 26 17:13:10 CEST [SC2:app.log.info:info]: vc: Provisioning and Cloning Capability 4.2: (0)  : vcUserId Administrator requested mount of newDatastore

Thu Sep 26 17:13:11 CEST [SC2:app.log.info:info]: vc: Provisioning and Cloning Capability 4.2: (0)  : Administrator requested newDatastore, but the task had an issue. We will clean up the unused volume.

Thu Sep 26 17:13:21 CEST [SC2:sis.op.stopped:error]: SIS operation for /vol/newDatastore has stopped

Thu Sep 26 17:13:24 CEST [SC2:wafl.vvol.offline:info]: Volume 'newDatastore' has been set temporarily offline

Thu Sep 26 17:13:25 CEST [SC2:wafl.vvol.destroyed:info]: Volume newDatastore destroyed.

Thu Sep 26 17:13:30 CEST [SC2:app.log.err:error]: vc: Provisioning and Cloning Capability 4.2: (0)  : Failed to export volume

Is this a (known ?) bug?

(Root priviledges, everything green on host connection, ... we checked all known corners)

Thanks in advance

Sebastian

1 ACCEPTED SOLUTION

Sebastian_Goetze
3,120 Views

Aaaargh,

we found it: When setting up the second Sim, the colleague had put a space in the 'administration host'.

That was kinda hard to see...

The empty (sort of) host name resulted in the malformed XML.

Maybe something to check for? (Also in the CLI 'setup' wizard?)

Anyway, it works now.

Sebastian    

View solution in original post

1 REPLY 1

Sebastian_Goetze
3,121 Views

Aaaargh,

we found it: When setting up the second Sim, the colleague had put a space in the 'administration host'.

That was kinda hard to see...

The empty (sort of) host name resulted in the malformed XML.

Maybe something to check for? (Also in the CLI 'setup' wizard?)

Anyway, it works now.

Sebastian    

Public