Red Hat Bugzilla – Bug 109152
redundant tables in database
Last modified: 2014-04-25 15:53:28 EDT
check_suite_probe and check_suite_member_probes contain redundant data. This appears to be an artifact of the probe_schema refactor. Apparently check_suite_probe was originally not a subclass of probe. When check_suites was created as a subclass of probe and its data was populated, check_suite_probe should have gone away. Both classes are being used by the dynamo code (check_suite_probe more heavily than check_suite_member_probe).
# How was this issue addressed? Dropped table check_suite_member_probe and replaced references to it with check_suite_probe. # What level of users are affected? Only the non-existent monitoring UI is impacted. # Where specifically can the change be seen? Database schema only # If the change cannot be verified visually, how should it be tested? 1) sqlplus command: "desc check_suite_member_probe" should not be able to find the table after the monitoring schema is deployed 2) monitoring schema should deploy check_suite_member_probe cleanly
Transfering to Peter to mark as ON_DEV when he pushes the monitoring schema to webdev.
on dev
actually, #2 should read: 2) monitoring schema should deploy check_suite_probe cleanly That being the case, this bug passes qa.
is there a test plan for this?
ok, I obviously didn't read this thread carefully. I now see the test plan thanks to the observant eyes of gdk.
Looks good in DB.