Bug 911172

Summary: Creating mail server fails with EAP 6.1.0.DR4 if outbound-socket-binding-ref is not filled, but the UI doesn't force to fill this field
Product: [JBoss] JBoss Operations Network Reporter: Radim Hatlapatka <rhatlapa>
Component: Plugin -- JBoss EAP 6Assignee: Thomas Segismont <tsegismo>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: low Docs Contact:
Priority: unspecified    
Version: JON 3.1.2CC: jstefl, myarboro, 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: 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 Radim Hatlapatka 2013-02-14 14:30:44 UTC
Description of problem:
When creating Mail Server (e.g. imap) then it fails with if outbound-socket-binding-ref is not filled:
JBAS014746: outbound-socket-binding-ref may not be null, rolled-back=true

But the field is not set as required in the UI.

Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:

1. start EAP 6.1.0.DR4 in standalone mode
2. Import it to JON
3. Under mail component create a new mail session (or use the default)
4. in the mail session via create new child try to create new mail server (it doesn't matter if imap, pop3 or smtp)
5. Leave outbound-socket-binding-ref as is (not specified) and finish the wizard

  
Actual results:

Mail server is not created and in child history in status of the operation is failed with error:
JBAS014746: outbound-socket-binding-ref may not be null, rolled-back=true


Expected results:

Either enforcing user to not be able to submit a request for mail server creation without specifying this field or not to require having this field filled (as was the behaviour in older versions)


Additional info:

Comment 1 Thomas Segismont 2013-02-18 11:15:48 UTC
IMO, we should force the field to be filled. Will discuss this with the team

Comment 2 Thomas Segismont 2013-02-19 11:50:49 UTC
Fixed in master: 7189891

Not sure where I should cherry-pick this one to.

Comment 3 Charles Crouch 2013-02-25 21:29:43 UTC
Setting this to MODIFIED as it will be available in the next build of JON320

Comment 4 Larry O'Leary 2013-09-06 14:31:45 UTC
As this is MODIFIED or ON_QA, setting milestone to ER1.

Comment 5 Jan Stefl 2013-09-26 12:53:18 UTC
JON 3.2 verified - OK