[ovirt-users] Upgrade from 4.1 to 4.2 failing - SQL Issues

2018-07-24 Thread Sven Achtelik
Hi All, I'm still struggling to upgrade from 4.1 to 4.2 and the root cause seems to be the SQL upgrade. I installed my 4.1.9 with the engine appliance image and restored a DB to it. My Upgrade to 4.2 is failing with the errors below: Performing Consistency

[ovirt-users] Upgrade from 4.1 to 4.2.3 failed

2018-05-14 Thread John Florian
When I run engine-setup, I get this error: [ ERROR ] Yum [u'Errors were encountered while downloading packages.', u'gdeploy-2.0.6-1.el7.noarch: failure: gdeploy-2.0.6-1.el7.noarch.rpm from ovirt-4.1-centos-gluster38: [Errno 256] No more mirrors to

Re: [ovirt-users] Upgrade 4 --> 4.1 OVirt PKI problem

2017-09-19 Thread Lionel Caignec
finally i restore backup to resolve my problem. - Mail original - De: "Lionel Caignec" <caig...@cines.fr> À: "users" <users@ovirt.org> Envoyé: Mardi 19 Septembre 2017 10:19:23 Objet: [ovirt-users] Upgrade 4 --> 4.1 OVirt PKI problem Hi, i've just

[ovirt-users] Upgrade 4 --> 4.1 OVirt PKI problem

2017-09-19 Thread Lionel Caignec
Hi, i've just upgraded to ovirt 4.1 but with some problem, in short ovirt regenerate all the pki infrastructure and now i've 2 problem : 1) If i start ovirt just after install, i can log in the GUI but all my host are unvailable with ssl communication problem. 2) If i restore my old

Re: [ovirt-users] upgrade to 4.1

2017-04-24 Thread Yedidyah Bar David
On Sun, Apr 23, 2017 at 2:53 PM, Fabrice Bacchella wrote: > >> Le 23 avr. 2017 à 07:59, Yedidyah Bar David a écrit : >> >> > >> The main reason we require this is for pg_dump/pg_restore which are ran >> during setup/rollback (if needed). pg_dump

Re: [ovirt-users] upgrade to 4.1

2017-04-23 Thread Fabrice Bacchella
> Le 23 avr. 2017 à 07:59, Yedidyah Bar David a écrit : > > > The main reason we require this is for pg_dump/pg_restore which are ran > during setup/rollback (if needed). pg_dump can't know for sure that all > the changes in the db were done using a client of its own version

Re: [ovirt-users] upgrade to 4.1

2017-04-23 Thread Fabrice Bacchella
> Le 23 avr. 2017 à 10:56, Yedidyah Bar David a écrit : > > On Sun, Apr 23, 2017 at 10:59 AM, Fabrice Bacchella > wrote: >> >>> Le 23 avr. 2017 à 07:59, Yedidyah Bar David a écrit : > >> > > And it was not in the

Re: [ovirt-users] upgrade to 4.1

2017-04-23 Thread Yedidyah Bar David
On Sun, Apr 23, 2017 at 10:59 AM, Fabrice Bacchella wrote: > >> Le 23 avr. 2017 à 07:59, Yedidyah Bar David a écrit : > And it was not in the release notes, it's not funny to get this warning after starting the upgrade >> >> This

Re: [ovirt-users] upgrade to 4.1

2017-04-23 Thread Fabrice Bacchella
> Le 23 avr. 2017 à 07:59, Yedidyah Bar David a écrit : >>> >>> >>> And it was not in the release notes, it's not funny to get this warning >>> after starting the upgrade > > This isn't a new test, see above bug. > > Are you sure it's the first time you see it? Perhaps you

Re: [ovirt-users] upgrade to 4.1

2017-04-23 Thread Yaniv Kaul
On Thu, Apr 20, 2017 at 4:50 PM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > I tried to upgrade ovirt to version 4.1 from 4.0 and got: > > Found the following problems in PostgreSQL configuration for the > Engine database: >autovacuum_vacuum_scale_factor

Re: [ovirt-users] upgrade to 4.1

2017-04-23 Thread Yedidyah Bar David
On Thu, Apr 20, 2017 at 6:59 PM, Simone Tiraboschi wrote: > > On Thu, Apr 20, 2017 at 3:50 PM, Fabrice Bacchella > wrote: >> >> I tried to upgrade ovirt to version 4.1 from 4.0 and got: >> >> Found the following problems in PostgreSQL

Re: [ovirt-users] upgrade to 4.1

2017-04-20 Thread Simone Tiraboschi
On Thu, Apr 20, 2017 at 3:50 PM, Fabrice Bacchella < fabrice.bacche...@orange.fr> wrote: > I tried to upgrade ovirt to version 4.1 from 4.0 and got: > > Found the following problems in PostgreSQL configuration for the > Engine database: >autovacuum_vacuum_scale_factor

[ovirt-users] upgrade to 4.1

2017-04-20 Thread Fabrice Bacchella
I tried to upgrade ovirt to version 4.1 from 4.0 and got: Found the following problems in PostgreSQL configuration for the Engine database: autovacuum_vacuum_scale_factor required to be at most 0.01 autovacuum_analyze_scale_factor required to be at most 0.075