We had this issue back in 3.x days. We found out it was due to a bug in maintenance windows that caused the device to go back into the production state that it was originally entered into zenoss at the end of the window.
↧
We had this issue back in 3.x days. We found out it was due to a bug in maintenance windows that caused the device to go back into the production state that it was originally entered into zenoss at the end of the window.