Bug 803516
Summary: | unable to re-import resources | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Libor Zoubek <lzoubek> | ||||||
Component: | Agent, Core Server | Assignee: | Jay Shaughnessy <jshaughn> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||||
Severity: | urgent | Docs Contact: | |||||||
Priority: | urgent | ||||||||
Version: | unspecified | CC: | hrupp, jshaughn, theute | ||||||
Target Milestone: | --- | ||||||||
Target Release: | RHQ 4.4.0 | ||||||||
Hardware: | All | ||||||||
OS: | All | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2013-08-31 09:55:36 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: | |||||||||
Attachments: |
|
Description
Libor Zoubek
2012-03-14 21:29:47 UTC
I did an investigation today and I found out there are other conditions to reproduce. My rhq setup has 2 agents, one is on same host as server - importing this agent is successfull. So problem is on the 2nd agent. There are errors in 2nd agent's log. Created attachment 570241 [details]
2nd agent's debug log
I'm not sure about the two-agent scenario. But I think this issue, at least the originally reported issue, has to do with re-inventory of a previously un-imported resource. Investigating... commit 5f54453db0ec22a717d8cbe029dcaf0535c7f4f2 With the latest changes to availability handling a Resource should always have an associated ResourceAvailability row as well as an Availability row. These are persisted with the Resource. This resolves a problem with that initial persistence of the supporting records. Test Notes: This problem could feasibly have occurred in various scenarios, I think the fix is central and would apply to all of them. So, please re-test any scenarios you may have found suspicious (for example, also test the two-agent scenario above). QE takeaway: https://engineering.redhat.com/trac/jon/ticket/66 verified on Version: 4.4.0-SNAPSHOT Build Number: 88ae0d8 CLI Automation has been added for this BZ. Attachment as evidence. Created attachment 573024 [details]
CLI automation
|