Bug 1025678

Summary:	Not possible to create log handler without specifying file-relative-to
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Martin Simka <msimka>
Component:	Web Console	Assignee:	Harald Pehl <hpehl>
Status:	CLOSED EOL	QA Contact:	Pavel Jelinek <pjelinek>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	brian.stansberry, hbraun, hpehl, jcordes, jkudrnac, pjelinek
Target Milestone:	ER1
Target Release:	EAP 6.4.0
Hardware:	Unspecified
OS:	Windows
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:47:51 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:	1148698

Description Martin Simka 2013-11-01 09:18:56 UTC

Description of problem:


Version-Release number of selected component (if applicable):
EAP 6.2.0.ER7 - 2.0.5.Final-redhat-1

Steps to Reproduce:
Profiles->Core->Logging->Handler->Size handler->Add and try to create handler with absolute file path without filling up relative-to

Actual results:
Error message: Invalid input: no whitespace, no special chars

Expected results:
Successfully created handler with absolute file path. In CLI is possible to create handler without specifying relative-to.

Additional info:

Comment 1 JBoss JIRA Server 2014-07-09 11:16:36 UTC

Heiko Braun <ike.braun> updated the status of jira HAL-443 to Resolved

Comment 4 Pavel Jelinek 2014-11-26 09:30:43 UTC

Should this still remain in POST state?

Comment 5 Pavel Jelinek 2014-12-09 10:27:34 UTC

Actual results:
I entered some name to 'Name', absolute path to log file to 'File path', leaved 'File Relative To' empty and chose log level than hit save and nothing happened, dialog stayed opened.

Comment 6 Harald Pehl 2014-12-18 09:39:28 UTC

Fixed as part of HAL-505

Comment 7 Harald Pehl 2014-12-18 09:59:40 UTC

*** Bug 1142590 has been marked as a duplicate of this bug. ***

Comment 8 Mike McCune 2016-03-28 22:41:35 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions