Back to bug 1399766

Who When What Removed Added
Martin Sivák 2016-11-29 17:02:21 UTC Link ID oVirt gerrit 67540
Status NEW POST
See Also https://bugzilla.redhat.com/show_bug.cgi?id=1362618
Nikolai Sednev 2016-11-30 07:02:53 UTC CC nsednev
QA Contact mavital nsednev
Doron Fediuck 2016-11-30 09:16:44 UTC Priority unspecified high
CC dfediuck
Flags ovirt-4.0.z? ovirt-4.1? planning_ack? testing_ack?
Severity unspecified high
Doron Fediuck 2016-11-30 09:17:18 UTC Target Milestone --- ovirt-4.1.0-alpha
Red Hat Bugzilla Rules Engine 2016-11-30 09:17:23 UTC Flags planning_ack? planning_ack+
Doron Fediuck 2016-11-30 09:18:09 UTC Target Milestone ovirt-4.1.0-alpha ovirt-4.0.7
meital avital 2016-11-30 09:26:52 UTC CC mavital
Flags testing_ack? testing_ack+
Red Hat Bugzilla Rules Engine 2016-11-30 09:26:57 UTC Flags ovirt-4.0.z? ovirt-4.1? ovirt-4.0.z+ ovirt-4.1+
Yaniv Lavi 2016-11-30 13:20:43 UTC Priority high medium
CC ydary
Flags ovirt-4.0.z+
Severity high low
Red Hat Bugzilla Rules Engine 2016-11-30 13:20:48 UTC Flags ovirt-4.0.z? ovirt-4.0.z? ovirt-4.0.z+
Artyom 2016-11-30 13:22:15 UTC CC alukiano
Nikolai Sednev 2016-11-30 14:12:16 UTC CC msivak
Flags needinfo?(msivak)
Martin Sivák 2016-11-30 14:16:36 UTC Flags needinfo?(msivak)
Artyom 2016-12-01 07:25:09 UTC Flags needinfo?(msivak)
Nikolai Sednev 2016-12-01 07:28:03 UTC Blocks 1362618
Martin Sivák 2016-12-01 08:21:46 UTC Flags needinfo?(msivak)
Martin Sivák 2016-12-12 10:53:12 UTC Blocks 1362618
Martin Sivák 2016-12-13 13:47:50 UTC Assignee bugs dchaplyg
Kobi Hakimi 2016-12-14 10:17:21 UTC CC khakimi
Martin Sivák 2016-12-16 11:42:35 UTC Link ID oVirt gerrit 68597
Status POST MODIFIED
Simone Tiraboschi 2017-01-24 15:50:24 UTC Blocks 1416111
Sandro Bonazzola 2017-01-25 07:54:57 UTC CC dchaplyg
Flags needinfo?(dchaplyg)
Denis Chaplygin 2017-01-25 10:28:28 UTC Target Milestone ovirt-4.0.7 ovirt-4.1.0-rc
Flags needinfo?(dchaplyg)
Sandro Bonazzola 2017-02-01 16:01:22 UTC Target Milestone ovirt-4.1.0-rc ovirt-4.1.1
Flags needinfo?(dchaplyg)
Denis Chaplygin 2017-03-02 06:03:57 UTC Flags needinfo?(dchaplyg)
Simone Tiraboschi 2017-03-02 16:56:33 UTC Blocks 1416111
Sandro Bonazzola 2017-03-03 14:19:58 UTC Status MODIFIED ON_QA
Target Release --- 2.1.0.4
Nikolai Sednev 2017-03-05 17:11:01 UTC Status ON_QA ASSIGNED
Red Hat Bugzilla Rules Engine 2017-03-05 17:11:08 UTC Target Release 2.1.0.4 ---
Yaniv Kaul 2017-03-09 09:17:42 UTC Flags needinfo?(dchaplyg)
Martin Sivák 2017-03-09 15:33:48 UTC Flags needinfo?(nsednev)
Nikolai Sednev 2017-03-12 08:28:39 UTC Flags needinfo?(dchaplyg) needinfo?(nsednev)
Doron Fediuck 2017-03-15 11:35:39 UTC Target Milestone ovirt-4.1.1 ovirt-4.1.4
Doron Fediuck 2017-03-15 11:36:37 UTC Depends On 1419326
Denis Chaplygin 2017-04-19 13:04:57 UTC Flags needinfo?(nsednev)
Nikolai Sednev 2017-04-19 14:35:51 UTC Flags needinfo?(nsednev)
Nikolai Sednev 2017-04-20 11:03:40 UTC Flags needinfo?(ydary)
Yaniv Lavi 2017-04-23 16:03:04 UTC Link ID oVirt gerrit 75684
Status ASSIGNED POST
Link ID oVirt gerrit 75685
Flags needinfo?(ydary) ovirt-4.0.z+
Denis Chaplygin 2017-04-25 13:53:43 UTC Link ID oVirt gerrit 75990
Status POST MODIFIED
Nikolai Sednev 2017-04-25 14:36:45 UTC Flags needinfo?(dchaplyg)
Nikolai Sednev 2017-04-25 15:15:43 UTC CC mkalinin
Flags needinfo?(mkalinin)
Elad 2017-04-25 16:17:07 UTC CC ebenahar
Denis Chaplygin 2017-04-26 07:42:15 UTC Flags needinfo?(dchaplyg) needinfo?(mkalinin)
Denis Chaplygin 2017-04-26 07:42:50 UTC Flags needinfo?(mkalinin)
Sandro Bonazzola 2017-07-18 15:31:50 UTC Target Milestone ovirt-4.1.4 ovirt-4.1.5
Sandro Bonazzola 2017-07-18 15:32:29 UTC Status MODIFIED POST
Germano Veit Michel 2017-07-19 03:38:46 UTC CC gveitmic
Yaniv Kaul 2017-08-07 17:52:34 UTC Severity low urgent
Doron Fediuck 2017-08-10 12:25:58 UTC Target Milestone ovirt-4.1.5 ovirt-4.1.6
Marina Kalinin 2017-08-10 21:08:37 UTC Flags needinfo?(mkalinin) needinfo?(dchaplyg)
Denis Chaplygin 2017-08-11 08:19:50 UTC Flags needinfo?(dchaplyg)
Marina Kalinin 2017-08-14 20:51:41 UTC Flags needinfo?(dchaplyg)
Marina Kalinin 2017-08-14 21:35:30 UTC CC lveyde
Flags needinfo?(lveyde)
Lev Veyde 2017-08-14 22:17:03 UTC Flags needinfo?(dchaplyg) needinfo?(lveyde)
Marina Kalinin 2017-08-15 02:34:21 UTC Flags needinfo?(dchaplyg)
Martin Sivák 2017-08-23 10:33:15 UTC Keywords TestOnly
Flags needinfo?(nsednev)
Martin Sivák 2017-08-23 10:38:18 UTC Depends On 1479768
Nikolai Sednev 2017-08-23 16:16:46 UTC Flags needinfo?(dchaplyg) needinfo?(nsednev)
Yaniv Kaul 2017-09-05 10:06:27 UTC Link ID oVirt gerrit 75990
Sandro Bonazzola 2017-09-05 14:15:25 UTC Status POST ON_QA
Target Release --- 2.1.5
Denis Chaplygin 2017-09-06 08:02:22 UTC Doc Text Cause: We are trying to synchronize two different apps, living on their own schedules. And, unfortunately, those schedules are quite different.

Consequence: At the moment Hosted engine updates it's status with about 30 seconds delay and status change propagation from HE to the engine takes about 15 seconds.

So, in worst case, engine will see correct state of HE agent after 75 seconds (30 seconds to report transition from LocalMaintenance state, 30 seconds to report new score, 15 seconds delay on the engine side)

Therefore, when you try to immediately use a host, just returned from the maintenance state, engine is not able to make a correct decision and tries to operate hosted engine, while it is still in a incorrect state.

Workaround (if any): There is no way to fix that behaviour, cause our system is not a realtime system and we have a lot of delays in it (as i mentioned above, waiting for more than 75 seconds between actions should be safe).
Doc Type If docs needed, set a value Known Issue
Nikolai Sednev 2017-09-06 16:40:32 UTC Status ON_QA ASSIGNED
Doc Text Cause: We are trying to synchronize two different apps, living on their own schedules. And, unfortunately, those schedules are quite different.

Consequence: At the moment Hosted engine updates it's status with about 30 seconds delay and status change propagation from HE to the engine takes about 15 seconds.

So, in worst case, engine will see correct state of HE agent after 75 seconds (30 seconds to report transition from LocalMaintenance state, 30 seconds to report new score, 15 seconds delay on the engine side)

Therefore, when you try to immediately use a host, just returned from the maintenance state, engine is not able to make a correct decision and tries to operate hosted engine, while it is still in a incorrect state.

Workaround (if any): There is no way to fix that behaviour, cause our system is not a realtime system and we have a lot of delays in it (as i mentioned above, waiting for more than 75 seconds between actions should be safe).
If this bug requires documentation, please select an appropriate Doc Type value.
Red Hat Bugzilla Rules Engine 2017-09-06 16:40:41 UTC Target Release 2.1.5 ---
Yaniv Kaul 2017-09-11 09:57:53 UTC Target Milestone ovirt-4.1.6 ovirt-4.1.7
Martin Sivák 2017-09-27 11:04:59 UTC Doc Text If this bug requires documentation, please select an appropriate Doc Type value. A hosted engine capable host returning from maintenance can take some time to return to the hosted engine capable status.

It won't be able to receive hosted engine VM before the hosted engine score is restored.

Now lets assume you have a second host that runs hosted engine VM atm and you want to put it into maintenance. The host can stall in Preparing for maintenance if no other hosted engine capable host is available. The easiest way out of that state is activating the host again, waiting before some other hosted engine host is ready and trying again.
Martin Sivák 2017-09-27 11:06:58 UTC Status ASSIGNED CLOSED
Resolution --- CANTFIX
Last Closed 2017-09-27 07:06:58 UTC
Emma Heftman 2017-11-07 10:11:49 UTC CC eheftman
Flags needinfo?(msivak)
Emma Heftman 2017-11-07 15:08:16 UTC Flags needinfo?(msivak) needinfo? needinfo?(dchaplyg)
Emma Heftman 2017-11-07 15:27:04 UTC Doc Text A hosted engine capable host returning from maintenance can take some time to return to the hosted engine capable status.

It won't be able to receive hosted engine VM before the hosted engine score is restored.

Now lets assume you have a second host that runs hosted engine VM atm and you want to put it into maintenance. The host can stall in Preparing for maintenance if no other hosted engine capable host is available. The easiest way out of that state is activating the host again, waiting before some other hosted engine host is ready and trying again.
If no self-hosted engine host is available other than the host that is currently running the self-hosted engine, you will not be able to move the host that runs the Manager virtual machine to maintenance mode. Furthermore, even after another host moves to a status of "Up", it could take a few minutes for it to receive a score that will enable it to run the Manager virtual machine.

The host will remain in a "preparing for maintenance" state until the Manager virtual machine can migrate to another host.
Flags needinfo? needinfo?(dchaplyg) needinfo-

Back to bug 1399766