Bug 911656

Summary: Postfix Server's Banner basic configuration property "default" value is empty
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: AgentAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED UPSTREAM QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: mazz, mfoley, myarboro, tsegismo
Target Milestone: ---   
Target Release: JON 3.2.0   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 994640 (view as bug list) Environment:
Last Closed: 2013-08-07 17:02:25 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:
Attachments:
Description Flags
postfix_banner_config_empty none

Description Armine Hovsepyan 2013-02-15 14:51:19 UTC
Created attachment 697832 [details]
postfix_banner_config_empty

Description of problem:
Postfix Server's Banner basic configuration property "default" value is empty 

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

How reproducible:
always

Steps to Reproduce:
1. Log in to JON server gui
2. Open postfix server's configuration page
3.
  
Actual results:
The following configuration properties have invalid values and must be corrected before the configuration can be saved: [[Banner]] - red error message is shown on the top of the page.

Expected results:
Either banner property is not required and not error message is visible or the default value is set.

Additional info:
screenshot is attached

Comment 3 John Mazzitelli 2013-04-22 15:54:37 UTC
JON does not ship with nor support the Postfix plugin (I don't even think we'd want to say it works fully with RHQ :-) The Postfix plugin hasn't been worked on in years, I'm not sure what it does or if it even works.

I would close this JON BZ as WONTFIX since the Postfix plugin isn't supported.

Comment 4 Thomas Segismont 2013-08-07 17:02:25 UTC
The issue will be tracked by upstream bug BZ994640