Bug 535512 (RHQ-219)
| Summary: | Create New Resource allows a Resource to be added to inventory that has the same resource key as a Resource already in inventorythis | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Ian Springer <ian.springer> |
| Component: | Inventory | Assignee: | RHQ Project Maintainer <rhq-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 0.1 | CC: | ccrouch, cwelton, jshaughn |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://jira.rhq-project.org/browse/RHQ-219 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
RHQ 1.0.RC4
|
|
| Last Closed: | 2014-05-05 21:59:44 UTC | 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
Ian Springer
2008-04-01 20:11:00 UTC
There's another aspect to this. This is the sort of "agent-side validation" we've talked about in the past. The agent-side plugin should be smart enough to check on a create that the resource doesn't exist. Many of our implementations as they stand today don't do that. We apply the static configuration validations server-side (the constraints as described in the configuration). However there are factors are are runtime that must be done on the agent. JNDI name is a good example. All of that mostly talks to point #2 of the original description. As for point #1, yes, the code that handles the create response should check to see if a resource exists in the place the new one will be written rather than relying on the DB to enforce that uniqueness. this would be a nice-to-have, but is likely not going to make it into the 1.1.0 time frame. so, realistically setting this to 2.0 This bug was previously known as http://jira.rhq-project.org/browse/RHQ-219 |