[Users] Old storage domain ID left behind in master storage domain's metadata

[Nir Soffer]

----- Original Message -----
> From: "Boyan Tabakov" <blade at alslayer.net>
> To: users at ovirt.org
> Sent: Tuesday, February 25, 2014 12:59:09 PM
> Subject: [Users] Old storage domain ID left behind in master storage	domain's metadata
> 
> Hello,
> 
> I started with an all-in-one installation of ovirt 3.3.2 on a FC19 host.
> After the initial setup was done, I created a new datacenter, cluster
> and storage domain in the engine and moved the single host in the engine
> to the new cluster. After that I deleted the automatically created
> storage domain, local datacenter, etc.
> 
> It seems, however, that the new master storage domain still contains
> some references to the now removed old storage domains in its metadata.
> Here's the metadata, extracted from the tags of the VG. I got them using
> vgs:
> 
> MDT_DESCRIPTION=StorageDomainX
> MDT_LOCKPOLICY=
> MDT_PV0=pv:36090a098103b1821532d057a5a0120d4&44&uuid:xreVSW-NmjD-MUqk-jucQ-Hrbs-KRe8-P93tn3&44&pestart:0&44&pecount:798&44&mapoffset:0
> MDT_TYPE=ISCSI
> MDT_LOGBLKSIZE=512
> MDT_VGUUID=npukh2-ulUm-MEbj-T0TZ-0kDX-pUkp-2hJEKo
> MDT_LEASERETRIES=3
> MDT_IOOPTIMEOUTSEC=10
> MDT_LOCKRENEWALINTERVALSEC=5
> MDT_SDUUID=3307f6fa-dd58-43db-ab23-b1fb299006c7
> MDT_PHYBLKSIZE=512
> MDT_CLASS=Data
> MDT_VERSION=3
> RHAT_storage_domain
> MDT_POOL_UUID=61f15cc0-8bba-482d-8a81-cd636a581b58
> MDT_ROLE=Master
> MDT_MASTER_VERSION=44
> MDT_POOL_DESCRIPTION=DataCenterX
> MDT_POOL_DOMAINS=ec4ba43a-e334-4ce2-90d1-86e5a6da071d:Active&44&a7af75fe-b96a-4ebe-8903-5743a8176311:Active&44&ff33856e-e00f-4be8-9456-8e47c592f82f:Active&44&3307f6fa-dd58-43db-ab23-b1fb299006c7:Active
> MDT_PV1=pv:36090a09810bb99fefb2da57b94332027&44&uuid:UMUs49-GvEF-IOgZ-p6jD-yP1r-dpnd-syawJz&44&pestart:0&44&pecount:798&44&mapoffset:798
> MDT_POOL_SPM_ID=1
> MDT_POOL_SPM_LVER=30
> MDT__SHA_CKSUM=ad43ad855d386b103a672a0801a932a9ee115ed7
> 
> Notably, see MDT_POOL_DOMAINS. Domains
> ec4ba43a-e334-4ce2-90d1-86e5a6da071d and
> a7af75fe-b96a-4ebe-8903-5743a8176311 no longer exist in the engine (were
> removed from admin UI).
> 
> Their presence in the metadata causes vdsmd to repeatedly try to access
> those domains, resulting in constant error messages in the log that the
> domains don't exist.
> 
> Any advice on how to properly clean up the old domains from the metadata?

The easy way to do this is to use vdsClient tool:

    vdsClient -s 0 forcedDetachStorageDomain <domain UUID> <pool UUID>

If you are not using secure connection (ssl=true), remove the -s option.

Nir