Skip to content

Redefine bucket/resource alerts to be more exact #18

@jeniawhite

Description

@jeniawhite

Following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1760358

Description of problem:

If a noobaa bucket's underlying AWS bucket is deleted,  Object Service dashboard doesn't show the correct "Target S3 bucket does not exist" alert that can be found in Noobaa UI, but the rather misleading "A NooBaa bucket awsbucket is using all of its capacity" and "A NooBaa bucket awsbucket is using 100% of its capacity" 


Version-Release number of selected component (if applicable):

OpenShift version: 4.2.0-0.nightly-2019-09-30-184859


How reproducible:

100%


Steps to Reproduce:

1. Add an AWS bucket as a cloud resource in Noobaa
2. Create a noobaa bucket connected to this resource
3. Delete the AWS bucket


Actual results:

Object Service dashboard shows alerts that the noobaa bucket is using all of its capacity


Expected results:

Object Service dashboard makes it clear to the user what is actually wrong with the bucket

We should change the alerts and trigger a single alert in such cases.
2019-10-10_object_service_dashboard (1)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions