Bug #21026: Notification not cleared when there is no other discovered host - Foreman

Bug #21026

Notification not cleared when there is no other discovered host

Added by Sebastian Gräßl 10 months ago. Updated 10 days ago.

Status:	Closed
Priority:	Normal
Assignee:	Sebastian Gräßl
Category:	Notifications
Target version:	1.17.0
Difficulty:		Team Backlog:
Triaged:		Fixed in Releases:
Bugzilla link:	1488998	Found in Releases:
Pull request:	https://github.com/theforeman/foreman/pull/4861

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1488998

Description of problem:

No notification regarding Discovery Host should be visible when there is no one available (see screenshot).

How reproducible:

Always

Steps to Reproduce:
1. Create a Discovery Host
2. Delete the Discovery Host

Actual results:

There is a notifications regarding discovery host even in its absence.

Expected results:

No notifications regarding discovery host.

Associated revisions

Revision 6d6adc3a
Added by Sebastian Gräßl 9 months ago

Fixes #21026 - Clear cached notifications properly

Using `delete_all` for has_many does not trigger callbacks
on the associated objects, `dependent: :destroy` does.

Clearing the cache needs to happen anytime a notification
gets created, modified and destroyed, `after_commit`
will be triggered on all o these occasions.

History

#1 Updated by Sebastian Gräßl 10 months ago

Subject changed from Notification not cleared when there is not discovered host to Notification not cleared when there is not discovered host
Assignee set to Sebastian Gräßl

#2 Updated by Sebastian Gräßl 10 months ago

Project changed from Discovery to Foreman
Subject changed from Notification not cleared when there is not discovered host to Notification not cleared when there is no other discovered host
Category set to Notifications