Back to bug 1383156

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-10-10 05:08:54 UTC Keywords FutureFeature
Marcus West 2016-10-10 05:18:10 UTC Whiteboard infra
Martin Perina 2016-10-11 09:30:26 UTC oVirt Team Infra Integration
Martin Sivák 2016-10-17 13:33:48 UTC Assignee msivak bugs
Marina Kalinin 2016-11-07 04:31:47 UTC CC mkalinin, mwest
Flags needinfo?(mwest)
Marcus West 2016-11-07 06:31:38 UTC Flags needinfo?(mwest)
Yaniv Lavi 2016-11-23 07:52:51 UTC Keywords FutureFeature
CC msivak, ydary
Summary [RFE] - upgrade to 4.0 and enable 'hosted engine' on newly upgraded hosts Upgrade to 4.0 and enable 'hosted engine' on newly upgraded hosts
oVirt Team Integration SLA
Flags needinfo?(msivak)
Martin Sivák 2016-11-23 11:47:16 UTC Flags needinfo?(msivak)
Martin Sivák 2016-11-23 11:48:21 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1369827
Doron Fediuck 2016-11-23 11:48:48 UTC Priority unspecified medium
CC dfediuck
Target Milestone --- ovirt-4.0.8
Yaniv Lavi 2016-12-28 16:37:51 UTC Flags needinfo?(mwest)
Marcus West 2017-01-09 23:25:27 UTC Flags needinfo?(mwest)
meital avital 2017-01-11 11:30:14 UTC QA Contact mavital nsednev
Nikolai Sednev 2017-01-15 13:53:10 UTC Flags needinfo?(mwest)
Marcus West 2017-01-16 05:32:33 UTC Flags needinfo?(mwest)
Bronce McClain 2017-02-07 01:33:10 UTC Target Milestone ovirt-4.0.8 ovirt-4.0.7
Moran Goldboim 2017-02-08 11:33:48 UTC CC mgoldboi
Yaniv Lavi 2017-02-15 13:17:45 UTC Priority medium high
Summary Upgrade to 4.0 and enable 'hosted engine' on newly upgraded hosts Enable HE deploy option in 3,6 cluster compatibility and add note in hosted engine tab that it will only work in host that are 4.0 and above.
Yaniv Lavi 2017-02-15 13:18:01 UTC Summary Enable HE deploy option in 3,6 cluster compatibility and add note in hosted engine tab that it will only work in host that are 4.0 and above. Enable HE deploy option in 3.6 cluster compatibility and add note in hosted engine tab that it will only work in host that are 4.0 and above.
Nikolai Sednev 2017-02-15 13:59:10 UTC Flags needinfo?(ydary)
Martin Sivák 2017-02-16 13:39:55 UTC Assignee bugs akrejcir
Andrej Krejcir 2017-02-21 14:06:14 UTC Link ID oVirt gerrit 72721
Andrej Krejcir 2017-02-21 14:06:52 UTC Link ID oVirt gerrit 72752
Andrej Krejcir 2017-02-21 14:07:10 UTC Status NEW ASSIGNED
Andrej Krejcir 2017-02-22 16:33:17 UTC Link ID oVirt gerrit 72894
Andrej Krejcir 2017-02-22 16:33:47 UTC Link ID oVirt gerrit 72917
Andrej Krejcir 2017-02-23 09:44:14 UTC Blocks 1425892
Keywords ZStream
Target Milestone ovirt-4.0.7 ovirt-4.1.1
Status ASSIGNED MODIFIED
Yaniv Lavi 2017-02-27 13:59:20 UTC Flags needinfo?(ydary)
Martin Sivák 2017-03-06 14:10:38 UTC Target Milestone ovirt-4.1.1 ovirt-4.1.2
errata-xmlrpc 2017-03-10 06:37:53 UTC Status MODIFIED ON_QA
Andrej Krejcir 2017-03-16 14:55:01 UTC Doc Text Cause:
Deploying HE on hosts through webadmin was not allowed if the
cluster compatibility level was less than 4.0
because the HE agent for 3.6 did not support it.

Consequence:
It was not possible to update a HE cluster from 3.6 to 4.0.

During the update, the cluster compatibility level has to be 3.6,
because it contains some 3.6 hosts.
Deploying the HE on a 4.0 host is only possible using the webadmin, but
at the same time the deployment was disabled because of the compatibility.

Fix:
Allow deployment of HE in the UI for compatibility version less than 4.0,
but show a warning to the user that it should only be done for hosts
with repositories for version 4.0 or larger.

Result:
It is now possible to update a HE cluster to 4.0.
Doc Type If docs needed, set a value Bug Fix
Nikolai Sednev 2017-03-16 17:03:27 UTC Keywords Triaged
Status ON_QA VERIFIED
Doc Text Cause:
Deploying HE on hosts through webadmin was not allowed if the
cluster compatibility level was less than 4.0
because the HE agent for 3.6 did not support it.

Consequence:
It was not possible to update a HE cluster from 3.6 to 4.0.

During the update, the cluster compatibility level has to be 3.6,
because it contains some 3.6 hosts.
Deploying the HE on a 4.0 host is only possible using the webadmin, but
at the same time the deployment was disabled because of the compatibility.

Fix:
Allow deployment of HE in the UI for compatibility version less than 4.0,
but show a warning to the user that it should only be done for hosts
with repositories for version 4.0 or larger.

Result:
It is now possible to update a HE cluster to 4.0.
If this bug requires documentation, please select an appropriate Doc Type value.
Megan Lewis 2017-04-05 06:09:31 UTC CC akrejcir, melewis
Flags needinfo?(akrejcir)
Andrej Krejcir 2017-04-05 08:32:52 UTC Doc Text If this bug requires documentation, please select an appropriate Doc Type value. Cause:
Deploying HE on hosts through webadmin was not allowed if the cluster compatibility level was less than 4.0 because the HE agent for 3.6 does not support it.

Consequence:
It was not possible to upgrade a HE cluster from 3.6 to 4.0. During the upgrade, the cluster compatibility level has to be 3.6, because it contains some 3.6 hosts. Deploying the HE on an upgraded 4.0 host is only possible using the webadmin, but at the same time the deployment was disabled because of the compatibility.

Fix:
Allow deployment of HE in the UI for compatibility version less than 4.0, but show a warning to the user that it should only be done for hosts with repositories for version 4.0 or larger.

Result:
It is now possible to upgrade a HE cluster to 4.0.
Flags needinfo?(akrejcir)
Megan Lewis 2017-04-10 02:18:26 UTC Doc Text Cause:
Deploying HE on hosts through webadmin was not allowed if the cluster compatibility level was less than 4.0 because the HE agent for 3.6 does not support it.

Consequence:
It was not possible to upgrade a HE cluster from 3.6 to 4.0. During the upgrade, the cluster compatibility level has to be 3.6, because it contains some 3.6 hosts. Deploying the HE on an upgraded 4.0 host is only possible using the webadmin, but at the same time the deployment was disabled because of the compatibility.

Fix:
Allow deployment of HE in the UI for compatibility version less than 4.0, but show a warning to the user that it should only be done for hosts with repositories for version 4.0 or larger.

Result:
It is now possible to upgrade a HE cluster to 4.0.
Previously, deploying self-hosted engine hosts through Administration Portal was not allowed if the cluster compatibility level was earlier than Red Hat Virtualization 4.0. This was because the self-hosted engine agent for Red Hat Enterprise Virtualization 3.6 did not support it. It was also not possible to upgrade a self-hosted engine cluster from Red Hat Enterprise Virtualization 3.6 to Red Hat Virtualization 4.0. During upgrade the cluster compatibility level was required to be set as Red Hat Enterprise Virtualization 3.6 because the cluster contained some Red Hat Enterprise Virtualization 3.6 hosts. This meant that deploying the self-hosted engine on an upgraded Red Hat Virtualization 4.0 host was only possible through the Administration Portal but at the same time the deployment was disabled due to compatibility issues. Now, the deployment of self-hosted engine hosts is allowed for hosts with a cluster compatibility level earlier than Red Hat Virtualization 4.0 but a warning is displayed advising the user that the deployment should only be performed on hosts with repositories for Red Hat Virtualization 4.0 or later. This means that it is now possible to upgrade a self-hosted engine cluster to Red Hat Virtualization 4.0.
errata-xmlrpc 2017-04-18 00:45:27 UTC Status VERIFIED RELEASE_PENDING
Yaniv Kaul 2017-04-20 09:54:23 UTC Flags needinfo?(akrejcir)
Sandro Bonazzola 2017-05-25 06:48:50 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-05-25 02:48:50 UTC
Andrej Krejcir 2018-01-22 12:54:57 UTC Flags needinfo?(akrejcir)
Gil Klein 2019-04-28 13:12:06 UTC CC gklein

Back to bug 1383156