[Users] Attaching export domain to dc fails

[Patrick Hurrelmann]

Hi list,

in one datacenter I'm facing problems with my export storage. The dc is
of type single host with local storage. On the host I see that the nfs
export domain is still connected, but the engine does not show this and
therefore it cannot be used for exports or detached.

Trying to add attach the export domain again fails. The following is
logged n vdsm:

Thread-1902159::ERROR::2013-01-24
17:11:45,474::task::853::TaskManager.Task::(_setError)
Task=`4bc15024-7917-4599-988f-2784ce43fbe7`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 861, in _run
    return fn(*args, **kargs)
  File "/usr/share/vdsm/logUtils.py", line 38, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/storage/hsm.py", line 960, in attachStorageDomain
    pool.attachSD(sdUUID)
  File "/usr/share/vdsm/storage/securable.py", line 63, in wrapper
    return f(self, *args, **kwargs)
  File "/usr/share/vdsm/storage/sp.py", line 924, in attachSD
    dom.attach(self.spUUID)
  File "/usr/share/vdsm/storage/sd.py", line 442, in attach
    raise se.StorageDomainAlreadyAttached(pools[0], self.sdUUID)
StorageDomainAlreadyAttached: Storage domain already attached to pool:
'domain=cd23808b-136a-4b33-a80c-f2581eab022d,
pool=d95c53ca-9cef-4db2-8858-bf4937bd8c14'

It won't let me attach the export domain saying that it is already
attached. Manually umounting the export domain on the host results in
the same error on subsequent attach.

This is on CentOS 6.3 using Dreyou's rpms. Installed versions on host:

vdsm.x86_64                                 4.10.0-0.44.14.el6
vdsm-cli.noarch                             4.10.0-0.44.14.el6
vdsm-python.x86_64                          4.10.0-0.44.14.el6
vdsm-xmlrpc.noarch                          4.10.0-0.44.14.el6

Engine:

ovirt-engine.noarch                         3.1.0-3.19.el6
ovirt-engine-backend.noarch                 3.1.0-3.19.el6
ovirt-engine-cli.noarch                     3.1.0.7-1.el6
ovirt-engine-config.noarch                  3.1.0-3.19.el6
ovirt-engine-dbscripts.noarch               3.1.0-3.19.el6
ovirt-engine-genericapi.noarch              3.1.0-3.19.el6
ovirt-engine-jbossas711.x86_64              1-0
ovirt-engine-notification-service.noarch    3.1.0-3.19.el6
ovirt-engine-restapi.noarch                 3.1.0-3.19.el6
ovirt-engine-sdk.noarch                     3.1.0.5-1.el6
ovirt-engine-setup.noarch                   3.1.0-3.19.el6
ovirt-engine-tools-common.noarch            3.1.0-3.19.el6
ovirt-engine-userportal.noarch              3.1.0-3.19.el6
ovirt-engine-webadmin-portal.noarch         3.1.0-3.19.el6
ovirt-image-uploader.noarch                 3.1.0-16.el6
ovirt-iso-uploader.noarch                   3.1.0-16.el6
ovirt-log-collector.noarch                  3.1.0-16.el6

How can this be recovered to a sane state? If more information is
needed, please do not hesitate to request it.

Thanks and regards
Patrick

-- 
Lobster LOGsuite GmbH, Münchner Straße 15a, D-82319 Starnberg

HRB 178831, Amtsgericht München
Geschäftsführer: Dr. Martin Fischer, Rolf Henrich
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vdsm_export.log
Type: text/x-log
Size: 20284 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130124/745349b3/attachment-0001.bin>