restore of backup fail when Migrating to ovirt-engine 4.0
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JapCK5PgIhrI8oHqAqwsEWsRJPfAwenGn Content-Type: multipart/mixed; boundary="l95MFGKDaMAbLFS8wD8PlqiDFIL5ddENQ" From: Ricky Schneberger <ricky@schneberger.se> Reply-To: ricky@schneberger.se To: users <users@ovirt.org> Message-ID: <577140AA.1030104@schneberger.se> Subject: restore of backup fail when Migrating to ovirt-engine 4.0 --l95MFGKDaMAbLFS8wD8PlqiDFIL5ddENQ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, I ran my oVirt 3.6 on Centos6 and because of that I had to do a manual migration when trying to move to oVirt 4.0. http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/ Everything went OK until I did the restore, ## engine-backup --mode=3Drestore --no-restore-permissions --provision-db --file=3Dengine-backup.tar.gz --log=3Dengine-backup-restore.log Preparing to restore: - Unpacking file 'engine-backup.tar.gz' FATAL: Backup was created by version '3.6' and can not be restored using the installed version 4.1 and then I got stucked. Is there something I need to do when I do the backup? My old oVirt-engine was version ovirt-engine-3.6.3.4-1.el6.noarch regards --=20 Ricky Schneberger ------------------------------------ Use PGP to protect your own privacy! Key fingerprint =3D 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63 --l95MFGKDaMAbLFS8wD8PlqiDFIL5ddENQ-- --JapCK5PgIhrI8oHqAqwsEWsRJPfAwenGn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAldxQKoACgkQOap81biMC2Mc0gCePkUfEw4SBu2UM2i5/eE3Wmwc gS0AnRVM8n3LdQf7Ca0GK9hYRqY+GPkO =HEj+ -----END PGP SIGNATURE----- --JapCK5PgIhrI8oHqAqwsEWsRJPfAwenGn-- -- IMPORTANT! This message has been scanned for viruses and phishing links. However, it is your responsibility to evaluate the links and attachments you choose to click. If you are uncertain, we always try to help. Greetings helpdesk@actnet.se
On Mon, Jun 27, 2016 at 5:05 PM, Ricky Schneberger <ricky@schneberger.se> wrote:
Hi,
I ran my oVirt 3.6 on Centos6 and because of that I had to do a manual migration when trying to move to oVirt 4.0.
http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/
Everything went OK until I did the restore,
## engine-backup --mode=restore --no-restore-permissions --provision-db --file=engine-backup.tar.gz --log=engine-backup-restore.log
Preparing to restore: - Unpacking file 'engine-backup.tar.gz' FATAL: Backup was created by version '3.6' and can not be restored using the installed version 4.1
This looks pretty strange: it should be 4.0 and it should work. Can you please share the list of oVirt packages you installed on the engine server? Can you please share your oVirt repo details?
and then I got stucked. Is there something I need to do when I do the backup?
My old oVirt-engine was version ovirt-engine-3.6.3.4-1.el6.noarch
regards
-- Ricky Schneberger
------------------------------------
Use PGP to protect your own privacy!
Key fingerprint = 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Just curious. Is the ovirt where the backup is coming from above version 3.6.6? Regards, -- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org On Mon, Jun 27, 2016, at 10:44 AM, Simone Tiraboschi wrote:
On Mon, Jun 27, 2016 at 5:05 PM, Ricky Schneberger <ricky@schneberger.se> wrote:
Hi,
I ran my oVirt 3.6 on Centos6 and because of that I had to do a manual migration when trying to move to oVirt 4.0.
http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/
Everything went OK until I did the restore,
## engine-backup --mode=restore --no-restore-permissions --provision-db --file=engine-backup.tar.gz --log=engine-backup-restore.log
Preparing to restore: - Unpacking file 'engine-backup.tar.gz' FATAL: Backup was created by version '3.6' and can not be restored using the installed version 4.1
This looks pretty strange: it should be 4.0 and it should work.
Can you please share the list of oVirt packages you installed on the engine server? Can you please share your oVirt repo details?
and then I got stucked. Is there something I need to do when I do the backup?
My old oVirt-engine was version ovirt-engine-3.6.3.4-1.el6.noarch
regards
-- Ricky Schneberger
------------------------------------
Use PGP to protect your own privacy!
Key fingerprint = 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --SN5sTN9PS0jpJRavcVIsHQAcGbib0dvfg Content-Type: multipart/mixed; boundary="utkPkcbGxCKiUiTDVR1AmRVNWRCp5ekXe" From: Ricky Schneberger <ricky@schneberger.se> Reply-To: ricky@schneberger.se To: users@ovirt.org Message-ID: <57715132.9030101@schneberger.se> Subject: Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0 References: <577140AA.1030104@schneberger.se> <CAN8-ONptgJF+xyMyD03vn_T_JDw9TYjN5+xp_0P0+ck5XGG2SA@mail.gmail.com> <1467043075.437745.649812721.558AB7EF@webmail.messagingengine.com> In-Reply-To: <1467043075.437745.649812721.558AB7EF@webmail.messagingengine.com> --utkPkcbGxCKiUiTDVR1AmRVNWRCp5ekXe Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-06-27 17:57, Fernando Fuentes wrote:
Just curious. Is the ovirt where the backup is coming from above version 3.6.6?
Regards,
Hi, The package is ovirt-engine-3.6.3.4-1.el6.noarch Regards --=20 Ricky Schneberger ------------------------------------ Use PGP to protect your own privacy! Key fingerprint =3D 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63 --utkPkcbGxCKiUiTDVR1AmRVNWRCp5ekXe-- --SN5sTN9PS0jpJRavcVIsHQAcGbib0dvfg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAldxUTMACgkQOap81biMC2OtCgCdEoZY1CQVE2A/d4+GBX2kvStJ SB8An0TVRzK7gQItch4BNMFMX5HZpHrz =o74d -----END PGP SIGNATURE----- --SN5sTN9PS0jpJRavcVIsHQAcGbib0dvfg-- -- IMPORTANT! This message has been scanned for viruses and phishing links. However, it is your responsibility to evaluate the links and attachments you choose to click. If you are uncertain, we always try to help. Greetings helpdesk@actnet.se
Ricky, I am under the impression that the DB migration was implemented in release 3.6.6. I might be wrong. https://www.ovirt.org/release/3.6.6/ What's New in 3.6.6? Enhancement oVirt Engine BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from el6->el7. BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored on 3.6 on el7 Feature: Allow engine-backup on el7 to restore backups taken on el6. Reason: engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7. This feature, backported from 4.0, allows to do such a migration also in 3.6. Result: Using this flow, it's possible to migrate a el6 setup to el7: On the existing engine machine run: 1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log On a new el7 machine: 2. Install engine, including dwh if it was set up on el6. 3. Copy engine-3.6.bck to the el7 machine 4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log --provision-db --no-restore-permissions 5. engine-setup Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc. -- Fernando Fuentes ffuentes@txweather.org http://www.txweather.org On Mon, Jun 27, 2016, at 11:15 AM, Ricky Schneberger wrote:
On 2016-06-27 17:57, Fernando Fuentes wrote:
Just curious. Is the ovirt where the backup is coming from above version 3.6.6?
Regards,
Hi,
The package is ovirt-engine-3.6.3.4-1.el6.noarch
Regards
-- Ricky Schneberger
------------------------------------
Use PGP to protect your own privacy!
Key fingerprint = 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Email had 1 attachment: + signature.asc 1k (application/pgp-signature)
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gjiixwMHWlaNQLhnIEfPnjDeMs6ADmWA6 Content-Type: multipart/mixed; boundary="9RQxjWDrJXAR1SgGCWAEr9XHaJowG9wsN" From: Ricky Schneberger <ricky@schneberger.se> Reply-To: ricky@schneberger.se To: users@ovirt.org Message-ID: <577177FB.7030101@schneberger.se> Subject: Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0 References: <577140AA.1030104@schneberger.se> <CAN8-ONptgJF+xyMyD03vn_T_JDw9TYjN5+xp_0P0+ck5XGG2SA@mail.gmail.com> <1467043075.437745.649812721.558AB7EF@webmail.messagingengine.com> <57715132.9030101@schneberger.se> <1467047727.452431.649895969.3DAA7E9C@webmail.messagingengine.com> In-Reply-To: <1467047727.452431.649895969.3DAA7E9C@webmail.messagingengine.com> --9RQxjWDrJXAR1SgGCWAEr9XHaJowG9wsN Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-06-27 19:15, Fernando Fuentes wrote:
Ricky,
I am under the impression that the DB migration was implemented in release 3.6.6.
I might be wrong.
https://www.ovirt.org/release/3.6.6/
What's New in 3.6.6? Enhancement oVirt Engine
BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from el6->el7. BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored on 3.6 on el7 Feature:=20
Allow engine-backup on el7 to restore backups taken on el6.
Reason:=20
engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7.
This feature, backported from 4.0, allows to do such a migration also in 3.6.
Result:=20
Using this flow, it's possible to migrate a el6 setup to el7:
On the existing engine machine run: 1. engine-backup --mode=3Dbackup --file=3Dengine-3.6.bck --log=3Dbackup.l= og
On a new el7 machine: 2. Install engine, including dwh if it was set up on el6. 3. Copy engine-3.6.bck to the el7 machine 4. engine-backup --mode=3Drestore --file=3Dengine-3.6.bck --log=3Drestore= .log --provision-db --no-restore-permissions 5. engine-setup
Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc.
Thank you! Seems that you have found the treasure. I will try this tomorrow Regards --=20 Ricky Schneberger ------------------------------------ Use PGP to protect your own privacy! Key fingerprint =3D 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63 --9RQxjWDrJXAR1SgGCWAEr9XHaJowG9wsN-- --gjiixwMHWlaNQLhnIEfPnjDeMs6ADmWA6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAldxd/sACgkQOap81biMC2Pf4ACfdcEu0gfSRUNzvgfwifD+2lsn KIUAn1EtF3XaPbf89Ja/bB7I5dW8nm3o =PEa2 -----END PGP SIGNATURE----- --gjiixwMHWlaNQLhnIEfPnjDeMs6ADmWA6-- -- IMPORTANT! This message has been scanned for viruses and phishing links. However, it is your responsibility to evaluate the links and attachments you choose to click. If you are uncertain, we always try to help. Greetings helpdesk@actnet.se
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1cmmjBXAdEhATNN6wv5UWH9qMD5WXmmXw Content-Type: multipart/mixed; boundary="qSDaSSxnqsk02ujvLqXK2xWFNPMPXvQ3d" From: Ricky Schneberger <ricky@schneberger.se> Reply-To: ricky@schneberger.se To: Fernando Fuentes <ffuentes@darktcp.net>, users@ovirt.org Message-ID: <57721A9A.9070400@schneberger.se> Subject: Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0 References: <577140AA.1030104@schneberger.se> <CAN8-ONptgJF+xyMyD03vn_T_JDw9TYjN5+xp_0P0+ck5XGG2SA@mail.gmail.com> <1467043075.437745.649812721.558AB7EF@webmail.messagingengine.com> <57715132.9030101@schneberger.se> <1467047727.452431.649895969.3DAA7E9C@webmail.messagingengine.com> In-Reply-To: <1467047727.452431.649895969.3DAA7E9C@webmail.messagingengine.com> --qSDaSSxnqsk02ujvLqXK2xWFNPMPXvQ3d Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-06-27 19:15, Fernando Fuentes wrote:
Ricky,
I am under the impression that the DB migration was implemented in release 3.6.6.
I might be wrong.
https://www.ovirt.org/release/3.6.6/
What's New in 3.6.6? Enhancement oVirt Engine
BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from el6->el7. BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored on 3.6 on el7 Feature:=20
Allow engine-backup on el7 to restore backups taken on el6.
Reason:=20
engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7.
This feature, backported from 4.0, allows to do such a migration also in 3.6.
Result:=20
Using this flow, it's possible to migrate a el6 setup to el7:
On the existing engine machine run: 1. engine-backup --mode=3Dbackup --file=3Dengine-3.6.bck --log=3Dbackup.l= og
On a new el7 machine: 2. Install engine, including dwh if it was set up on el6. 3. Copy engine-3.6.bck to the el7 machine 4. engine-backup --mode=3Drestore --file=3Dengine-3.6.bck --log=3Drestore= .log --provision-db --no-restore-permissions 5. engine-setup
Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc.
Hi, I tried upgrade my old install to 3.6.6 with same result. I will try downgrade to 4.0 to see what happen. Regards --=20 Ricky Schneberger ------------------------------------ Use PGP to protect your own privacy! Key fingerprint =3D 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63 --qSDaSSxnqsk02ujvLqXK2xWFNPMPXvQ3d-- --1cmmjBXAdEhATNN6wv5UWH9qMD5WXmmXw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAldyGpsACgkQOap81biMC2OKpwCeNJAFUmrib06ehmgNHLefSd7A prIAn3OV2ghoFOIp9sXNnYeaQkFRyPGo =qHwZ -----END PGP SIGNATURE----- --1cmmjBXAdEhATNN6wv5UWH9qMD5WXmmXw-- -- IMPORTANT! This message has been scanned for viruses and phishing links. However, it is your responsibility to evaluate the links and attachments you choose to click. If you are uncertain, we always try to help. Greetings helpdesk@actnet.se
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --X1bMWFpsf2B6WeUlPQWQ79ga0HH4Ir30b Content-Type: multipart/mixed; boundary="RbuEg8Cm5biR9Sc8pBSF3NhlWLgtUJ7da" From: Ricky Schneberger <ricky@schneberger.se> Reply-To: ricky@schneberger.se To: Fernando Fuentes <ffuentes@darktcp.net>, users@ovirt.org Message-ID: <57722D13.7090907@schneberger.se> Subject: Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0 References: <577140AA.1030104@schneberger.se> <CAN8-ONptgJF+xyMyD03vn_T_JDw9TYjN5+xp_0P0+ck5XGG2SA@mail.gmail.com> <1467043075.437745.649812721.558AB7EF@webmail.messagingengine.com> <57715132.9030101@schneberger.se> <1467047727.452431.649895969.3DAA7E9C@webmail.messagingengine.com> In-Reply-To: <1467047727.452431.649895969.3DAA7E9C@webmail.messagingengine.com> --RbuEg8Cm5biR9Sc8pBSF3NhlWLgtUJ7da Content-Type: multipart/mixed; boundary="------------060009030503040407080808" This is a multi-part message in MIME format. --------------060009030503040407080808 Content-Type: multipart/alternative; boundary="------------060709040505040106000408" --------------060709040505040106000408 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-06-27 19:15, Fernando Fuentes wrote:
Ricky,
I am under the impression that the DB migration was implemented in release 3.6.6.
I might be wrong.
https://www.ovirt.org/release/3.6.6/
What's New in 3.6.6? Enhancement oVirt Engine
BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from el6->el7. BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored on 3.6 on el7 Feature:=20
Allow engine-backup on el7 to restore backups taken on el6.
Reason:=20
engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7.
This feature, backported from 4.0, allows to do such a migration also in 3.6.
Result:=20
Using this flow, it's possible to migrate a el6 setup to el7:
On the existing engine machine run: 1. engine-backup --mode=3Dbackup --file=3Dengine-3.6.bck --log=3Dbackup.l= og
On a new el7 machine: 2. Install engine, including dwh if it was set up on el6. 3. Copy engine-3.6.bck to the el7 machine 4. engine-backup --mode=3Drestore --file=3Dengine-3.6.bck --log=3Drestore= .log --provision-db --no-restore-permissions 5. engine-setup
Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc.
One step forward, two backward.... - upgrade the old EL6 to ovirt 3.6.6 - engine-backup --mode=3Dbackup --file=3Dengine-backup.tar.gz --log=3Dbacku= p.log - install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, to have ovirt-engine 4.0.0.6. - yum install ovirt-engine - |engine-backup --mode=3Drestore --no-restore-permissions --provision-db --file=3Dengine-backup.tar.gz --log=3Dengine-backup-restore.log Then I got this error... "Preparing to restore: - Unpacking file 'engine-backup.tar.gz' Restoring: - Files ---------------------------------------------------------------------------= --- Please note: Operating system is different from the one used during backup. Current operating system: centos7 Operating system at backup: centos6 Apache httpd configuration will not be restored. You will be asked about it on the next engine-setup run. ---------------------------------------------------------------------------= --- Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' Restoring: FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'." I have attached the engine-backup-restore.log. //Ricky | --------------060709040505040106000408 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html> <head> <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Type= "> </head> <body text=3D"#000000" bgcolor=3D"#FFFFFF"> <div class=3D"moz-cite-prefix">On 2016-06-27 19:15, Fernando Fuentes wrote:<br> </div> <blockquote cite=3D"mid:1467047727.452431.649895969.3DAA7E9C@webmail.messagingengine.co= m" type=3D"cite"> <pre wrap=3D"">Ricky, I am under the impression that the DB migration was implemented in release 3.6.6. I might be wrong. <a class=3D"moz-txt-link-freetext" href=3D"https://www.ovirt.org/release/3.= 6.6/">https://www.ovirt.org/release/3.6.6/</a> What's New in 3.6.6? Enhancement oVirt Engine BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from el6->el7. BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored on 3.6 on el7 Feature:=20 Allow engine-backup on el7 to restore backups taken on el6. Reason:=20 engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7. This feature, backported from 4.0, allows to do such a migration also in 3.6. Result:=20 Using this flow, it's possible to migrate a el6 setup to el7: On the existing engine machine run: 1. engine-backup --mode=3Dbackup --file=3Dengine-3.6.bck --log=3Dbackup.log On a new el7 machine: 2. Install engine, including dwh if it was set up on el6. 3. Copy engine-3.6.bck to the el7 machine 4. engine-backup --mode=3Drestore --file=3Dengine-3.6.bck --log=3Drestore.l= og --provision-db --no-restore-permissions 5. engine-setup Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc. </pre> </blockquote> <br> One step forward, two backward....<br> <br> <tt>- upgrade the old EL6 to ovirt 3.6.6</tt><tt><br> </tt><tt>- engine-backup --mode=3Dbackup --file=3Dengine-backup.tar.gz --log=3Dbackup.log</tt><tt><br> </tt><tt>- install </tt><tt><a class=3D"moz-txt-link-freetext" href=3D"http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm= ">http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm</a></tt><tt>, to have ovirt-engine 4.0.0.6.</tt><tt><br> </tt><tt>- yum install ovirt-engine</tt><tt><br> </tt><tt>- </tt><code>engine-backup --mode=3Drestore --no-restore-permissions --provision-db --file=3Dengine-backup.tar.gz --log=3Dengine-backup-restore.log<br> <br> Then I got this error...<br> <br> "Preparing to restore:<br> - Unpacking file 'engine-backup.tar.gz'<br> Restoring:<br> - Files<br> ---------------------------------------------------------------------------= ---<br> Please note:<br> <br> Operating system is different from the one used during backup.<br> Current operating system: centos7<br> Operating system at backup: centos6<br> <br> Apache httpd configuration will not be restored.<br> You will be asked about it on the next engine-setup run.<br> ---------------------------------------------------------------------------= ---<br> Provisioning PostgreSQL users/databases:<br> - user 'engine', database 'engine'<br> Restoring:<br> FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'."<br> <br> I have attached the engine-backup-restore.log.<br> <br> //Ricky<br> <br> <br> </code> </body> </html> --------------060709040505040106000408-- --------------060009030503040407080808 Content-Type: text/plain; charset=UTF-8; name="Untitled Document 1" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Untitled Document 1" MjAxNi0wNi0yOCAwOTo0MjowMSAyMDI2MDogU3RhcnQgb2YgZW5naW5lLWJh Y2t1cCBtb2RlIHJlc3RvcmUgc2NvcGUgYWxsIGZpbGUgZW5naW5lLWJhY2t1 cC50YXIuZ3oKMjAxNi0wNi0yOCAwOTo0MjowMSAyMDI2MDogT1VUUFVUOiBQ cmVwYXJpbmcgdG8gcmVzdG9yZToKMjAxNi0wNi0yOCAwOTo0MjowMSAyMDI2 MDogT1VUUFVUOiAtIFVucGFja2luZyBmaWxlICdlbmdpbmUtYmFja3VwLnRh ci5neicKMjAxNi0wNi0yOCAwOTo0MjowMSAyMDI2MDogT3BlbmluZyB0YXJi YWxsIGVuZ2luZS1iYWNrdXAudGFyLmd6IHRvIC90bXAvZW5naW5lLWJhY2t1 cC5ZdU5ZUWFDOUozCjIwMTYtMDYtMjggMDk6NDI6MDIgMjAyNjA6IFZlcmlm eWluZyBtZDUKMjAxNi0wNi0yOCAwOTo0MjowMiAyMDI2MDogVmVyaWZ5aW5n IHZlcnNpb24KMjAxNi0wNi0yOCAwOTo0MjowMiAyMDI2MDogUmVhZGluZyBj b25maWcKMjAxNi0wNi0yOCAwOTo0MjowMiAyMDI2MDogT1VUUFVUOiBSZXN0 b3Jpbmc6CjIwMTYtMDYtMjggMDk6NDI6MDIgMjAyNjA6IE9VVFBVVDogLSBG aWxlcwoyMDE2LTA2LTI4IDA5OjQyOjAyIDIwMjYwOiBSZXN0b3JpbmcgZmls ZXMKMjAxNi0wNi0yOCAwOTo0MjowMiAyMDI2MDogUmVsb2FkaW5nIGNvbmZp Z3VyYXRpb24KMjAxNi0wNi0yOCAwOTo0MjowMiAyMDI2MDogT1VUUFVUOiBQ cm92aXNpb25pbmcgUG9zdGdyZVNRTCB1c2Vycy9kYXRhYmFzZXM6CjIwMTYt MDYtMjggMDk6NDI6MDIgMjAyNjA6IHByb3Zpc2lvbkRCOiB1c2VyIGVuZ2lu ZSBob3N0IGxvY2FsaG9zdCBwb3J0IDU0MzIgZGF0YWJhc2UgZW5naW5lIHNl Y3VyZWQgRmFsc2Ugc2VjdXJlZF9ob3N0X3ZhbGlkYXRpb24gRmFsc2UKMjAx Ni0wNi0yOCAwOTo0MjowMiAyMDI2MDogT1VUUFVUOiAtIHVzZXIgJ2VuZ2lu ZScsIGRhdGFiYXNlICdlbmdpbmUnClsgSU5GTyAgXSBTdGFnZTogSW5pdGlh bGl6aW5nClsgSU5GTyAgXSBTdGFnZTogRW52aXJvbm1lbnQgc2V0dXAKICAg ICAgICAgIENvbmZpZ3VyYXRpb24gZmlsZXM6IFsnL2V0Yy9vdmlydC1lbmdp bmUtc2V0dXAuY29uZi5kLzEwLXBhY2thZ2luZy1qYm9zcy5jb25mJywgJy9l dGMvb3ZpcnQtZW5naW5lLXNldHVwLmNvbmYuZC8xMC1wYWNrYWdpbmcuY29u ZicsICcvZXRjL292aXJ0LWVuZ2luZS1zZXR1cC5jb25mLmQvMjAtc2V0dXAt b3ZpcnQtcG9zdC5jb25mJywgJy90bXAvZW5naW5lLWJhY2t1cC5ZdU5ZUWFD OUozL3BnLXByb3Zpc2lvbi1hbnN3ZXItZmlsZSddCiAgICAgICAgICBMb2cg ZmlsZTogL3Zhci9sb2cvb3ZpcnQtZW5naW5lL3NldHVwL292aXJ0LWVuZ2lu ZS1wcm92aXNpb25kYi0yMDE2MDYyODA5NDIwMi1ud2NwMjEubG9nCiAgICAg ICAgICBWZXJzaW9uOiBvdG9waS0xLjUuMCAob3RvcGktMS41LjAtMS5lbDcu Y2VudG9zKQpbIElORk8gIF0gU3RhZ2U6IEVudmlyb25tZW50IHBhY2thZ2Vz IHNldHVwClsgSU5GTyAgXSBTdGFnZTogUHJvZ3JhbXMgZGV0ZWN0aW9uClsg SU5GTyAgXSBTdGFnZTogRW52aXJvbm1lbnQgY3VzdG9taXphdGlvbgpbIElO Rk8gIF0gU3RhZ2U6IFNldHVwIHZhbGlkYXRpb24KWyBJTkZPICBdIFN0YWdl OiBUcmFuc2FjdGlvbiBzZXR1cApbIElORk8gIF0gU3RhZ2U6IE1pc2MgY29u ZmlndXJhdGlvbgpbIElORk8gIF0gU3RhZ2U6IFBhY2thZ2UgaW5zdGFsbGF0 aW9uClsgSU5GTyAgXSBTdGFnZTogTWlzYyBjb25maWd1cmF0aW9uClsgSU5G TyAgXSBDcmVhdGluZyBQb3N0Z3JlU1FMICdlbmdpbmUnIGRhdGFiYXNlClsg SU5GTyAgXSBDb25maWd1cmluZyBQb3N0Z3JlU1FMClsgSU5GTyAgXSBTdGFn ZTogVHJhbnNhY3Rpb24gY29tbWl0ClsgSU5GTyAgXSBTdGFnZTogQ2xvc2lu ZyB1cApbIElORk8gIF0gU3RhZ2U6IENsZWFuIHVwCiAgICAgICAgICBMb2cg ZmlsZSBpcyBsb2NhdGVkIGF0IC92YXIvbG9nL292aXJ0LWVuZ2luZS9zZXR1 cC9vdmlydC1lbmdpbmUtcHJvdmlzaW9uZGItMjAxNjA2MjgwOTQyMDItbndj cDIxLmxvZwpbIElORk8gIF0gU3RhZ2U6IFByZS10ZXJtaW5hdGlvbgpbIElO Rk8gIF0gU3RhZ2U6IFRlcm1pbmF0aW9uClsgSU5GTyAgXSBFeGVjdXRpb24g b2YgcHJvdmlzaW9uZGIgY29tcGxldGVkIHN1Y2Nlc3NmdWxseQoyMDE2LTA2 LTI4IDA5OjQyOjA4IDIwMjYwOiBPVVRQVVQ6IFJlc3RvcmluZzoKMjAxNi0w Ni0yOCAwOTo0MjowOCAyMDI2MDogR2VuZXJhdGluZyBwZ3Bhc3MKMjAxNi0w Ni0yOCAwOTo0MjowOCAyMDI2MDogVmVyaWZ5aW5nIGNvbm5lY3Rpb24KMjAx Ni0wNi0yOCAwOTo0MjowOCAyMDI2MDogcGdfY21kIHJ1bm5pbmc6IHBzcWwg LXcgLVUgZW5naW5lIC1oIGxvY2FsaG9zdCAtcCA1NDMyICBlbmdpbmUgLWMg c2VsZWN0IDEKID9jb2x1bW4/IAotLS0tLS0tLS0tCiAgICAgICAgMQooMSBy b3cpCgoyMDE2LTA2LTI4IDA5OjQyOjA4IDIwMjYwOiBwZ19jbWQgcnVubmlu ZzogcHNxbCAtdyAtVSBlbmdpbmUgLWggbG9jYWxob3N0IC1wIDU0MzIgIGVu Z2luZSAtdCAtYyBzaG93IGxjX21lc3NhZ2VzCjIwMTYtMDYtMjggMDk6NDI6 MDggMjAyNjA6IHBnX2NtZCBydW5uaW5nOiBwZ19kdW1wIC13IC1VIGVuZ2lu ZSAtaCBsb2NhbGhvc3QgLXAgNTQzMiAgZW5naW5lIC1zCjIwMTYtMDYtMjgg MDk6NDI6MDggMjAyNjA6IHBnX2NtZCBydW5uaW5nOiBwc3FsIC13IC1VIG92 aXJ0X2VuZ2luZV9oaXN0b3J5IC1oIGxvY2FsaG9zdCAtcCA1NDMyICBvdmly dF9lbmdpbmVfaGlzdG9yeSAtYyBzZWxlY3QgMQpwc3FsOiBGQVRBTDogIElk ZW50IGF1dGhlbnRpY2F0aW9uIGZhaWxlZCBmb3IgdXNlciAib3ZpcnRfZW5n aW5lX2hpc3RvcnkiCjIwMTYtMDYtMjggMDk6NDI6MDggMjAyNjA6IEZBVEFM OiBDYW4ndCBjb25uZWN0IHRvIGRhdGFiYXNlICdvdmlydF9lbmdpbmVfaGlz dG9yeScuIFBsZWFzZSBzZWUgJy91c3IvYmluL2VuZ2luZS1iYWNrdXAgLS1o ZWxwJy4KCg== --------------060009030503040407080808-- --RbuEg8Cm5biR9Sc8pBSF3NhlWLgtUJ7da-- --X1bMWFpsf2B6WeUlPQWQ79ga0HH4Ir30b Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAldyLRMACgkQOap81biMC2Ne1wCfT/D+/lKKN4GCapw4fCWB/wiH ABAAoIsnW4xd3EU8TKBZOIxd4HlLMz2t =jr51 -----END PGP SIGNATURE----- --X1bMWFpsf2B6WeUlPQWQ79ga0HH4Ir30b-- -- IMPORTANT! This message has been scanned for viruses and phishing links. However, it is your responsibility to evaluate the links and attachments you choose to click. If you are uncertain, we always try to help. Greetings helpdesk@actnet.se
On Tue, Jun 28, 2016 at 10:53 AM, Ricky Schneberger <ricky@schneberger.se> wrote:
On 2016-06-27 19:15, Fernando Fuentes wrote:
Ricky,
I am under the impression that the DB migration was implemented in release 3.6.6.
I might be wrong.
https://www.ovirt.org/release/3.6.6/
What's New in 3.6.6? Enhancement oVirt Engine
BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from el6->el7. BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored on 3.6 on el7 Feature:
Allow engine-backup on el7 to restore backups taken on el6.
Reason:
engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7.
This feature, backported from 4.0, allows to do such a migration also in 3.6.
Result:
Using this flow, it's possible to migrate a el6 setup to el7:
On the existing engine machine run: 1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log
On a new el7 machine: 2. Install engine, including dwh if it was set up on el6. 3. Copy engine-3.6.bck to the el7 machine 4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log --provision-db --no-restore-permissions 5. engine-setup
Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc.
One step forward, two backward....
- upgrade the old EL6 to ovirt 3.6.6 - engine-backup --mode=backup --file=engine-backup.tar.gz --log=backup.log - install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, to have ovirt-engine 4.0.0.6. - yum install ovirt-engine - engine-backup --mode=restore --no-restore-permissions --provision-db --file=engine-backup.tar.gz --log=engine-backup-restore.log
Then I got this error...
"Preparing to restore: - Unpacking file 'engine-backup.tar.gz' Restoring: - Files ------------------------------------------------------------------------------ Please note:
Operating system is different from the one used during backup. Current operating system: centos7 Operating system at backup: centos6
Apache httpd configuration will not be restored. You will be asked about it on the next engine-setup run. ------------------------------------------------------------------------------ Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' Restoring: FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'."
The backup/restore here is just like normal ones, so for details you can read the output of 'engine-backup --help' or [1]. In your specific case, you seem to have dwh in your backup. To restore it, you have to either prepare a database with the same credentials as the one used in the old machine, or, if it was automatically-provisioned by engine-setup, you can pass the option '--provision-dwh-db' to make engine-backup create it for you. I think I should add an option '--provision-all-databases' or something like that. Didn't feel very good about it so never done, and no-one asked for it... Best regards, [1] http://www.ovirt.org/develop/release-management/features/engine/engine-backu...
I have attached the engine-backup-restore.log.
//Ricky
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --BNsuvqlTn36xbwElBfkFvfgbObVW02SHF Content-Type: multipart/mixed; boundary="GNlqx8MWeOXhKK4MmnxAuApqIV1VwqBOw" From: Ricky Schneberger <ricky@schneberger.se> Reply-To: ricky@schneberger.se To: Yedidyah Bar David <didi@redhat.com> Cc: Fernando Fuentes <ffuentes@darktcp.net>, users <users@ovirt.org> Message-ID: <57724FD5.5040100@schneberger.se> Subject: Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0 References: <577140AA.1030104@schneberger.se> <CAN8-ONptgJF+xyMyD03vn_T_JDw9TYjN5+xp_0P0+ck5XGG2SA@mail.gmail.com> <1467043075.437745.649812721.558AB7EF@webmail.messagingengine.com> <57715132.9030101@schneberger.se> <1467047727.452431.649895969.3DAA7E9C@webmail.messagingengine.com> <57722D13.7090907@schneberger.se> <CAHRwYXu=6pGnFYBPY80qbhqLx67Hyuss+sDVvqiveuLDx-hEFw@mail.gmail.com> In-Reply-To: <CAHRwYXu=6pGnFYBPY80qbhqLx67Hyuss+sDVvqiveuLDx-hEFw@mail.gmail.com> --GNlqx8MWeOXhKK4MmnxAuApqIV1VwqBOw Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-06-28 10:21, Yedidyah Bar David wrote:
On Tue, Jun 28, 2016 at 10:53 AM, Ricky Schneberger <ricky@schneberger.se> wrote:
On 2016-06-27 19:15, Fernando Fuentes wrote:
Ricky,
I am under the impression that the DB migration was implemented in release 3.6.6.
I might be wrong.
https://www.ovirt.org/release/3.6.6/
What's New in 3.6.6? Enhancement oVirt Engine
BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from el6->el7. BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored on 3.6 on el7 Feature:
Allow engine-backup on el7 to restore backups taken on el6.
Reason:
engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7.
This feature, backported from 4.0, allows to do such a migration also in 3.6.
Result:
Using this flow, it's possible to migrate a el6 setup to el7:
On the existing engine machine run: 1. engine-backup --mode=3Dbackup --file=3Dengine-3.6.bck --log=3Dbackup.= log
On a new el7 machine: 2. Install engine, including dwh if it was set up on el6. 3. Copy engine-3.6.bck to the el7 machine 4. engine-backup --mode=3Drestore --file=3Dengine-3.6.bck --log=3Drestor= e.log --provision-db --no-restore-permissions 5. engine-setup
Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc.
One step forward, two backward....
- upgrade the old EL6 to ovirt 3.6.6 - engine-backup --mode=3Dbackup --file=3Dengine-backup.tar.gz --log=3Dba= ckup.log - install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, to have ovirt-engine 4.0.0.6. - yum install ovirt-engine - engine-backup --mode=3Drestore --no-restore-permissions --provision-db --file=3Dengine-backup.tar.gz --log=3Dengine-backup-restore.log
Then I got this error...
"Preparing to restore: - Unpacking file 'engine-backup.tar.gz' Restoring: - Files ------------------------------------------------------------------------=
Please note:
Operating system is different from the one used during backup. Current operating system: centos7 Operating system at backup: centos6
Apache httpd configuration will not be restored. You will be asked about it on the next engine-setup run. ------------------------------------------------------------------------=
Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' Restoring: FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'."
The backup/restore here is just like normal ones, so for details you can = read the output of 'engine-backup --help' or [1].
In your specific case, you seem to have dwh in your backup.
To restore it, you have to either prepare a database with the same creden= tials as the one used in the old machine, or, if it was automatically-provision= ed by engine-setup, you can pass the option '--provision-dwh-db' to make engine= -backup create it for you.
I think I should add an option '--provision-all-databases' or something l= ike that. Didn't feel very good about it so never done, and no-one asked for = it...
Best regards,
[1] http://www.ovirt.org/develop/release-management/features/engine/engin= e-backup/
#engine-backup --mode=3Drestore --no-restore-permissions --provision-db --provision-dwh-db --provision-reports-db --file=3Dengine-backup.tar.gz --log=3Dengine-backup-restore.log Success with the restore! Thanks for pointing me out. What I did was just following the documentation, right or wrong. But when I run "Engine-setup" I got stucked with "[ INFO ] Stage: Setup validation [WARNING] Less than 16384MB of memory is available [ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade from unsupported versions: 3.5 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160628120936-ix7pb8.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160628121149-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed" Seems to be something missing from an earlier db-upgrade? --=20 Ricky Schneberger ------------------------------------ Use PGP to protect your own privacy! Key fingerprint =3D 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63 --GNlqx8MWeOXhKK4MmnxAuApqIV1VwqBOw-- --BNsuvqlTn36xbwElBfkFvfgbObVW02SHF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAldyT9YACgkQOap81biMC2MWzACeOmAGkLrp/GiX9v91YyDCK5ve 0t4An1/HBydydenxXbrfgomgSr9NT5H/ =r/tn -----END PGP SIGNATURE----- --BNsuvqlTn36xbwElBfkFvfgbObVW02SHF-- -- IMPORTANT! This message has been scanned for viruses and phishing links. However, it is your responsibility to evaluate the links and attachments you choose to click. If you are uncertain, we always try to help. Greetings helpdesk@actnet.se
Do you have any 3.5 clusters? You can only upgrade to 4.0, if all the cluster are 3.6 compatibility. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary@redhat.com IRC : ydary On Tue, Jun 28, 2016 at 1:22 PM, Ricky Schneberger <ricky@schneberger.se> wrote:
On 2016-06-28 10:21, Yedidyah Bar David wrote:
On Tue, Jun 28, 2016 at 10:53 AM, Ricky Schneberger <ricky@schneberger.se> wrote:
On 2016-06-27 19:15, Fernando Fuentes wrote:
Ricky,
I am under the impression that the DB migration was implemented in release 3.6.6.
I might be wrong.
https://www.ovirt.org/release/3.6.6/
What's New in 3.6.6? Enhancement oVirt Engine
BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from el6->el7. BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored on 3.6 on el7 Feature:
Allow engine-backup on el7 to restore backups taken on el6.
Reason:
engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7.
This feature, backported from 4.0, allows to do such a migration also in 3.6.
Result:
Using this flow, it's possible to migrate a el6 setup to el7:
On the existing engine machine run: 1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log
On a new el7 machine: 2. Install engine, including dwh if it was set up on el6. 3. Copy engine-3.6.bck to the el7 machine 4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log --provision-db --no-restore-permissions 5. engine-setup
Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc.
One step forward, two backward....
- upgrade the old EL6 to ovirt 3.6.6 - engine-backup --mode=backup --file=engine-backup.tar.gz --log=backup.log - install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, to have ovirt-engine 4.0.0.6. - yum install ovirt-engine - engine-backup --mode=restore --no-restore-permissions --provision-db --file=engine-backup.tar.gz --log=engine-backup-restore.log
Then I got this error...
"Preparing to restore: - Unpacking file 'engine-backup.tar.gz' Restoring: - Files
Please note:
Operating system is different from the one used during backup. Current operating system: centos7 Operating system at backup: centos6
Apache httpd configuration will not be restored. You will be asked about it on the next engine-setup run.
Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' Restoring: FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'."
The backup/restore here is just like normal ones, so for details you can read the output of 'engine-backup --help' or [1].
In your specific case, you seem to have dwh in your backup.
To restore it, you have to either prepare a database with the same credentials as the one used in the old machine, or, if it was automatically-provisioned by engine-setup, you can pass the option '--provision-dwh-db' to make engine-backup create it for you.
I think I should add an option '--provision-all-databases' or something like that. Didn't feel very good about it so never done, and no-one asked for it...
Best regards,
[1] http://www.ovirt.org/develop/release-management/features/engine/engine-backu...
#engine-backup --mode=restore --no-restore-permissions --provision-db --provision-dwh-db --provision-reports-db --file=engine-backup.tar.gz --log=engine-backup-restore.log
Success with the restore!
Thanks for pointing me out. What I did was just following the documentation, right or wrong.
But when I run "Engine-setup" I got stucked with
"[ INFO ] Stage: Setup validation [WARNING] Less than 16384MB of memory is available [ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade from unsupported versions: 3.5 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160628120936-ix7pb8.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160628121149-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed"
Seems to be something missing from an earlier db-upgrade?
-- Ricky Schneberger
------------------------------------
Use PGP to protect your own privacy!
Key fingerprint = 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Adding Jiri. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary@redhat.com IRC : ydary On Tue, Jun 28, 2016 at 4:00 PM, Yaniv Dary <ydary@redhat.com> wrote:
Do you have any 3.5 clusters? You can only upgrade to 4.0, if all the cluster are 3.6 compatibility.
Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109
Tel : +972 (9) 7692306 8272306 Email: ydary@redhat.com IRC : ydary
On Tue, Jun 28, 2016 at 1:22 PM, Ricky Schneberger <ricky@schneberger.se> wrote:
On 2016-06-28 10:21, Yedidyah Bar David wrote:
On Tue, Jun 28, 2016 at 10:53 AM, Ricky Schneberger <ricky@schneberger.se> wrote:
On 2016-06-27 19:15, Fernando Fuentes wrote:
Ricky,
I am under the impression that the DB migration was implemented in release 3.6.6.
I might be wrong.
https://www.ovirt.org/release/3.6.6/
What's New in 3.6.6? Enhancement oVirt Engine
BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from el6->el7. BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored on 3.6 on el7 Feature:
Allow engine-backup on el7 to restore backups taken on el6.
Reason:
engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7.
This feature, backported from 4.0, allows to do such a migration also in 3.6.
Result:
Using this flow, it's possible to migrate a el6 setup to el7:
On the existing engine machine run: 1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log
On a new el7 machine: 2. Install engine, including dwh if it was set up on el6. 3. Copy engine-3.6.bck to the el7 machine 4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log --provision-db --no-restore-permissions 5. engine-setup
Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc.
One step forward, two backward....
- upgrade the old EL6 to ovirt 3.6.6 - engine-backup --mode=backup --file=engine-backup.tar.gz --log=backup.log - install http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, to have ovirt-engine 4.0.0.6. - yum install ovirt-engine - engine-backup --mode=restore --no-restore-permissions --provision-db --file=engine-backup.tar.gz --log=engine-backup-restore.log
Then I got this error...
"Preparing to restore: - Unpacking file 'engine-backup.tar.gz' Restoring: - Files
Please note:
Operating system is different from the one used during backup. Current operating system: centos7 Operating system at backup: centos6
Apache httpd configuration will not be restored. You will be asked about it on the next engine-setup run.
Provisioning PostgreSQL users/databases: - user 'engine', database 'engine' Restoring: FATAL: Can't connect to database 'ovirt_engine_history'. Please see '/usr/bin/engine-backup --help'."
The backup/restore here is just like normal ones, so for details you can read the output of 'engine-backup --help' or [1].
In your specific case, you seem to have dwh in your backup.
To restore it, you have to either prepare a database with the same credentials as the one used in the old machine, or, if it was automatically-provisioned by engine-setup, you can pass the option '--provision-dwh-db' to make engine-backup create it for you.
I think I should add an option '--provision-all-databases' or something like that. Didn't feel very good about it so never done, and no-one asked for it...
Best regards,
[1] http://www.ovirt.org/develop/release-management/features/engine/engine-backu...
#engine-backup --mode=restore --no-restore-permissions --provision-db --provision-dwh-db --provision-reports-db --file=engine-backup.tar.gz --log=engine-backup-restore.log
Success with the restore!
Thanks for pointing me out. What I did was just following the documentation, right or wrong.
But when I run "Engine-setup" I got stucked with
"[ INFO ] Stage: Setup validation [WARNING] Less than 16384MB of memory is available [ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade from unsupported versions: 3.5 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160628120936-ix7pb8.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160628121149-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed"
Seems to be something missing from an earlier db-upgrade?
-- Ricky Schneberger
------------------------------------
Use PGP to protect your own privacy!
Key fingerprint = 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[.. cutting all bogus as it is unreadable, even with html mails..]
On Tue, Jun 28, 2016 at 4:00 PM, Yaniv Dary <ydary@redhat.com> wrote:
Do you have any 3.5 clusters? You can only upgrade to 4.0, if all the cluster are 3.6 compatibility.
#engine-backup --mode=restore --no-restore-permissions --provision-db --provision-dwh-db --provision-reports-db --file=engine-backup.tar.gz --log=engine-backup-restore.log
Success with the restore!
Thanks for pointing me out. What I did was just following the documentation, right or wrong.
But when I run "Engine-setup" I got stucked with
"[ INFO ] Stage: Setup validation [WARNING] Less than 16384MB of memory is available [ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade from unsupported versions: 3.5 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160628120936-ix7pb8.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160628121149-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed"
3.6 EL6 migration to 4.0 EL7 works OK for me with following steps: 1. 3.6 EL6 engine (3.6 dc/clstr level) 2. 3.6 EL6 engine-backup and do backup 3. 4.0 EL7 clean install 4. 4.0 EL7 engine-backup and do restore 5. 4.0 EL7 engine-setup What are the problematic steps on other side? Do we have a problem if 3.6 EL6 engine does have dc/clstr level set to '3.5'? j.
[.. cutting all bogus as it is unreadable, even with html mails..]
On Tue, Jun 28, 2016 at 4:00 PM, Yaniv Dary <ydary@redhat.com> wrote:
Do you have any 3.5 clusters? You can only upgrade to 4.0, if all the cluster are 3.6 compatibility.
#engine-backup --mode=restore --no-restore-permissions --provision-db --provision-dwh-db --provision-reports-db --file=engine-backup.tar.gz --log=engine-backup-restore.log
Success with the restore!
Thanks for pointing me out. What I did was just following the documentation, right or wrong.
But when I run "Engine-setup" I got stucked with
"[ INFO ] Stage: Setup validation [WARNING] Less than 16384MB of memory is available [ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade from unsupported versions: 3.5 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160628120936-ix7pb8.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160628121149-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed"
3.6 EL6 migration to 4.0 EL7 works OK for me with following steps:
1. 3.6 EL6 engine (3.6 dc/clstr level) 2. 3.6 EL6 engine-backup and do backup 3. 4.0 EL7 clean install 4. 4.0 EL7 engine-backup and do restore 5. 4.0 EL7 engine-setup
What are the problematic steps on other side?
Do we have a problem if 3.6 EL6 engine does have dc/clstr level set to '3.5'?
j.
I "thought" I got cluster level 3.6. Bad move to not check this up. Now when I tried to upgrade from cluster level 3.5 I found out that I maybe need EL7 hosts to upgrade to 3.6. I have VDSM 4.16.x on my el6 hosts and thought it should work but no success. regards -- Ricky Schneberger ------------------------------------ Use PGP to protect your own privacy! Key fingerprint = 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63 -- IMPORTANT! This message has been scanned for viruses and phishing links. However, it is your responsibility to evaluate the links and attachments you choose to click. If you are uncertain, we always try to help. Greetings helpdesk@actnet.se
On Wed, Jun 29, 2016 at 11:29 AM, Ricky Schneberger <ricky@schneberger.se> wrote:
[.. cutting all bogus as it is unreadable, even with html mails..]
On Tue, Jun 28, 2016 at 4:00 PM, Yaniv Dary <ydary@redhat.com> wrote:
Do you have any 3.5 clusters? You can only upgrade to 4.0, if all the cluster are 3.6 compatibility.
#engine-backup --mode=restore --no-restore-permissions --provision-db --provision-dwh-db --provision-reports-db --file=engine-backup.tar.gz --log=engine-backup-restore.log
Success with the restore!
Thanks for pointing me out. What I did was just following the documentation, right or wrong.
But when I run "Engine-setup" I got stucked with
"[ INFO ] Stage: Setup validation [WARNING] Less than 16384MB of memory is available [ ERROR ] Failed to execute stage 'Setup validation': Trying to upgrade from unsupported versions: 3.5 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20160628120936-ix7pb8.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20160628121149-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed"
3.6 EL6 migration to 4.0 EL7 works OK for me with following steps:
1. 3.6 EL6 engine (3.6 dc/clstr level) 2. 3.6 EL6 engine-backup and do backup 3. 4.0 EL7 clean install 4. 4.0 EL7 engine-backup and do restore 5. 4.0 EL7 engine-setup
What are the problematic steps on other side?
Do we have a problem if 3.6 EL6 engine does have dc/clstr level set to '3.5'?
j.
I "thought" I got cluster level 3.6. Bad move to not check this up. Now when I tried to upgrade from cluster level 3.5 I found out that I maybe need EL7 hosts to upgrade to 3.6.
Yes, you have to.
I have VDSM 4.16.x on my el6 hosts and thought it should work but no success.
To reach 3.6 compatibility level, you need VDSM 4.17.z on el7 on all the hosts.
regards
-- Ricky Schneberger
------------------------------------
Use PGP to protect your own privacy!
Key fingerprint = 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63
-- IMPORTANT! This message has been scanned for viruses and phishing links. However, it is your responsibility to evaluate the links and attachments you choose to click. If you are uncertain, we always try to help. Greetings helpdesk@actnet.se
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --VbM2Qid5iB1dJK8qCX57le4EA9qaRga1H Content-Type: multipart/mixed; boundary="q8BXi6m2TJ1F642GIkmmdIm23w7crGgQF" From: Ricky Schneberger <ricky@schneberger.se> Reply-To: ricky@schneberger.se To: Simone Tiraboschi <stirabos@redhat.com> Cc: users <users@ovirt.org> Message-ID: <57714F6A.2050204@schneberger.se> Subject: Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0 References: <577140AA.1030104@schneberger.se> <CAN8-ONptgJF+xyMyD03vn_T_JDw9TYjN5+xp_0P0+ck5XGG2SA@mail.gmail.com> In-Reply-To: <CAN8-ONptgJF+xyMyD03vn_T_JDw9TYjN5+xp_0P0+ck5XGG2SA@mail.gmail.com> --q8BXi6m2TJ1F642GIkmmdIm23w7crGgQF Content-Type: multipart/mixed; boundary="------------050006060400010902040609" This is a multi-part message in MIME format. --------------050006060400010902040609 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-06-27 17:44, Simone Tiraboschi wrote:
On Mon, Jun 27, 2016 at 5:05 PM, Ricky Schneberger <ricky@schneberger.se>= wrote:
Hi,
I ran my oVirt 3.6 on Centos6 and because of that I had to do a manual migration when trying to move to oVirt 4.0.
http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/
Everything went OK until I did the restore,
## engine-backup --mode=3Drestore --no-restore-permissions --provision-db --file=3Dengine-backup.tar.gz --log=3Dengine-backup-restore.log
Preparing to restore: - Unpacking file 'engine-backup.tar.gz' FATAL: Backup was created by version '3.6' and can not be restored using the installed version 4.1 This looks pretty strange: it should be 4.0 and it should work.
Can you please share the list of oVirt packages you installed on the engine server? Can you please share your oVirt repo details?
and then I got stucked. Is there something I need to do when I do the backup?
My old oVirt-engine was version ovirt-engine-3.6.3.4-1.el6.noarch
regards
-- Ricky Schneberger
I attached my repo files and below you find parts of my yum.log. Jun 27 16:36:40 Installed: ovirt-release-master-4.0.0-0.3.master.20160518074018.gitec2301a.noarch Jun 27 16:42:01 Installed: ovirt-setup-lib-1.0.2-1.el7.centos.noarch Jun 27 16:42:30 Installed: ovirt-engine-extensions-api-impl-4.1.0-0.0.master.20160626231337.git2603680= .el7.centos.noarch Jun 27 16:42:31 Installed: ovirt-engine-extension-aaa-jdbc-1.1.1-0.0.master.20160526092913.git2e68ef6.= el7.noarch Jun 27 16:42:33 Installed: ovirt-engine-sdk-python-3.6.5.2-0.1.20160531.gite3a4f2a.el7.centos.noarch Jun 27 16:42:39 Installed: ovirt-host-deploy-1.5.0-1.el7.centos.noarch Jun 27 16:43:08 Installed: python-ovirt-engine-sdk4-4.0.0-0.3.a3.el7.centos.x86_64 Jun 27 16:43:09 Installed: ovirt-image-uploader-4.0.1-0.0.master.20160601214601.gitd6fd324.el7.centos.= noarch Jun 27 16:43:09 Installed: ovirt-iso-uploader-4.0.1-0.0.master.20160531154203.git7213b00.el7.centos.no= arch Jun 27 16:43:16 Installed: ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch Jun 27 16:43:42 Installed: ovirt-engine-wildfly-10.0.0-1.el7.x86_64 Jun 27 16:43:59 Installed: ovirt-engine-lib-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noar= ch Jun 27 16:44:04 Installed: ovirt-engine-setup-base-4.1.0-0.0.master.20160626231337.git2603680.el7.cent= os.noarch Jun 27 16:44:40 Installed: ovirt-engine-setup-plugin-ovirt-engine-common-4.1.0-0.0.master.201606262313= 37.git2603680.el7.centos.noarch Jun 27 16:44:41 Installed: ovirt-engine-tools-backup-4.1.0-0.0.master.20160626231337.git2603680.el7.ce= ntos.noarch Jun 27 16:44:42 Installed: ovirt-engine-setup-plugin-websocket-proxy-4.1.0-0.0.master.20160626231337.g= it2603680.el7.centos.noarch Jun 27 16:44:42 Installed: ovirt-engine-websocket-proxy-4.1.0-0.0.master.20160626231337.git2603680.el7= .centos.noarch Jun 27 16:45:28 Installed: ovirt-vmconsole-1.0.3-0.0.master.20160614081534.gitd1c5824.el7.noarch Jun 27 16:46:09 Installed: ovirt-vmconsole-proxy-1.0.3-0.0.master.20160614081534.gitd1c5824.el7.noarch Jun 27 16:46:13 Installed: ovirt-engine-cli-3.6.7.0-1.el7.centos.noarch Jun 27 16:46:45 Installed: ovirt-host-deploy-java-1.5.0-1.el7.centos.noarch Jun 27 16:46:56 Installed: ovirt-engine-dwh-setup-4.1.0-0.0.master.20160623114857.git8c585e3.el7.cento= s.noarch Jun 27 16:46:58 Installed: ovirt-engine-dwh-4.1.0-0.0.master.20160623114857.git8c585e3.el7.centos.noar= ch Jun 27 16:47:13 Installed: ovirt-engine-dashboard-1.0.0-0.3.20160622gitdf5c4fb.el7.centos.noarch Jun 27 16:47:30 Installed: ovirt-engine-webadmin-portal-4.1.0-0.0.master.20160626231337.git2603680.el7= .centos.noarch Jun 27 16:47:34 Installed: ovirt-engine-backend-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.= noarch Jun 27 16:47:35 Installed: ovirt-engine-dbscripts-4.1.0-0.0.master.20160626231337.git2603680.el7.cento= s.noarch Jun 27 16:47:36 Installed: ovirt-engine-setup-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.no= arch Jun 27 16:47:37 Installed: ovirt-engine-vmconsole-proxy-helper-4.1.0-0.0.master.20160626231337.git2603= 680.el7.centos.noarch Jun 27 16:47:37 Installed: ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.1.0-0.0.master.201606262= 31337.git2603680.el7.centos.noarch Jun 27 16:47:39 Installed: ovirt-engine-setup-plugin-ovirt-engine-4.1.0-0.0.master.20160626231337.git2= 603680.el7.centos.noarch Jun 27 16:47:57 Installed: ovirt-engine-userportal-4.1.0-0.0.master.20160626231337.git2603680.el7.cent= os.noarch Jun 27 16:47:58 Installed: ovirt-engine-restapi-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.= noarch Jun 27 16:47:59 Installed: ovirt-engine-tools-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.no= arch Jun 27 16:48:00 Installed: ovirt-engine-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch Regards //Ricky --------------050006060400010902040609 Content-Type: text/plain; charset=UTF-8; name="ovirt-master-snapshot.repo" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="ovirt-master-snapshot.repo" W292aXJ0LW1hc3Rlci1zbmFwc2hvdF0KbmFtZT1MYXRlc3Qgb1ZpcnQgbWFz dGVyIG5pZ2h0bHkgc25hcHNob3QKI2Jhc2V1cmw9aHR0cDovL3Jlc291cmNl cy5vdmlydC5vcmcvcHViL292aXJ0LW1hc3Rlci1zbmFwc2hvdC9ycG0vZWwk cmVsZWFzZXZlci8KbWlycm9ybGlzdD1odHRwOi8vcmVzb3VyY2VzLm92aXJ0 Lm9yZy9wdWIveXVtLXJlcG8vbWlycm9ybGlzdC1vdmlydC1tYXN0ZXItc25h cHNob3QtZWwkcmVsZWFzZXZlcgplbmFibGVkPTEKc2tpcF9pZl91bmF2YWls YWJsZT0xCmdwZ2NoZWNrPTAKCltvdmlydC1tYXN0ZXItc25hcHNob3Qtc3Rh dGljXQpuYW1lPUxhdGVzdCBvVmlydCBtYXN0ZXIgYWRkaXRpb25hbCBuaWdo dGx5IHNuYXBzaG90CiNiYXNldXJsPWh0dHA6Ly9yZXNvdXJjZXMub3ZpcnQu b3JnL3B1Yi9vdmlydC1tYXN0ZXItc25hcHNob3Qtc3RhdGljL3JwbS9lbCRy ZWxlYXNldmVyLwptaXJyb3JsaXN0PWh0dHA6Ly9yZXNvdXJjZXMub3ZpcnQu b3JnL3B1Yi95dW0tcmVwby9taXJyb3JsaXN0LW92aXJ0LW1hc3Rlci1zbmFw c2hvdC1zdGF0aWMtZWwkcmVsZWFzZXZlcgplbmFibGVkPTEKc2tpcF9pZl91 bmF2YWlsYWJsZT0xCmdwZ2NoZWNrPTAKCg== --------------050006060400010902040609 Content-Type: text/plain; charset=UTF-8; name="ovirt-master-dependencies.repo" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="ovirt-master-dependencies.repo" W292aXJ0LW1hc3Rlci1lcGVsXQpuYW1lPUV4dHJhIFBhY2thZ2VzIGZvciBF bnRlcnByaXNlIExpbnV4IDcgLSAkYmFzZWFyY2gKI2Jhc2V1cmw9aHR0cDov L2Rvd25sb2FkLmZlZG9yYXByb2plY3Qub3JnL3B1Yi9lcGVsLzcvJGJhc2Vh cmNoCm1pcnJvcmxpc3Q9aHR0cHM6Ly9taXJyb3JzLmZlZG9yYXByb2plY3Qu b3JnL21ldGFsaW5rP3JlcG89ZXBlbC03JmFyY2g9JGJhc2VhcmNoCmZhaWxv dmVybWV0aG9kPXByaW9yaXR5CmVuYWJsZWQ9MQppbmNsdWRlcGtncz1lcGVs LXJlbGVhc2UscHl0aG9uLXVpbnB1dCxwdXBwZXQscHl0aG9uLWxvY2tmaWxl LHB5dGhvbi1jcG9wZW4scHl0aG9uLW9yZGVyZWRkaWN0LHB5dGhvbi1wdGhy ZWFkaW5nLHB5dGhvbi1pbm90aWZ5LHB5dGhvbi1hcmdwYXJzZSxub3ZuYyxw eXRob24tcGx5LHB5dGhvbi1raXRjaGVuLHB5dGhvbi1kYWVtb24scHl0aG9u LXdlYnNvY2tpZnksbGl2ZWNkLXRvb2xzLHNwaWNlLWh0bWw1LG1vbSxweXRo b24tSVB5LHB5dGhvbi1pb3Byb2Nlc3MsaW9wcm9jZXNzLHNhZmVsZWFzZSxw eXRob24tcGFyYW1pa28scHl0aG9uMi1jcnlwdG8sbGlidG9tY3J5cHQsbGli dG9tbWF0aCxweXRob24tY2hlZXRhaCxweXRob24tZWNkc2EscHl0aG9uMi1l Y2RzYSxweXRob24tbWFya2Rvd24scnVieWdlbS1yZ2VuLG92aXJ0LWd1ZXN0 LWFnZW50Kix1c2Vyc3BhY2UtcmN1LHByb3RvYnVmLWphdmEsb2JqZW5lc2lz LHB5dGhvbjM0KgpncGdjaGVjaz0xCmdwZ2tleT1odHRwczovL2RsLmZlZG9y YXByb2plY3Qub3JnL3B1Yi9lcGVsL1JQTS1HUEctS0VZLUVQRUwtNwoKW292 aXJ0LW1hc3Rlci1jZW50b3MtZ2x1c3RlcjM3XQpuYW1lPUNlbnRPUy0kcmVs ZWFzZXZlciAtIEdsdXN0ZXIgMy43CmJhc2V1cmw9aHR0cDovL21pcnJvci5j ZW50b3Mub3JnL2NlbnRvcy8kcmVsZWFzZXZlci9zdG9yYWdlLyRiYXNlYXJj aC9nbHVzdGVyLTMuNy8KZ3BnY2hlY2s9MQplbmFibGVkPTEKZ3Bna2V5PWh0 dHBzOi8vcmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbS9DZW50T1MtU3RvcmFn ZS1TSUcvY2VudG9zLXJlbGVhc2Utc3RvcmFnZS1jb21tb24vbWFzdGVyL1JQ TS1HUEctS0VZLUNlbnRPUy1TSUctU3RvcmFnZQoKW292aXJ0LW1hc3Rlci1w YXR0ZXJuZmx5MS1ub2FyY2gtZXBlbF0KbmFtZT1Db3ByIHJlcG8gZm9yIHBh dHRlcm5mbHkxIG93bmVkIGJ5IHBhdHRlcm5mbHkKYmFzZXVybD1odHRwOi8v Y29wci1iZS5jbG91ZC5mZWRvcmFwcm9qZWN0Lm9yZy9yZXN1bHRzL3BhdHRl cm5mbHkvcGF0dGVybmZseTEvZXBlbC03LSRiYXNlYXJjaC8KZW5hYmxlZD0x CnNraXBfaWZfdW5hdmFpbGFibGU9MQpncGdjaGVjaz0wCgpbdmlydGlvLXdp bi1zdGFibGVdCm5hbWU9dmlydGlvLXdpbiBidWlsZHMgcm91Z2hseSBtYXRj aGluZyB3aGF0IHdhcyBzaGlwcGVkIGluIGxhdGVzdCBSSEVMCmJhc2V1cmw9 aHR0cDovL2ZlZG9yYXBlb3BsZS5vcmcvZ3JvdXBzL3ZpcnQvdmlydGlvLXdp bi9yZXBvL3N0YWJsZQplbmFibGVkPTEKc2tpcF9pZl91bmF2YWlsYWJsZT0x CmdwZ2NoZWNrPTAKCltjZW50b3Mtb3ZpcnQ0MC1jYW5kaWRhdGVdCm5hbWU9 Q2VudE9TLSRyZWxlYXNldmVyIC0gb1ZpcnQgNC4wCmJhc2V1cmw9aHR0cDov L2Nicy5jZW50b3Mub3JnL3JlcG9zL3ZpcnQ3LW92aXJ0LTQwLWNhbmRpZGF0 ZS94ODZfNjQvb3MvCmdwZ2NoZWNrPTAKZW5hYmxlZD0xCgoK --------------050006060400010902040609-- --q8BXi6m2TJ1F642GIkmmdIm23w7crGgQF-- --VbM2Qid5iB1dJK8qCX57le4EA9qaRga1H Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAldxT2sACgkQOap81biMC2OueQCghRYBhUiDVifX/UJ1tS6WQ+sW klwAnRrbhIjq6YnDUlovRRsLxhxpaJPs =auMc -----END PGP SIGNATURE----- --VbM2Qid5iB1dJK8qCX57le4EA9qaRga1H-- -- IMPORTANT! This message has been scanned for viruses and phishing links. However, it is your responsibility to evaluate the links and attachments you choose to click. If you are uncertain, we always try to help. Greetings helpdesk@actnet.se
Il 27 Giu 2016 18:18, "Ricky Schneberger" <ricky@schneberger.se> ha scritto:
On 2016-06-27 17:44, Simone Tiraboschi wrote:
On Mon, Jun 27, 2016 at 5:05 PM, Ricky Schneberger <ricky@schneberger.se>
wrote:
Hi,
I ran my oVirt 3.6 on Centos6 and because of that I had to do a manual migration when trying to move to oVirt 4.0.
http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/
Everything went OK until I did the restore,
## engine-backup --mode=restore --no-restore-permissions --provision-db --file=engine-backup.tar.gz --log=engine-backup-restore.log
Preparing to restore: - Unpacking file 'engine-backup.tar.gz' FATAL: Backup was created by version '3.6' and can not be restored using the installed version 4.1 This looks pretty strange: it should be 4.0 and it should work.
Can you please share the list of oVirt packages you installed on the engine server? Can you please share your oVirt repo details?
and then I got stucked. Is there something I need to do when I do the backup?
My old oVirt-engine was version ovirt-engine-3.6.3.4-1.el6.noarch
regards
-- Ricky Schneberger
I attached my repo files and below you find parts of my yum.log.
OK, the issue is here: ovirt-master-snapshot is the nightly build repo from the development branch. If you want something stable, please downgrade to 4.0.
Jun 27 16:36:40 Installed: ovirt-release-master-4.0.0-0.3.master.20160518074018.gitec2301a.noarch Jun 27 16:42:01 Installed: ovirt-setup-lib-1.0.2-1.el7.centos.noarch Jun 27 16:42:30 Installed:
ovirt-engine-extensions-api-impl-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:42:31 Installed:
ovirt-engine-extension-aaa-jdbc-1.1.1-0.0.master.20160526092913.git2e68ef6.el7.noarch
Jun 27 16:42:33 Installed: ovirt-engine-sdk-python-3.6.5.2-0.1.20160531.gite3a4f2a.el7.centos.noarch Jun 27 16:42:39 Installed: ovirt-host-deploy-1.5.0-1.el7.centos.noarch Jun 27 16:43:08 Installed: python-ovirt-engine-sdk4-4.0.0-0.3.a3.el7.centos.x86_64 Jun 27 16:43:09 Installed:
ovirt-image-uploader-4.0.1-0.0.master.20160601214601.gitd6fd324.el7.centos.noarch
Jun 27 16:43:09 Installed:
ovirt-iso-uploader-4.0.1-0.0.master.20160531154203.git7213b00.el7.centos.noarch
Jun 27 16:43:16 Installed: ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch Jun 27 16:43:42 Installed: ovirt-engine-wildfly-10.0.0-1.el7.x86_64 Jun 27 16:43:59 Installed:
ovirt-engine-lib-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:44:04 Installed:
ovirt-engine-setup-base-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:44:40 Installed:
ovirt-engine-setup-plugin-ovirt-engine-common-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:44:41 Installed:
ovirt-engine-tools-backup-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:44:42 Installed:
ovirt-engine-setup-plugin-websocket-proxy-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:44:42 Installed:
ovirt-engine-websocket-proxy-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:45:28 Installed: ovirt-vmconsole-1.0.3-0.0.master.20160614081534.gitd1c5824.el7.noarch Jun 27 16:46:09 Installed:
ovirt-vmconsole-proxy-1.0.3-0.0.master.20160614081534.gitd1c5824.el7.noarch
Jun 27 16:46:13 Installed: ovirt-engine-cli-3.6.7.0-1.el7.centos.noarch Jun 27 16:46:45 Installed: ovirt-host-deploy-java-1.5.0-1.el7.centos.noarch Jun 27 16:46:56 Installed:
ovirt-engine-dwh-setup-4.1.0-0.0.master.20160623114857.git8c585e3.el7.centos.noarch
Jun 27 16:46:58 Installed:
ovirt-engine-dwh-4.1.0-0.0.master.20160623114857.git8c585e3.el7.centos.noarch
Jun 27 16:47:13 Installed: ovirt-engine-dashboard-1.0.0-0.3.20160622gitdf5c4fb.el7.centos.noarch Jun 27 16:47:30 Installed:
ovirt-engine-webadmin-portal-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:47:34 Installed:
ovirt-engine-backend-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:47:35 Installed:
ovirt-engine-dbscripts-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:47:36 Installed:
ovirt-engine-setup-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:47:37 Installed:
ovirt-engine-vmconsole-proxy-helper-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:47:37 Installed:
ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:47:39 Installed:
ovirt-engine-setup-plugin-ovirt-engine-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:47:57 Installed:
ovirt-engine-userportal-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:47:58 Installed:
ovirt-engine-restapi-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:47:59 Installed:
ovirt-engine-tools-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Jun 27 16:48:00 Installed: ovirt-engine-4.1.0-0.0.master.20160626231337.git2603680.el7.centos.noarch
Regards
//Ricky
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --m1MOVC028xlSHJwVTi4rDRRohxm0dI91E Content-Type: multipart/mixed; boundary="jH4epSlrw3NioG3WWhEHv9kJmUkKlgd0o" From: Ricky Schneberger <ricky@schneberger.se> Reply-To: ricky@schneberger.se To: Simone Tiraboschi <stirabos@redhat.com> Cc: users <users@ovirt.org> Message-ID: <57721B46.1050302@schneberger.se> Subject: Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0 References: <577140AA.1030104@schneberger.se> <CAN8-ONptgJF+xyMyD03vn_T_JDw9TYjN5+xp_0P0+ck5XGG2SA@mail.gmail.com> <57714F6A.2050204@schneberger.se> <CAN8-ONo-VgweO9sKTmfy4w5VHWYWhS8ydPjwwNjOiKt2XH2ZNA@mail.gmail.com> In-Reply-To: <CAN8-ONo-VgweO9sKTmfy4w5VHWYWhS8ydPjwwNjOiKt2XH2ZNA@mail.gmail.com> --jH4epSlrw3NioG3WWhEHv9kJmUkKlgd0o Content-Type: multipart/alternative; boundary="------------070309060103060502070308" This is a multi-part message in MIME format. --------------070309060103060502070308 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-06-27 23:52, Simone Tiraboschi wrote:
Il 27 Giu 2016 18:18, "Ricky Schneberger" <ricky@schneberger.se <mailto:ricky@schneberger.se>> ha scritto:
On 2016-06-27 17:44, Simone Tiraboschi wrote:
On Mon, Jun 27, 2016 at 5:05 PM, Ricky Schneberger
<ricky@schneberger.se <mailto:ricky@schneberger.se>> wrote:
Hi,
I ran my oVirt 3.6 on Centos6 and because of that I had to do a manual migration when trying to move to oVirt 4.0.
http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/
Everything went OK until I did the restore,
## engine-backup --mode=3Drestore --no-restore-permissions --provision-db --file=3Dengine-backup.tar.gz --log=3Dengine-backup-restore.log
Preparing to restore: - Unpacking file 'engine-backup.tar.gz' FATAL: Backup was created by version '3.6' and can not be restored using the installed version 4.1 This looks pretty strange: it should be 4.0 and it should work.
Can you please share the list of oVirt packages you installed on the engine server? Can you please share your oVirt repo details?
and then I got stucked. Is there something I need to do when I do the backup?
My old oVirt-engine was version ovirt-engine-3.6.3.4-1.el6.noarch
regards
-- Ricky Schneberger
I attached my repo files and below you find parts of my yum.log.
OK, the issue is here: ovirt-master-snapshot is the nightly build repo from the development branch. If you want something stable, please downgrade to 4.0.
The ovirt-master-snapshot is enabled by default when following the migration documentation. I don't think this is an good idea. Regards //Ricky --------------070309060103060502070308 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html> <head> <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Type= "> </head> <body text=3D"#000000" bgcolor=3D"#FFFFFF"> <div class=3D"moz-cite-prefix">On 2016-06-27 23:52, Simone Tiraboschi wrote:<br> </div> <blockquote cite=3D"mid:CAN8-ONo-VgweO9sKTmfy4w5VHWYWhS8ydPjwwNjOiKt2XH2ZNA@mail.gmail.= com" type=3D"cite"> <p dir=3D"ltr"><br> Il 27 Giu 2016 18:18, "Ricky Schneberger" <<a moz-do-not-send=3D"true" href=3D"mailto:ricky@schneberger.se"><a = class=3D"moz-txt-link-abbreviated" href=3D"mailto:ricky@schneberger.se">ric= ky@schneberger.se</a></a>> ha scritto:<br> ><br> > On 2016-06-27 17:44, Simone Tiraboschi wrote:<br> > > On Mon, Jun 27, 2016 at 5:05 PM, Ricky Schneberger <<a moz-do-not-send=3D"true" href=3D"mailto:ricky@schneberger.se= ">ricky@schneberger.se</a>> wrote:<br> > >> Hi,<br> > >><br> > >> I ran my oVirt 3.6 on Centos6 and because of that I had to do a manual<br> > >> migration when trying to move to oVirt 4.0.<br> > >><br> > >> <a moz-do-not-send=3D"true" href=3D"http://www.ovirt.org/documentation/migration-engine-3.6-t= o-4.0/">http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/</a>= <br> > >><br> > >> Everything went OK until I did the restore,<br> > >><br> > >> ## engine-backup --mode=3Drestore --no-restore-permissions --provision-db<br> > >> --file=3Dengine-backup.tar.gz --log=3Dengine-backup-restore.log<br> > >><br> > >> Preparing to restore:<br> > >> - Unpacking file 'engine-backup.tar.gz'<br> > >> FATAL: Backup was created by version '3.6' and can not be restored using<br> > >> the installed version 4.1<br> > > This looks pretty strange: it should be 4.0 and it should work.<br> > ><br> > > Can you please share the list of oVirt packages you installed on the<br> > > engine server?<br> > > Can you please share your oVirt repo details?<br> > ><br> > >> and then I got stucked. Is there something I need to do when I do the<br> > >> backup?<br> > >><br> > >> My old oVirt-engine was version ovirt-engine-3.6.3.4-1.el6.noarch<br> > >><br> > >> regards<br> > >><br> > >> --<br> > >> Ricky Schneberger<br> ><br> > I attached my repo files and below you find parts of my yum.log.</p> <p dir=3D"ltr">OK, the issue is here: ovirt-master-snapshot is the nightly build repo from the development branch.<br> If you want something stable, please downgrade to 4.0.</p> <br> </blockquote> The ovirt-master-snapshot is enabled by default when following the migration documentation. I don't think this is an good idea.<br> <br> Regards //Ricky<br> </body> </html> --------------070309060103060502070308-- --jH4epSlrw3NioG3WWhEHv9kJmUkKlgd0o-- --m1MOVC028xlSHJwVTi4rDRRohxm0dI91E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAldyG0YACgkQOap81biMC2MQMQCfRoESoG3psp09pKSP1VQueeSs DCgAn2dKTswgTshEyw528XbuZVJa+RE2 =5Q8e -----END PGP SIGNATURE----- --m1MOVC028xlSHJwVTi4rDRRohxm0dI91E-- -- IMPORTANT! This message has been scanned for viruses and phishing links. However, it is your responsibility to evaluate the links and attachments you choose to click. If you are uncertain, we always try to help. Greetings helpdesk@actnet.se
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --lkNbvdH3M7Gt1AmeW4oj89HGdXFMrwlvA Content-Type: multipart/mixed; boundary="rdOa8bToa4RgBMFwwPcvIkcdMaMQqvoX3" From: Ricky Schneberger <ricky@schneberger.se> Reply-To: ricky@schneberger.se To: Simone Tiraboschi <stirabos@redhat.com> Cc: users <users@ovirt.org> Message-ID: <57722659.1030602@schneberger.se> Subject: Re: [ovirt-users] restore of backup fail when Migrating to ovirt-engine 4.0 References: <577140AA.1030104@schneberger.se> <CAN8-ONptgJF+xyMyD03vn_T_JDw9TYjN5+xp_0P0+ck5XGG2SA@mail.gmail.com> <57714F6A.2050204@schneberger.se> <CAN8-ONo-VgweO9sKTmfy4w5VHWYWhS8ydPjwwNjOiKt2XH2ZNA@mail.gmail.com> <57721B46.1050302@schneberger.se> In-Reply-To: <57721B46.1050302@schneberger.se> --rdOa8bToa4RgBMFwwPcvIkcdMaMQqvoX3 Content-Type: multipart/alternative; boundary="------------060508080506090809060901" This is a multi-part message in MIME format. --------------060508080506090809060901 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2016-06-28 08:37, Ricky Schneberger wrote:
On 2016-06-27 23:52, Simone Tiraboschi wrote:
Il 27 Giu 2016 18:18, "Ricky Schneberger" <ricky@schneberger.se> ha scritto:
On 2016-06-27 17:44, Simone Tiraboschi wrote:
On Mon, Jun 27, 2016 at 5:05 PM, Ricky Schneberger
<ricky@schneberger.se <mailto:ricky@schneberger.se>> wrote:
Hi,
I ran my oVirt 3.6 on Centos6 and because of that I had to do a manual migration when trying to move to oVirt 4.0.
http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/
Everything went OK until I did the restore,
## engine-backup --mode=3Drestore --no-restore-permissions --provision-db --file=3Dengine-backup.tar.gz --log=3Dengine-backup-restore.log
Preparing to restore: - Unpacking file 'engine-backup.tar.gz' FATAL: Backup was created by version '3.6' and can not be restored using the installed version 4.1 This looks pretty strange: it should be 4.0 and it should work.
Can you please share the list of oVirt packages you installed on the engine server? Can you please share your oVirt repo details?
and then I got stucked. Is there something I need to do when I do the backup?
My old oVirt-engine was version ovirt-engine-3.6.3.4-1.el6.noarch
regards
-- Ricky Schneberger
I attached my repo files and below you find parts of my yum.log.
OK, the issue is here: ovirt-master-snapshot is the nightly build repo from the development branch. If you want something stable, please downgrade to 4.0.
The ovirt-master-snapshot is enabled by default when following the migration documentation. I don't think this is an good idea.
Regards //Ricky
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
OK, when using the right repos, http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm, I got ovirt-engine 4.0.0.6. Thanks. --=20 Ricky Schneberger ------------------------------------ Use PGP to protect your own privacy! Key fingerprint =3D 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63 --------------060508080506090809060901 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html> <head> <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Type= "> </head> <body text=3D"#000000" bgcolor=3D"#FFFFFF"> <div class=3D"moz-cite-prefix">On 2016-06-28 08:37, Ricky Schneberger wrote:<br> </div> <blockquote cite=3D"mid:57721B46.1050302@schneberger.se" type=3D"cite"> <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty= pe"> <div class=3D"moz-cite-prefix">On 2016-06-27 23:52, Simone Tiraboschi wrote:<br> </div> <blockquote cite=3D"mid:CAN8-ONo-VgweO9sKTmfy4w5VHWYWhS8ydPjwwNjOiKt2XH2ZNA@mail.gmail.= com" type=3D"cite"> <p dir=3D"ltr"><br> Il 27 Giu 2016 18:18, "Ricky Schneberger" <<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" href=3D"mailto:ricky@schneberger.se"><a class=3D"moz-txt-link-a= bbreviated" href=3D"mailto:ricky@schneberger.se">ricky@schneberger.se</a></= a>> ha scritto:<br> ><br> > On 2016-06-27 17:44, Simone Tiraboschi wrote:<br> > > On Mon, Jun 27, 2016 at 5:05 PM, Ricky Schneberger <<a moz-do-not-send=3D"true" href=3D"mailto:ricky@schneberger.se">ricky@schneberger.se</a>&g= t; wrote:<br> > >> Hi,<br> > >><br> > >> I ran my oVirt 3.6 on Centos6 and because of that I had to do a manual<br> > >> migration when trying to move to oVirt 4.0.<br> > >><br> > >> <a moz-do-not-send=3D"true" href=3D"http://www.ovirt.org/documentation/migration-engine-3.6= -to-4.0/">http://www.ovirt.org/documentation/migration-engine-3.6-to-4.0/</= a><br> > >><br> > >> Everything went OK until I did the restore,<br> > >><br> > >> ## engine-backup --mode=3Drestore --no-restore-permissions --provision-db<br> > >> --file=3Dengine-backup.tar.gz --log=3Dengine-backup-restore.log<br> > >><br> > >> Preparing to restore:<br> > >> - Unpacking file 'engine-backup.tar.gz'<br> > >> FATAL: Backup was created by version '3.6' and can not be restored using<br> > >> the installed version 4.1<br> > > This looks pretty strange: it should be 4.0 and it should work.<br> > ><br> > > Can you please share the list of oVirt packages you installed on the<br> > > engine server?<br> > > Can you please share your oVirt repo details?<br> > ><br> > >> and then I got stucked. Is there something I need to do when I do the<br> > >> backup?<br> > >><br> > >> My old oVirt-engine was version ovirt-engine-3.6.3.4-1.el6.noarch<br> > >><br> > >> regards<br> > >><br> > >> --<br> > >> Ricky Schneberger<br> ><br> > I attached my repo files and below you find parts of my yum.log.</p> <p dir=3D"ltr">OK, the issue is here: ovirt-master-snapshot is the nightly build repo from the development branch.<br> If you want something stable, please downgrade to 4.0.</p> <br> </blockquote> The ovirt-master-snapshot is enabled by default when following the migration documentation. I don't think this is an good idea.<br> <br> Regards //Ricky<br> <br> <fieldset class=3D"mimeAttachmentHeader"></fieldset> <br> <pre wrap=3D"">_______________________________________________ Users mailing list <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Users@ovirt.org">Users= @ovirt.org</a> <a class=3D"moz-txt-link-freetext" href=3D"http://lists.ovirt.org/mailman/l= istinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> <br> OK, when using the right repos, <a class=3D"moz-txt-link-freetext" href=3D"http://resources.ovirt.org/p= ub/yum-repo/ovirt-release40.rpm">http://resources.ovirt.org/pub/yum-repo/ov= irt-release40.rpm</a>, I got ovirt-engine 4.0.0.6.<br> <br> Thanks.<br> <br> <pre class=3D"moz-signature" cols=3D"72">--=20 Ricky Schneberger ------------------------------------ Use PGP to protect your own privacy! Key fingerprint =3D 59E1 2B00 C28B 6E0D C8D1 D85B 39AA 7CD5 B88C 0B63 Key-ID: 0xB88C0B63 </pre> </body> </html> --------------060508080506090809060901-- --rdOa8bToa4RgBMFwwPcvIkcdMaMQqvoX3-- --lkNbvdH3M7Gt1AmeW4oj89HGdXFMrwlvA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAldyJlkACgkQOap81biMC2Pc1QCfX7PxDiL5RB7slQHHGd9EuJZo U1YAnic3RWQDO5hO+Wge9e6gdaPlTT56 =ULab -----END PGP SIGNATURE----- --lkNbvdH3M7Gt1AmeW4oj89HGdXFMrwlvA-- -- IMPORTANT! This message has been scanned for viruses and phishing links. However, it is your responsibility to evaluate the links and attachments you choose to click. If you are uncertain, we always try to help. Greetings helpdesk@actnet.se
participants (6)
-
Fernando Fuentes -
Jiri Belka -
Ricky Schneberger -
Simone Tiraboschi -
Yaniv Dary -
Yedidyah Bar David