Master data domain must be reachable in order for the DC to be up.
Export domain shouldn't affect the dc status.
Are you sure that you've created the export domain as an export domain, and not as a
regular nfs?
----- Original Message -----
From: "Giorgio Bersano" <giorgio.bersano(a)gmail.com>
To: "Meital Bourvine" <mbourvin(a)redhat.com>
Cc: "users(a)ovirt.org" <Users(a)ovirt.org>
Sent: Tuesday, March 4, 2014 4:16:19 PM
Subject: Re: [Users] Data Center Non Responsive / Contending
2014-03-04 14:48 GMT+01:00 Meital Bourvine <mbourvin(a)redhat.com>:
> StorageDomainDoesNotExist: Storage domain does not exist:
> (u'1810e5eb-9eb6-4797-ac50-8023a939f312',)
>
> What's the output of:
> lvs
> vdsClient -s 0 getStorageDomainsList
>
> If it exists in the list, please run:
> vdsClient -s 0 getStorageDomainInfo 1810e5eb-9eb6-4797-ac50-8023a939f312
>
I'm attaching a compressed archive to avoid mangling by googlemail client.
Indeed the NFS storage with that id is not in the list of available
storage as it is brought up by a VM that has to be run in this very
same cluster. Obviously it isn't running at the moment.
You find this in the DB:
COPY storage_domain_static (id, storage, storage_name,
storage_domain_type, storage_type, storage_domain_format_type,
_create_date, _update_date, recoverable, last_time_used_as_master,
storage_description, storage_comment) FROM stdin;
...
1810e5eb-9eb6-4797-ac50-8023a939f312
11d4972d-f227-49ed-b997-f33cf4b2aa26 nfs02EXPORT 3 1
0 2014-02-28 18:11:23.17092+01 \N t 0 \N
\N
...
Also, disks for that VM are carved from the Master Data Domain that is
not available ATM.
To say in other words: I thought that availability of an export domain
wasn't critical to switch on a Data Center. Am I wrong?
Thanks,
Giorgio.