Bug 846785
Summary: | RHQ: Unable to create ESB deployment manually for SOA-P 4.3.0 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Stefan Negrea <snegrea> | ||||
Component: | Content | Assignee: | Stefan Negrea <snegrea> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 4.4 | CC: | hrupp, ldimaggi, mvecera, tcunning | ||||
Target Milestone: | --- | ||||||
Target Release: | RHQ 4.5.0 | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | 836527 | Environment: | |||||
Last Closed: | 2013-09-01 10:08:15 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: | |||||||
Bug Depends On: | 836527 | ||||||
Bug Blocks: | 841939 | ||||||
Attachments: |
|
Description
Stefan Negrea
2012-08-08 16:58:53 UTC
master branch commit: http://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?id=b97ed4379723df4bd78d5a101094ada80097025e SOA-P 4.3.0.GA_CP5 and JON 3.1.1.ER2: https://brewweb.devel.redhat.com/buildinfo?buildID=228250 There is not an exception in the agent log anymore, but the ESB archive is not in the SOA-P and JON deployed. Created attachment 609616 [details] JON 3.1.1.CR1 DEBUG logs JON 3.1.1.CR1: https://brewweb.devel.redhat.com/buildinfo?buildID=231258 did not fix the bug for SOA-P 4.3.0. Adding JON debug logs. This bug is applicable to RHQ only. Please retest with the latest version of RHQ to verify that the issue has been resolved. Also, please augment the replication steps from the bug description with a manual discovery. That is, after you run all the replication from the bug description, please wait 10 minutes, run discovery manually, wait another 10 minutes, and then check to see if the SOA-P resource was discovered. The 10 minutes wait between tasks is a good practice given the fact that most of the work is done by the content system. The fact that there are no errors in the logs is an indication that deployment and resource creation succeeded. From what I can see using 3.1.1 CR1, this does work. I see the ESB archive in both SOA-P 4.3.0 and in JON after hitting refresh in the child resources a few times. Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since. |