Reenabling the monitoring fails in v5.2
Problem
With the latest release, we can disable the monitoring, but now we are not able to enable it back.
appbert.log:
It seems that the delete task is still in progress according to appbert.
Checking the appbert logs again, we can see that the delete task has now been completed.
Now if we enable monitoring from the UI it gets enabled without any issues. So immediately after disabling the monitoring, we cannot enable monitoring again as the Delete task was still InProgress. Once the delete task was in a Complete state we can enable monitoring.
Environment
- Platform9 Managed Kubernetes - v4.0 and Higher
Was this page helpful?