Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 886119

Summary:	JON is using JNDI when referring to child Datasource resource instead of specified Resource name
Product:	[JBoss] JBoss Operations Network	Reporter:	Jakub Cechacek <jcechace>
Component:	Plugin -- JBoss EAP 5	Assignee:	Thomas Segismont <tsegismo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	JON 3.1.2	CC:	jcechace, jkudrnac, lfuka, loleary, myarboro, rhatlapa, tsegismo
Target Milestone:	ER01
Target Release:	JON 3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-02 20:34:57 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:

Description Jakub Cechacek 2012-12-11 14:51:41 UTC

After specifying Resource name during the creation of new Datasource JON will refer to created Datasource with its JNDI name instead


Steps to reproduce

1) Create new child Resource of type Local Tx Datasource (for example)
2) In first step of creation wizard fill the Resource name filed.
3) Fill the JNDI name and other mandatory fields.
4) finish the wizard.

Now u can see in EAP server inventory that created child resource is being referenced by its JNDI name. 


Same goes for JMS (Queues and Topics) but in this case resource is being referenced by Queue/Topic name instead of JNDI.

Comment 2 Thomas Segismont 2013-07-25 12:16:39 UTC

The problem is we can't guarantee that a resource will be given the name supplied in the creation wizard when it gets discovered.

See discussion on rhq-devel for the details:
https://lists.fedorahosted.org/pipermail/rhq-devel/2013-July/003103.html

Proposed resolution for this BZ:

A message will be added in the first step of the wizard to indicate that some plugin implementations might not be able to give the resource the supplied name when it gets discovered.

A new BZ will be created to implement a change in the plugin descriptor grammar: plugin developers will be able to say for each resource type if resources can be given a name.

Comment 3 Thomas Segismont 2013-08-05 15:26:49 UTC

Fixed in master

commit 0d9fb46045b844ef4f2a4c921fbe461c37c09c4e
Author: Thomas Segismont <tsegismo>
Date:   Fri Jul 26 14:50:07 2013 +0200

Comment 4 Libor Fuka 2013-09-25 11:59:15 UTC

The problem is still persists with JON 3.2.0.ER1 and EAP 5.2.0.GA

Comment 5 Thomas Segismont 2013-09-25 13:35:08 UTC

Libor, please read https://bugzilla.redhat.com/show_bug.cgi?id=886119#c2.

It has been agreed that for now we would only add a message in the first step of the Create Resource Wizard:

"Not all management plug-ins or their managed resources allow the agent to set the name for a new resource. This value will only be used by agent plug-ins that support the capability. For plug-ins that do not support the capability, the resource may receive a generic or different name when it is discovered."

The original will be later addressed (see BZ1011095)

Comment 6 Radim Hatlapatka 2013-10-14 12:43:07 UTC

Verified in JON 3.2.0.ER3, part where name attribute of the element is not available is being addressed in separate ticket (see BZ1011095)