083d38923a
If the first mtcAlive message from a host that was supposed to be rebooted reports uptime in excess of 40 minutes then that means it did not reboot as expected. This was seen to happen during an extended offline case where the host failed heartbeat, then was reported offline during Graceful Recovery which forced a full enable. When the host eventually came back online its reported uptime made it clear that it never rebooted but mtce allowed it to come into service anyway. This is a security issue that can lead to a host disappearing, being security hacked and brought back into the system without reboot. To fix that, this update requires that a host's uptime, reported in its first mtcAlive message, indicate that it has been up for less twice the configured mtcAlive timeout or the enable will fail until it is proven to reset. Story: 2002882 Task: 22845 Change-Id: I9b3ff0bc1ba5af2ca5b07a58db9da9f288b59576 Signed-off-by: Jack Ding <jack.ding@windriver.com> |
||
|---|---|---|
| .. | ||
| centos | ||
| cgts-mtce-common-1.0 | ||
| LICENSE | ||
| PKG-INFO | ||