You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a replication object with volume out of sync gets deleted, the metrics still show that this object is still out of sync.
Steps to reproduce
Create a replicationSource with the wrong destination address for the metric volsync_volume_out_of_sync is equal to 1. Now delete the replicationSource object and check the metrics again.
Expected behavior
Expected the metrics gauge value to be 0 when the object is deleted.
Actual results
the metrics stay as 1 even when the replication object gets deleted
Additional context
As per my understanding, the gauge metric should be reverted to 0 when the replication object gets deleted. Showing that there is a volume out of sync for a delete replication object creates confusion.
The text was updated successfully, but these errors were encountered:
Describe the bug
When a replication object with volume out of sync gets deleted, the metrics still show that this object is still out of sync.
Steps to reproduce
Create a replicationSource with the wrong destination address for the metric
volsync_volume_out_of_sync
is equal to 1. Now delete the replicationSource object and check the metrics again.Expected behavior
Expected the metrics gauge value to be 0 when the object is deleted.
Actual results
the metrics stay as 1 even when the replication object gets deleted
Additional context
As per my understanding, the gauge metric should be reverted to 0 when the replication object gets deleted. Showing that there is a volume out of sync for a delete replication object creates confusion.
The text was updated successfully, but these errors were encountered: