The scheduler can pick a non working Host
|Assignee:||Ruben S. Montero||% Done:|
|Target version:||Release 3.6|
|Affected Versions:||OpenNebula 3.0|
The scheduler filters the existing hosts to get the ones with a status less than 3, including the ones in INIT or MONITORING state.
A Host in MONITORING state may be chosen to deploy a VM if there is old monitoring data in it, but the host may be unreachable and end in ERROR state.
Revert "Bug #766: Scheduler only filters Hosts in MONITORED state"
This reverts commit f162b2c4a97a14f3057f120948bd6cacaf74e7a9.
bug #766: Update OCA (Ruby & Java) to make use of the new monitoring state. Update onehost command.
#3 Updated by Carlos Martín almost 9 years ago
- Status changed from Closed to Assigned
- % Done changed from 100 to 0
- Resolution deleted (
The previous commit didn't solve the issue, because a host in MONITORED state changes periodically to MONITORING in each monitoring cycle. With a small monitoring timer, the scheduler couldn't find any host in MONITORED.
We will have to implement one of the following options:
- Automatically disable a Host after N unsuccessful monitor events.
- Introduce a new state, to differentiate a host being monitored to refresh its info (valid candidate for deployment), or to recover from an ERROR state.