-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cluster moved to un-managed state alert #157
Comments
@ltrilety do you mean this notification should vanish once cluster is imported again? Actually there is no clearing events for this so it remains there. |
@shtripat , I don't think this is an alert condtion. This can be just logged as an event. |
@nthomas-redhat agree. Lets hear from others as well on this and based on that take the action. |
@shtripat @nthomas-redhat I agree that it should not be alert at all. Just an event saying that cluster was un-managed in past and where to look for it's data. |
@ltrilety @nthomas-redhat @r0h4n @shtripat Now the question I think is whether or not an alert is needed. I think we probably don't need to do so as (1) there probably are not many storage administrator users on at the same time managing the same cluster, and (2) the action of manage/unmanage is user-initiated so the user will typically assume it happens once the user initiates the action. What the user expects will be alerts to get his/her attention if the action fails, e.g. unmanage or manage/import fails (and clearing when the failure is no longer presented). |
@julienlim regarding failure of import/un-manage, the task itself would be failed and we already indicate an import failure for a cluster in cluster-list view. |
@julienlim ,I agree with @shtripat. Its a user action and details of failure/success is presented as part of the task itself. Logging an event is good enough is what I am think right now. |
I'm in agreement that we don't need to raise an alert for the manage/unmanage as I already stated so above ("Now the question I think is whether or not an alert is needed. I think we probably don't need to do so as...."). |
Ack. Sending a PR to just log and event with archive location now. |
While un-manage cluster, the archive location was earlier being communicated through a notification. The same is changed to just log as an event as un-manage is always a user triggered action and and event with archive location details is sufficient tendrl-bug-id: Tendrl/notifier#157 Signed-off-by: Shubhendu <[email protected]>
After un-manage and import of cluster I found an alert which is saying that cluster goes to un-manage state. It's not true as the cluster is imported again.
Tested version:
tendrl-commons-1.6.0-1.el7.centos.noarch
tendrl-api-1.6.0-1.el7.centos.noarch
tendrl-ui-1.6.0-1.el7.centos.noarch
tendrl-grafana-selinux-1.5.4-2.el7.centos.noarch
tendrl-ansible-1.5.5-1.el7.centos.noarch
tendrl-notifier-1.6.0-1.el7.centos.noarch
tendrl-node-agent-1.6.0-1.el7.centos.noarch
tendrl-api-httpd-1.6.0-1.el7.centos.noarch
tendrl-selinux-1.5.4-2.el7.centos.noarch
tendrl-grafana-plugins-1.6.0-1.el7.centos.noarch
tendrl-monitoring-integration-1.6.0-1.el7.centos.noarch
The text was updated successfully, but these errors were encountered: