[Users] Data Center Non Responsive / Contending

[Giorgio Bersano]

2014-03-04 22:35 GMT+01:00 Liron Aravot <laravot at redhat.com>:
>
>
> ----- Original Message -----
>> From: "Giorgio Bersano" <giorgio.bersano at gmail.com>
>> To: "Liron Aravot" <laravot at redhat.com>
>> Cc: "Meital Bourvine" <mbourvin at redhat.com>, "users at ovirt.org" <Users at ovirt.org>, fsimonce at redhat.com
>> Sent: Tuesday, March 4, 2014 6:10:27 PM
>> Subject: Re: [Users] Data Center Non Responsive / Contending
>>
>> 2014-03-04 16:37 GMT+01:00 Liron Aravot <laravot at redhat.com>:
>> >
>> >
>> > ----- Original Message -----
>> >> From: "Giorgio Bersano" <giorgio.bersano at gmail.com>
>> >> To: "Liron Aravot" <laravot at redhat.com>
>> >> Cc: "Meital Bourvine" <mbourvin at redhat.com>, "users at ovirt.org"
>> >> <Users at ovirt.org>, fsimonce at redhat.com
>> >> Sent: Tuesday, March 4, 2014 5:31:01 PM
>> >> Subject: Re: [Users] Data Center Non Responsive / Contending
>> >>
>> >> 2014-03-04 16:03 GMT+01:00 Liron Aravot <laravot at redhat.com>:
>> >> > Hi Giorgio,
>> >> > Apperantly the issue is caused because there is no connectivity to the
>> >> > export domain and than we fail on spmStart - that's obviously a bug that
>> >> > shouldn't happen.
>> >>
>> >> Hi Liron,
>> >> we are reaching the same conclusion.
>> >>
>> >> > can you open a bug for the issue?
>> >> Surely I will
>> >>
>> >> > in the meanwhile, as it seems to still exist - seems to me like the way
>> >> > for
>> >> > solving it would be either to fix the connectivity issue between vdsm
>> >> > and
>> >> > the storage domain or to downgrade your vdsm version to before this
>> >> > issue
>> >> > was introduced.
>> >>
>> >>
>> >> I have some problems with your suggestion(s):
>> >> - I cannot fix the connectivity between vdsm and the storage domain
>> >> because, as I already said, it is exposed by a VM by this very same
>> >> DataCenter and if the DC doesn't goes up, the NFS server can't too.
>> >> - I don't understand what does it mean to downgrade the vdsm: to which
>> >> point in time?
>> >>
>> >> It seems I've put myself - again - in a situation of the "the egg or
>> >> the chicken" type, where the SD depends from THIS export domain but
>> >> the export domain isn't available if the DC isn't running.
>> >>
>> >> This export domain isn't that important to me. I can throw it away
>> >> without any problem.
>> >>
>> >> What if we edit the DB and remove any instances related to it? Any
>> >> adverse consequences?
>> >>
>> >
>> > Ok, please perform a full db backup before attempting the following:
>> > 1. right click on the the domain and choose "Destory"
>> > 2. move all hosts to maintenance
>> > 3. log in into the database and run the following sql command:
>> > update storage_pool where id = '{you id goes here}' set
>> > master_domain_version = master_domain_version + 1;
>> > 4. activate a host.
>>
>> Ok Liron, that did the trick!
>>

Just for the record, the correct command was this one:

update storage_pool  set master_domain_version = master_domain_version + 1
where id = '{your id goes here}' ;

Best regards,
Giorgio.

>> Up and running again, even that VM supposed to be the server acting as
>> export domain.
>>
>> Now I've to run away as I'm late to a meeting but tomorrow I'll file a
>> bug regarding this.
>>
>> Thanks to you and Meital for your assistance,
>> Giorgio.
>
> Sure, happy that everything is fine!
>>