Re: [ovirt-users] Update to 4.2.0 failing in db check

2017-12-30 Thread Jiri Slezka
On 12/26/2017 01:43 PM, Jiri Slezka wrote: > Hi, > > I have been also bitten by this bug :-) > > I am also using template with subtemplate. Can I workaround this somehow > or should I wait until fkvalidator fix is released? solution was obvious - I just exported (sub

Re: [ovirt-users] Update to 4.2.0 failing in db check

2017-12-26 Thread Jiri Slezka
Hi, I have been also bitten by this bug :-) I am also using template with subtemplate. Can I workaround this somehow or should I wait until fkvalidator fix is released? Cheers, Jiri On 12/21/2017 03:19 PM, Giorgio Biacchi wrote: > On 12/21/2017 11:24 AM, Sandro Bonazzola wrote: >> >> >>

Re: [ovirt-users] vms stucked after migrate from 4.1.0 to 4.1.1 host

2017-03-30 Thread Jiri Slezka
On 03/28/2017 05:04 PM, Jiří Sléžka wrote: > On 03/28/2017 01:50 PM, Michal Skrivanek wrote: >> >>> On 28 Mar 2017, at 13:41, Jiří Sléžka wrote: >>> >>> On 03/28/2017 12:34 AM, Jiří Sléžka wrote: Hi all, I have just upgraded ovirt manager from 4.1.0 to 4.1.1,

Re: [ovirt-users] [Call for feedback] did you install/update to 4.1.0?

2017-02-03 Thread Jiri Slezka
Hi, I updated our oVirt cluster day after 4.1.0 went public. Upgrade was simple but while migrating and upgrading hosts some vms was stucked with 100% cpu usage and totally non responsible. I had to power of them and start again. But it could be some problem with CentOS7.2->7.3 transition or