Bug 1015446
| Summary: | No product type with product-name 'Red Hat JBoss Fuse Service Works' is known | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Libor Zoubek <lzoubek> | |
| Component: | Plugin -- JBoss EAP 6 | Assignee: | Mike Foley <mfoley> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | JON 3.2 | CC: | dbokde, hrupp, kconner, rhatlapa, soa-p-jira, spinder, theute | |
| Target Milestone: | ER03 | |||
| Target Release: | JON 3.2.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1015665 (view as bug list) | Environment: | ||
| Last Closed: | 2014-01-02 20:36:43 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: | ||||
| Bug Blocks: | 1012435, 1015665 | |||
@Libor, this looks like a problem in the latest Fuse plugin. For your SOA testing you could remove or disable the Fuse plugin and this will go away, but we need to raise this as a concern with the Fuse team. They can now be solved on the plugin side using Discovery Callbacks: https://docs.jboss.org/author/display/RHQ/Discovery+Callbacks - Moving out of SOA plugin. - I'm putting assign/needinfo on Dhiraj Bokde so that he can take a look at this. Curious things to note: - Why is the AS7 plugin even involved here? IIRC they are still JMX based but I'll have to look into that further. per jon triage, assigning to soa team Fuse plugins do not support JBoss Fuse Service Works (JFSW), which looks like a customized version of an AS7 server. This is not a Fuse plugin problem since they won't discover JFSW, and as the error is being thrown by the AS7 plugin that's where it should be fixed. Thanks, Dhiraj. @Dhiraj, sorry about that. The conversation about the right fix for this is still going on and we've since agreed that the issue is in the As7 plugin. I was about to update the BZ again before you responded. @Simeon, no worries. I could see why it would be confusing. For a product that uses our group's name 'Fuse', Fuse engineering had no idea what this product was until a week ago. :) kicked back from soa team to jon team. this issue surfaced before and may have been related to .. https://bugzilla.redhat.com/show_bug.cgi?id=998023 soa6 plugin qe (varun/viet) to retest with JON 3.2 ER3. The product name has been changed so that above warning should no longer show up.
master 9adf1e4
- SOA("SOA-P", "JBoss SOA-P 6", "Red Hat JBoss Fuse Service Works", "SOAP"),
+ SOA("SOA-P", "JBoss SOA-P 6", "Red Hat JBoss Fuse Service Works", "Red Hat JBoss Fuse Service Works"),
For the future we need to remove that bogus check and let the layered plugins provide / decide the product name here.
Moving to ON_QA for testing. verified on ER3 |
Description of problem: I am getting an exception in agent log file when I import SOA6 instance Version-Release number of selected component (if applicable): JON 3.2.ER2 + SOA6.1.ER3 How reproducible: always Steps to Reproduce: 1. start soa6 server 2. discover it 3. import it Actual results: ERROR [ResourceContainer.invoker.daemon-22] (rhq.modules.plugins.jbossas7.BaseServerComponent)- Failed to validate product type for ResourceType[id=0, name=JBossAS7 Standalone Server, plugin=JBossAS7, category=Server] [hostConfig: /home/hudson/jboss-soa6/standalone0/configuration/standalone.xml]. java.lang.IllegalArgumentException: No product type with product-name 'Red Hat JBoss Fuse Service Works' is known. at org.rhq.modules.plugins.jbossas7.JBossProductType.getValueByProductName(JBossProductType.java:104) at org.rhq.modules.plugins.jbossas7.BaseServerComponent.validateServerAttributes(BaseServerComponent.java:211) at org.rhq.modules.plugins.jbossas7.BaseServerComponent.getAvailabilityNow(BaseServerComponent.java:154) at org.rhq.modules.plugins.jbossas7.BaseServerComponent.getAvailability(BaseServerComponent.java:139) at org.rhq.modules.plugins.jbossas7.BaseServerComponent.start(BaseServerComponent.java:101) Expected results: Additional info: this exception might be harmless, 'cause I can manage/monitor/configure/deploy with such server as usual