Bug 848868
Summary: | Purging plugins still leaves traces in the database? | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Lukas Krejci <lkrejci> |
Component: | Core Server | Assignee: | RHQ Project Maintainer <rhq-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | Mike Foley <mfoley> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 4.5 | CC: | hrupp, jsanda, myarboro |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-11-20 20:41:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lukas Krejci
2012-08-16 15:54:19 UTC
I ran through the repro steps 3 times without seeing this problem. I did on one pass get a deadlock in the async resource delete process during what looked like plugin purge time. But I couldn't reproduce it and it did not seem to affect anything negatively. I wonder if maybe the above happens if you mistakenly deploy slightly before the purge is done. I'm not sure if the UI is the perfect indicator, although I have no reason to think it's not. All in all I still don't completely trust plugin purge but I don't see a blatant issue. As per 8/20 triage 8/20 pushing to JON312 This is the same problem as bug 869063. See comment 3 in bug 869063 for a detailed explanation. The short version is that we were allow the row in the rhq_plugin table to get deleted in the db before all of the resource types were purged. This is bad because it allows you to re-install a plugin while it is still in the process of being purged. My fix for bug 869063 which should also address this bug changes the plugin purge logic such that the purge does not happen until all resource types have first been purged. *** This bug has been marked as a duplicate of bug 869063 *** |