[ovirt-users] Re: Upgrade 4.0 to 4.1: Global Maintenance Mode not recognized

2018-11-27 Thread Simone Tiraboschi
On Tue, Nov 27, 2018 at 8:45 AM Edward Haas wrote: > Where did you managed to get a 4.1 version from? > I would recommend using a supported version (4.2). > > On Mon, Nov 26, 2018 at 1:20 PM gregor wrote: > >> During installation the firewall was enable or changed therefore I get >> an "NoRouteT

[ovirt-users] Re: Upgrade 4.0 to 4.1: Global Maintenance Mode not recognized

2018-11-26 Thread Edward Haas
Where did you managed to get a 4.1 version from? I would recommend using a supported version (4.2). On Mon, Nov 26, 2018 at 1:20 PM gregor wrote: > During installation the firewall was enable or changed therefore I get > an "NoRouteToHostException" from the Engine to the Host. > After disabling

[ovirt-users] Re: Upgrade 4.0 to 4.1: Global Maintenance Mode not recognized

2018-11-26 Thread gregor
During installation the firewall was enable or changed therefore I get an "NoRouteToHostException" from the Engine to the Host. After disabling the firewall on the Host the Data Center and VM's are up and running. regards gregor Am 26.11.18 um 07:50 schrieb gregor: > The Engine is up but the host

[ovirt-users] Re: Upgrade 4.0 to 4.1: Global Maintenance Mode not recognized

2018-11-26 Thread gregor
After a reboot the complete installation was gone. No automounts, no engine nothing. Luckily the files where there. Now I reinstall the whole host + engine fresh and import the existend vm's :-( Am 26.11.18 um 07:50 schrieb gregor: > The Engine is up but the host stucks in NonResponsive. > > The

[ovirt-users] Re: Upgrade 4.0 to 4.1: Global Maintenance Mode not recognized

2018-11-25 Thread gregor
The Engine is up but the host stucks in NonResponsive. The Webinterface stuck in "hanlding non respsonsive host". "Validating" is green and "Executing" is spinning. Can anybody help? I found no errors in the logs under /var/log/ovirt-hosted-engine-ha and journalclt regards gregor Am 26.11.18 u

[ovirt-users] Re: Upgrade 4.0 to 4.1: Global Maintenance Mode not recognized

2018-11-25 Thread gregor
I was able to change the maintenance state in the database to finish the upgrade with engine-setup. these are the lines: select vds_id,ha_global_maintenance from vds_statistics where vds_id = '706599d5-2dbc-400c-b9da-5b5906de6dbd'; update vds_statistics set ha_global_maintenance = 't' where vds_i