UMM doesn't respect "COUNTER_RESET_TIME" value
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
High
|
Oleksiy Molchanov | ||
Mitaka |
Fix Released
|
High
|
Oleksiy Molchanov |
Bug Description
--- Environment ---
Mirantis OpenStack: 9.0 + code from stable/mitaka branch on January 22
Environment: All OpenStack nodes are VMs on top of Libvirt+KVM
--- Description ---
A node ends up in maintenance mode (UMM) after the configured number of "unclean" reboots ("REBOOT_COUNT" in umm.conf) even if the period of time between these reboots is longer than the configured one (COUNTER_RESET_TIME in umm.conf).
--- Steps to reproduce ---
1) Deploy a MOS environment on top of Libvirt+KVM
2) Ensure there are default values of "REBOOT_COUNT" and "COUNTER_
cat /etc/umm.conf
UMM=yes
REBOOT_COUNT=2
COUNTER_
3) Kill a Libvirt VM which corresponds to Controller node using virsh then start it immediately
virsh destroy f90-reg-
virsh start f90-reg-
4) Enter the Controller node and check that the operating system has booted properly
$ umm status
runlevel N 2
5) Wait for 15 minutes
6) Kill the same Libvirt VM using virsh then start it immediately
virsh destroy f90-reg-
virsh start f90-reg-
--- Actual behavior ---
The node is in maintenance mode
# umm status
umm
--- Expected behavior ---
Operating system is still boot in runlevel 2
$ umm status
runlevel N 2
Changed in fuel: | |
assignee: | nobody → Oleksiy Molchanov (omolchanov) |
Changed in fuel: | |
status: | New → In Progress |
milestone: | none → 10.x-updates |
Changed in fuel: | |
status: | In Progress → Confirmed |
tags: | added: on-verification |
Changed in fuel: | |
milestone: | 10.x-updates → 10.1 |
Changed in fuel: | |
status: | In Progress → Won't Fix |
sla1 for 9.0-updates