Background:

We had an issue when an operator decided to just install Windows on a running oVirt hypervisor with VMs running.

Somehow the Windows installation somehow corrupted some of the storage metadata for one storage domain (The storage domain could not be activated, activation failed after ~5 minutes each time I tried).

I was able to move all disks on that storage domain except two to another a new storage domain so all important data was saved.

After data was moved I removed the corrupted storage domain from the cluster/datacenter with no issues.

I then destroyed the storage domain.

 

The existing hypervisors in the cluster can reboot without any issues with the existing storage domains.

 

So far so good.

 

Issue:

However when I try to add an additional hypervisor to the cluster I get an error referencing the corrupted storage domain (UUID is for the bad one that no longer exists).

My question is where can the reference still be, in the DB or in any active data structure the hypervisors are using?

if it is in the DB I guess some clever SQL statement might be able to remove it but if that's the case I would need help with those SQL statements.

 

Thanks

/Jonas


*******************************************
CONFIDENTIALITY AND PRIVACY NOTICE: This e-mail and any attachments are for the exclusive and confidential use of the intended recipient and may constitute non-public information.  Personal data in this email is governed by our Privacy Policy at  http://business.nasdaq.com/privacy-statement  unless explicitly excluded from it; please see the section in the policy entitled “Situations Where This Privacy Policy Does Not Apply” for circumstances where different privacy terms govern emailed personal data.  If you received this e-mail in error, disclosing, copying, distributing or taking any action in reliance of this e-mail is strictly prohibited and may be unlawful. Instead, please notify us immediately by return e-mail and promptly delete this message and its attachments from your computer system. We do not waive any work product or other applicable legal privilege(s) by the transmission of this message.
*******************************************