Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix the issue that user can't add alerts.
When seeded from the fixture file, default events in miq_event_definitions table always belong to certain event set. However there are some appliances from 5.6 fresh installation that have some deleted old events showed up in the DB and not belong to any event set. UI for Add a New Alert would not open due to these ghost and orphaned events. So far we can't find out why these deleted events still showed up in a fresh appliance. It is strange. This commit would skip these orphaned events so users can access the Add a New Alert page. https://bugzilla.redhat.com/show_bug.cgi?id=1379854
- Loading branch information
Showing
3 changed files
with
50 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters