Upgrade from 3.6 to 4.1
I am currently running oVirt 3.6 on a physical server using hosted engine environment. I have one server since it's a lab setup. The storage is on a Synology 3615xs iSCSI LUN so that's where the vms are. I plan to upgrade to 4.1 and need to check to make sure I understand the procedure. I've read the oVirt 4.1 Release Notes and they leave some questions. First they say I can simply install the 4.1 release repo update all the ovirt-*-setup* and then run engine-setup. 1. I assume this is on the engine VM running on the host physical box. 2. What does engine-setup do. Does it know what I have and simply update or do I have to go through setup again. 3. Then do I go to the host and update all the ovirt stuff? However, they then say for oVirt Hosted Engine follow a link for upgrading which takes me to a Not Found :( page but did have a link back to the release notes which link to the Not Found which.... So what do I need to know about upgrading a hosted engine setup that there are no directions for. Are there some gotchas? I thought that the release notes said I just had to upgrade the engine and then the host. Given that my VMs are on iSCSI what happens if things go bad and I have to start from scratch. Can I import the VMs created under 3.6 into 4.1 or do I have to do something else like copy them somewhere for backup. Any other hints and tips are appreciated. Thanks.
On 23 Mar 2017, at 20:09, Brett Holcomb <biholcomb@l1049h.com> wrote: =20 I am currently running oVirt 3.6 on a physical server using hosted = engine environment. I have one server since it's a lab setup. The = storage is on a Synology 3615xs iSCSI LUN so that's where the vms are. = I plan to upgrade to 4.1 and need to check to make sure I understand the =
=20 First they say I can simply install the 4.1 release repo update all =
--Apple-Mail=_79208A1C-FED4-4A1F-A42D-A0E4FCCCB67C Content-Type: multipart/alternative; boundary="Apple-Mail=_1E6A5F3B-0D66-4696-B59D-B368422CE60E" --Apple-Mail=_1E6A5F3B-0D66-4696-B59D-B368422CE60E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 procedure. I've read the oVirt 4.1 Release Notes and they leave some = questions. the ovirt-*-setup* and then run engine-setup. I don=E2=80=99t know for sure, but I would first go to latest 4.0 and = then to 4.1 as I=E2=80=99m not sure they test upgrades from 3.6 to 4.1 = directly.=20
=20 1. I assume this is on the engine VM running on the host physical box.
Yes, inside the VM. But first, follow the guide below and make sure = engine is in global maintenance mode.=20
=20 2. What does engine-setup do. Does it know what I have and simply = update or do I have to go through setup again.
You don=E2=80=99t have to setup from scratch.=20
=20 3. Then do I go to the host and update all the ovirt stuff?
=20 However, they then say for oVirt Hosted Engine follow a link for = upgrading which takes me to a Not Found :( page but did have a link back = to the release notes which link to the Not Found which.... So what do I = need to know about upgrading a hosted engine setup that there are no =
Yes, first putting host in local maintenance mode and removing global = maintenance mode from engine.=20 directions for. Are there some gotchas? I thought that the release = notes said I just had to upgrade the engine and then the host. @ovirt, can this be fixed ? It=E2=80=99s quite annoying indeed. Meanwhile, I usually follow the linke from 4.0.0 release notes which is = not 404.=20 = https://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-e= ngine = <https://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-hosted-= engine>
=20 Given that my VMs are on iSCSI what happens if things go bad and I = have to start from scratch. Can I import the VMs created under 3.6 into = 4.1 or do I have to do something else like copy them somewhere for = backup.
It might be good to shutdown the VMs and do an export if you have a = storage domain for that. Just to be 100 % safe. In any case, during the upgrade, since the host is in maintenance, all = VMs have to be OFF.
=20 Any other hints and tips are appreciated.
Don=E2=80=99t have iSCSI so can=E2=80=99t help much with that. I=E2=80=99m just a regular user who failed many times :)
=20 Thanks. =20 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_1E6A5F3B-0D66-4696-B59D-B368422CE60E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div = class=3D"">On 23 Mar 2017, at 20:09, Brett Holcomb <<a = href=3D"mailto:biholcomb@l1049h.com" = class=3D"">biholcomb@l1049h.com</a>> wrote:</div><br = class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">I am = currently running oVirt 3.6 on a physical server using hosted engine = environment. I have one server since it's a lab setup. The = storage is on a Synology 3615xs iSCSI LUN so that's where the vms are. = I plan to upgrade to 4.1 and need to check to make sure I = understand the procedure. I've read the oVirt 4.1 Release Notes = and they leave some questions.<br class=3D""><br class=3D"">First they = say I can simply install the 4.1 release repo update all the = ovirt-*-setup* and then run engine-setup.<br = class=3D""></div></div></blockquote><div><br class=3D""></div><div>I = don=E2=80=99t know for sure, but I would first go to latest 4.0 and then = to 4.1 as I=E2=80=99m not sure they test upgrades from 3.6 to 4.1 = directly. </div><br class=3D""><blockquote type=3D"cite" = class=3D""><div class=3D""><div class=3D""><br class=3D"">1. I assume = this is on the engine VM running on the host physical box.<br = class=3D""></div></div></blockquote><div><br class=3D""></div><div>Yes, = inside the VM. But first, follow the guide below and make sure engine is = in global maintenance mode. </div><br class=3D""><blockquote = type=3D"cite" class=3D""><div class=3D""><div class=3D""><br class=3D"">2.= What does engine-setup do. Does it know what I have and = simply update or do I have to go through setup again.<br = class=3D""></div></div></blockquote><div><br class=3D""></div><div>You = don=E2=80=99t have to setup from scratch. </div><br = class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div = class=3D""><br class=3D"">3. Then do I go to the host and update = all the ovirt stuff?<br class=3D""></div></div></blockquote><div><br = class=3D""></div><div>Yes, first putting host in local maintenance mode = and removing global maintenance mode from engine. </div><br = class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div = class=3D""><br class=3D"">However, they then say for oVirt Hosted Engine = follow a link for upgrading which takes me to a Not Found :( page but = did have a link back to the release notes which link to the Not Found = which.... So what do I need to know about upgrading a hosted = engine setup that there are no directions for. Are there some = gotchas? I thought that the release notes said I just had to = upgrade the engine and then the host.<br = class=3D""></div></div></blockquote><div><br class=3D""></div><div>@ovirt,= can this be fixed ? It=E2=80=99s quite annoying indeed.</div><div><br = class=3D""></div><div>Meanwhile, I usually follow the linke from 4.0.0 = release notes which is not 404. </div><div><br = class=3D""></div><div><a = href=3D"https://www.ovirt.org/documentation/how-to/hosted-engine/#upgrade-= hosted-engine" = class=3D"">https://www.ovirt.org/documentation/how-to/hosted-engine/#upgra= de-hosted-engine</a></div><br class=3D""><blockquote type=3D"cite" = class=3D""><div class=3D""><div class=3D""><br class=3D"">Given that my = VMs are on iSCSI what happens if things go bad and I have to start from = scratch. Can I import the VMs created under 3.6 into 4.1 or do I = have to do something else like copy them somewhere for backup.<br = class=3D""></div></div></blockquote><div><br class=3D""></div><div>It = might be good to shutdown the VMs and do an export if you have a storage = domain for that. Just to be 100 % safe.</div><div>In any case, during = the upgrade, since the host is in maintenance, all VMs have to be = OFF.</div><br class=3D""><blockquote type=3D"cite" class=3D""><div = class=3D""><div class=3D""><br class=3D"">Any other hints and tips are = appreciated.<br class=3D""></div></div></blockquote><div><br = class=3D""></div><div>Don=E2=80=99t have iSCSI so can=E2=80=99t help = much with that.</div><div>I=E2=80=99m just a regular user who failed = many times :)</div><br class=3D""><blockquote type=3D"cite" = class=3D""><div class=3D""><div class=3D""><br class=3D"">Thanks.<br = class=3D""><br = class=3D"">_______________________________________________<br = class=3D"">Users mailing list<br class=3D""><a = href=3D"mailto:Users@ovirt.org" class=3D"">Users@ovirt.org</a><br = class=3D"">http://lists.ovirt.org/mailman/listinfo/users<br = class=3D""></div></div></blockquote></div><br class=3D""></body></html>= --Apple-Mail=_1E6A5F3B-0D66-4696-B59D-B368422CE60E-- --Apple-Mail=_79208A1C-FED4-4A1F-A42D-A0E4FCCCB67C Content-Disposition: attachment; filename="smime.p7s" Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKUjCCBQAw ggPooAMCAQICEANL7hcft+EGNy/UckJAvSowDQYJKoZIhvcNAQELBQAwZTELMAkGA1UEBhMCVVMx FTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UE AxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTE0MTExODEyMDAwMFoXDTI0MTExODEy MDAwMFowaTELMAkGA1UEBhMCTkwxFjAUBgNVBAgTDU5vb3JkLUhvbGxhbmQxEjAQBgNVBAcTCUFt c3RlcmRhbTEPMA0GA1UEChMGVEVSRU5BMR0wGwYDVQQDExRURVJFTkEgUGVyc29uYWwgQ0EgMzCC ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMalux9VgvSlNHIUcmWbX9XqoGjYm4KJT1Ni nHuMzg7a1DIOrxuMy6br2+DrAzSUwYd+UyCoHvkbF4p9AWYSV2heLZwuKyGoVS9TZwl4zdJpGwuT YGy4KBPOH02xiCatRfrQoc6rt5gpVnFs8VYkXacw4G4xc27aoFdMZIt4tcec28bevtMvMaDWgDm1 4DFAToSjzJJJ4hds/vBkHvq6vCWHnU8huslmOQON1BUQuHs6VM/VY7pP8d/oGwR94VymhrV74xb+ XDRV61M88dDXkdgpg/ZZiiEfHMOIL5BTATtRlUGWn1xcinAe4PNKJtzlEbfPSf+PZJALHQOTkUwB QSsCAwEAAaOCAaYwggGiMBIGA1UdEwEB/wQIMAYBAf8CAQAwDgYDVR0PAQH/BAQDAgGGMHkGCCsG AQUFBwEBBG0wazAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuZGlnaWNlcnQuY29tMEMGCCsGAQUF BzAChjdodHRwOi8vY2FjZXJ0cy5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURSb290Q0Eu Y3J0MIGBBgNVHR8EejB4MDqgOKA2hjRodHRwOi8vY3JsMy5kaWdpY2VydC5jb20vRGlnaUNlcnRB c3N1cmVkSURSb290Q0EuY3JsMDqgOKA2hjRodHRwOi8vY3JsNC5kaWdpY2VydC5jb20vRGlnaUNl cnRBc3N1cmVkSURSb290Q0EuY3JsMD0GA1UdIAQ2MDQwMgYEVR0gADAqMCgGCCsGAQUFBwIBFhxo dHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BTMB0GA1UdDgQWBBTwIelJd3Ofha4YO+hScBQG7ULu yjAfBgNVHSMEGDAWgBRF66Kv9JLLgjEtUYunpyGd823IDzANBgkqhkiG9w0BAQsFAAOCAQEAOsIb K/5j3rthtLlHqPx8BbEmICJRm8g9+fXFWB6wXqOynAJBjzEaf8wbTh34mH3sjwj9d/Hb0kQQWrat CbDg/GI71GINnvGgPE13iutENHuOu04pA/wn6j5qHS9I4/raGcP/M9Ls1Ey0jJVLYbbvsoAvl8hH raeCv3zh+YmCEO/RuyMYCZ67cQ/TGFSwMlPrUigAagoGfEE8B6DdZex1Kbgaftu3K9qR7IW1h5uv YqY4FJrbw9GoZIO6vnppmEmgzZ4zNzqmua8bDC0DNGxzm3Y6wpG4dZXo7dqc/YrbuMZlHZuLVVfU 1BS8hulU1O7COb5dxm2xr8AAkX0oaQSx4DCCBUowggQyoAMCAQICEAbOAJ+Ec9btisckDi20mtow DQYJKoZIhvcNAQELBQAwaTELMAkGA1UEBhMCTkwxFjAUBgNVBAgTDU5vb3JkLUhvbGxhbmQxEjAQ BgNVBAcTCUFtc3RlcmRhbTEPMA0GA1UEChMGVEVSRU5BMR0wGwYDVQQDExRURVJFTkEgUGVyc29u YWwgQ0EgMzAeFw0xNzAzMTAwMDAwMDBaFw0xODAzMTAxMjAwMDBaMH0xCzAJBgNVBAYTAkxVMRMw EQYDVQQIEwpMdXhlbWJvdXJnMRkwFwYDVQQHExBFc2NoLXN1ci1BbHpldHRlMSEwHwYDVQQKExhV bml2ZXJzaXR5IG9mIEx1eGVtYm91cmcxGzAZBgNVBAMTEkNocmlzdG9waGUgVFJFRk9JUzCCASIw DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANMliC5A438/QPwe9tp30XBB7iJzjF+Yxl/HiBzO rMOdNwEVbrGdtAuKaPY61yhv8dMzDYAHmmY7aBlFw/5ynohdLhRNNZ64d08lXxI4UCFnOtj+yJE7 ScvsvyOiORa+bdnRTSnSE2JDcB3Vlk2dUXIQ86+pc0J6zPBeCDTXUvqw2y7znrXm1reksJl8fMUL R+LWX12hN6z2MRKgDZL3CswOIzocl+bmBnYqUnU2iDcv31QOKy6AGqGdV2t+1bAbJgZEqgkerSsf YpHeezMej2vH5E6/IlwnHVnG7c54bGD1AumloDdEjCysqdlcEq/dc7Bb9qFrjg/Rby5iGxUtbhUC AwEAAaOCAdgwggHUMB8GA1UdIwQYMBaAFPAh6Ul3c5+Frhg76FJwFAbtQu7KMB0GA1UdDgQWBBTI hivrWIlnKOLxQ9wYwCGuiJFoezAMBgNVHRMBAf8EAjAAMCQGA1UdEQQdMBuBGWNocmlzdG9waGUu dHJlZm9pc0B1bmkubHUwDgYDVR0PAQH/BAQDAgWgMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEF BQcDBDBDBgNVHSAEPDA6MDgGCmCGSAGG/WwEAQIwKjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cu ZGlnaWNlcnQuY29tL0NQUzB1BgNVHR8EbjBsMDSgMqAwhi5odHRwOi8vY3JsMy5kaWdpY2VydC5j b20vVEVSRU5BUGVyc29uYWxDQTMuY3JsMDSgMqAwhi5odHRwOi8vY3JsNC5kaWdpY2VydC5jb20v VEVSRU5BUGVyc29uYWxDQTMuY3JsMHMGCCsGAQUFBwEBBGcwZTAkBggrBgEFBQcwAYYYaHR0cDov L29jc3AuZGlnaWNlcnQuY29tMD0GCCsGAQUFBzAChjFodHRwOi8vY2FjZXJ0cy5kaWdpY2VydC5j b20vVEVSRU5BUGVyc29uYWxDQTMuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQC59zmhjgRb56qtSBn6 a3cA8FGq1pQyOmNRZtCHlMN/LuAdHBxteXrbVzPDrGl27lHVvgoAcFPxo093R3Z0qNjE/qOSro8e i5PfQBEGbRwbWi6cHDOHT9y+OIq23wQdlnhV6gcdirfc5YXSD/0U573DDzW+MfloIRVA03EsXb+v nZEgp6ajNtYL/cYMch5oQa3s2H27K0WVk0l+R38ChSJazkpchWZb7TvH+h2LHDZLRlvmuFHNACWJ zSusO3o/N95pUnUS4uwnAmavXN3ZZWVqlTX5qyQin68dYZPkQJY0agX+T27Y+VFs/llOUmNw6X2m e7G8PVBBx6cxvPaJ9tKMMYIDJTCCAyECAQEwfTBpMQswCQYDVQQGEwJOTDEWMBQGA1UECBMNTm9v cmQtSG9sbGFuZDESMBAGA1UEBxMJQW1zdGVyZGFtMQ8wDQYDVQQKEwZURVJFTkExHTAbBgNVBAMT FFRFUkVOQSBQZXJzb25hbCBDQSAzAhAGzgCfhHPW7YrHJA4ttJraMAkGBSsOAwIaBQCgggF9MBgG CSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTE3MDMyNDEwNTE1NVowIwYJ KoZIhvcNAQkEMRYEFGZXWW4DKTcfgbWyq438y/mPgh4qMIGMBgkrBgEEAYI3EAQxfzB9MGkxCzAJ BgNVBAYTAk5MMRYwFAYDVQQIEw1Ob29yZC1Ib2xsYW5kMRIwEAYDVQQHEwlBbXN0ZXJkYW0xDzAN BgNVBAoTBlRFUkVOQTEdMBsGA1UEAxMUVEVSRU5BIFBlcnNvbmFsIENBIDMCEAbOAJ+Ec9btisck Di20mtowgY4GCyqGSIb3DQEJEAILMX+gfTBpMQswCQYDVQQGEwJOTDEWMBQGA1UECBMNTm9vcmQt SG9sbGFuZDESMBAGA1UEBxMJQW1zdGVyZGFtMQ8wDQYDVQQKEwZURVJFTkExHTAbBgNVBAMTFFRF UkVOQSBQZXJzb25hbCBDQSAzAhAGzgCfhHPW7YrHJA4ttJraMA0GCSqGSIb3DQEBAQUABIIBAG9U 09zgx1uoHmOdX7r8dJ5dvDuBwq3g2LrFWgTm665z7uE8VrgCxmHzUyuorjGti2zGtp9lZRXeszvg hiAw0cMX2RGl53LLpUT7oBiKrAIffn8Uc4TXzZBmj1uljszDM8gME8g7JIuXq9CEswr+yKv5EgnK H1vNB13WPJ2v04aZESFDcghGs5mGmIhEDtW93ItOdX/FwwZrF28sPTqaq0iEAX2aVuLaF/MqGHVD RkozCxcAQ3rdehyGBbcqyyNzQlp2JR9JfkobLu45ZbFAj08WO8xeRZFupGjGy3omNDoBnxUs2KMh DW7TeZExhofETwyQ7VruqzqqF393oVGi0w0AAAAAAAA= --Apple-Mail=_79208A1C-FED4-4A1F-A42D-A0E4FCCCB67C--
Before upgrade make shure that epel is disabled, there are some conflicts in collectd package. On Fri, Mar 24, 2017 at 11:51 AM, Christophe TREFOIS < christophe.trefois@uni.lu> wrote:
On 23 Mar 2017, at 20:09, Brett Holcomb <biholcomb@l1049h.com> wrote:
I am currently running oVirt 3.6 on a physical server using hosted engine environment. I have one server since it's a lab setup. The storage is on a Synology 3615xs iSCSI LUN so that's where the vms are. I plan to upgrade to 4.1 and need to check to make sure I understand the procedure. I've read the oVirt 4.1 Release Notes and they leave some questions.
First they say I can simply install the 4.1 release repo update all the ovirt-*-setup* and then run engine-setup.
I don’t know for sure, but I would first go to latest 4.0 and then to 4.1 as I’m not sure they test upgrades from 3.6 to 4.1 directly.
1. I assume this is on the engine VM running on the host physical box.
Yes, inside the VM. But first, follow the guide below and make sure engine is in global maintenance mode.
2. What does engine-setup do. Does it know what I have and simply update or do I have to go through setup again.
You don’t have to setup from scratch.
3. Then do I go to the host and update all the ovirt stuff?
Yes, first putting host in local maintenance mode and removing global maintenance mode from engine.
However, they then say for oVirt Hosted Engine follow a link for upgrading which takes me to a Not Found :( page but did have a link back to the release notes which link to the Not Found which.... So what do I need to know about upgrading a hosted engine setup that there are no directions for. Are there some gotchas? I thought that the release notes said I just had to upgrade the engine and then the host.
@ovirt, can this be fixed ? It’s quite annoying indeed.
Meanwhile, I usually follow the linke from 4.0.0 release notes which is not 404.
https://www.ovirt.org/documentation/how-to/hosted- engine/#upgrade-hosted-engine
Given that my VMs are on iSCSI what happens if things go bad and I have to start from scratch. Can I import the VMs created under 3.6 into 4.1 or do I have to do something else like copy them somewhere for backup.
It might be good to shutdown the VMs and do an export if you have a storage domain for that. Just to be 100 % safe. In any case, during the upgrade, since the host is in maintenance, all VMs have to be OFF.
Any other hints and tips are appreciated.
Don’t have iSCSI so can’t help much with that. I’m just a regular user who failed many times :)
Thanks.
_______________________________________________ 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
participants (3)
-
Arman Khalatyan -
Brett Holcomb -
Christophe TREFOIS