Bug 743426
Summary: | cannot purge latest individual plugin config history item | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Mike Foley <mfoley> |
Component: | Core Server | Assignee: | Nobody <nobody> |
Status: | NEW --- | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.1 | CC: | hrupp, mazz |
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: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike Foley
2011-10-04 21:29:35 UTC
I found that if I have more than one history item, I can delete one of them. But if I have only one left, I can't delete it. This might be OK (since it probably is pointing to the current config). but we should bomb out like this and we probably should not try to purge it at all if we really aren't allowing us to remove the last one. Not sure what the full issue is here, but certainly I was able to delete history items but only if it wasn't the last one left in the list. ok, narrowed it down. It turns out this error occurs when you attempt to delete the LATEST plugin config history item. To test: 1) go to RHQ Agent resource 2) change a plugin config (aka connection property) setting to anything 3) repeat step 2 a couple more times - get N update history items 4) Go to Inventory>ConnectionPropertyHistory and see your N history items 5) try to delete the LATEST one (see the timestamp to determine that) notice you get an error the buttons are probably disabled now due to the bad error. Just navigate away and then back again to this page. Now try to delete any history item that IS NOT the latest history item. You'll find you can do it successfully. So, I think it is probably OK that we don't delete the latest history item. We are preserving the current history item in effect. HOWEVER, we should not bomb out with this ugly error. We should spit out a yellow warning message saying "you can't remove the latest update history item". We do something very similar for the RESOURCE config history list - do the same test but for resource config changes and you'll see you'll get a yellow warning saying you can't delete the current history item. a restriction in the code and architecture. should not get ugly error message. |