[ovirt-users] Re: Upgrade 3.5 to 4.3

smirta Fri, 05 Apr 2019 04:39:02 -0700

Dear all

Upgrading from 3.5 to 4.0 or 4.3 is not supported. You need to upgrade to 3.6 first. We've done this and everything worked just fine. Always check out the release notes and upgrade instructions before upgrading.

From https://www.ovirt.org/documentation/upgrade-guide/chap-Upgrading_to_oVirt_4.0.html : "Upgrading to version 4.0 can only be performed from version 3.6"

Best regards

Simon

Gesendet: Donnerstag, 04. April 2019 um 17:53 Uhr
Von: "Николаев Алексей" <[email protected]>
An: users <[email protected]>, "Demeter Tibor" <[email protected]>
Betreff: [ovirt-users] Re: Upgrade 3.5 to 4.3

Hi!

The best practice is to import the data domain into a new instance of ovirt-engine.

04.04.2019, 16:17, "Demeter Tibor" <[email protected]>:

Hi All,

I did began a very big project, I've started upgrade a cluster from 3.5 to 4.3...

It was a mistake:(

Since upgrade, I can't start the host. The UI seems to working fine.

[root@virt ~]# service vdsm-network start

Redirecting to /bin/systemctl start vdsm-network.service

Job for vdsm-network.service failed because the control process exited with error code. See "systemctl status vdsm-network.service" and "journalctl -xe" for details.

[root@virt ~]# service vdsm-network status

Redirecting to /bin/systemctl status vdsm-network.service

● vdsm-network.service - Virtual Desktop Server Manager network restoration

Loaded: loaded (/usr/lib/systemd/system/vdsm-network.service; disabled; vendor preset: enabled)

Active: failed (Result: exit-code) since Thu 2019-04-04 15:03:44 CEST; 6s ago

Process: 19325 ExecStart=/usr/bin/vdsm-tool restore-nets (code=exited, status=1/FAILURE)

Process: 19313 ExecStartPre=/usr/bin/vdsm-tool --vvverbose --append --logfile=/var/log/vdsm/upgrade.log upgrade-unified-persistence (code=exited, status=0/SUCCESS)

Main PID: 19325 (code=exited, status=1/FAILURE)

Apr 04 15:03:44 virt.bolax.hu vdsm-tool[19325]: return tool_command[cmd]["command"](*args)

Apr 04 15:03:44 virt.bolax.hu vdsm-tool[19325]: File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line 41, in restore_command

Apr 04 15:03:44 virt.bolax.hu vdsm-tool[19325]: exec_restore(cmd)

Apr 04 15:03:44 virt.bolax.hu vdsm-tool[19325]: File "/usr/lib/python2.7/site-packages/vdsm/tool/restore_nets.py", line 54, in exec_restore

Apr 04 15:03:44 virt.bolax.hu vdsm-tool[19325]: raise EnvironmentError('Failed to restore the persisted networks')

Apr 04 15:03:44 virt.bolax.hu vdsm-tool[19325]: EnvironmentError: Failed to restore the persisted networks

Apr 04 15:03:44 virt.bolax.hu systemd[1]: vdsm-network.service: main process exited, code=exited, status=1/FAILURE

Apr 04 15:03:44 virt.bolax.hu systemd[1]: Failed to start Virtual Desktop Server Manager network restoration.

Apr 04 15:03:44 virt.bolax.hu systemd[1]: Unit vdsm-network.service entered failed state.

Apr 04 15:03:44 virt.bolax.hu systemd[1]: vdsm-network.service failed.

Since, the host does not start.

Apr 04 14:56:00 virt.bolax.hu libvirtd[17705]: 2019-04-04 12:56:00.764+0000: 17705: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error

Apr 04 14:56:00 virt.bolax.hu libvirtd[17705]: 2019-04-04 12:56:00.965+0000: 17709: error : virNetSASLSessionListMechanisms:393 : internal error: cannot list SASL ...line 1757)

Apr 04 14:56:00 virt.bolax.hu libvirtd[17705]: 2019-04-04 12:56:00.966+0000: 17709: error : remoteDispatchAuthSaslInit:3440 : authentication failed: authentication failed

Apr 04 14:56:00 virt.bolax.hu libvirtd[17705]: 2019-04-04 12:56:00.966+0000: 17705: error : virNetSocketReadWire:1806 : End of file while reading data: Input/output error

Apr 04 14:56:01 virt.bolax.hu libvirtd[17705]: 2019-04-04 12:56:01.167+0000: 17710: error : virNetSASLSessionListMechanisms:393 : internal error: cannot list SASL ...line 1757)

Apr 04 14:56:01 virt.bolax.hu libvirtd[17705]: 2019-04-04 12:56:01.167+0000: 17710: error : remoteDispatchAuthSaslInit:3440 : authentication failed: authentication failed

[root@virt ~]# service vdsm-network status

Redirecting to /bin/systemctl status vdsm-network.service

● vdsm-network.service - Virtual Desktop Server Manager network restoration

Loaded: loaded (/usr/lib/systemd/system/vdsm-network.service; disabled; vendor preset: enabled)

Active: failed (Result: exit-code) since Thu 2019-04-04 15:00:39 CEST; 2min 49s ago

Process: 19079 ExecStart=/usr/bin/vdsm-tool restore-nets (code=exited, status=1/FAILURE)

Process: 19045 ExecStartPre=/usr/bin/vdsm-tool --vvverbose --append --logfile=/var/log/vdsm/upgrade.log upgrade-unified-persistence (code=exited, status=0/SUCCESS)

Main PID: 19079 (code=exited, status=1/FAILURE)

Also, I upgraded to until 4.0 , but it seems to same. I cant reinstall, and reactivate the host.

Originally it was an AIO installation.

Please help me solve this problem.

Thanks in advance,

R
Tibor

_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/5U4R4R2YI7QUPVFDVWF6B3NMXWESBNRD/

_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/EWC6JYQCZT6LL6KLNVHPZLVXLVKPVLGY/

_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/XHKHTFOCHO44JQJ3FOO2W56IJBKAYOXJ/

[ovirt-users] Re: Upgrade 3.5 to 4.3

Reply via email to