[
https://issues.jboss.org/browse/WFCORE-3217?page=com.atlassian.jira.plugi...
]
Brian Stansberry updated WFCORE-3217:
-------------------------------------
Description:
WFCORE-2849 fails ops against domain profile resources if the OSH tries to register a
Stage.RUNTIME step. But we are still hitting cases where we have OSHs that try to do this
(see WFLY-9281). Since those OSHs have worked for years without this causing major
trouble, failing the op seems excessive.
Instead I would like to log -a WARN- an INFO, and have the problematic 'addStep'
call simply return without adding the step.
Perhaps this could be a DEBUG, but really if an OSH is doing this it is a bug and I'd
like to not hide that. A WARN OTOH seems too high, as this likely does not harm the end
user and there is nothing they can do about it other than not invoking the op.
was:
WFCORE-2849 fails ops against domain profile resources if the OSH tries to register a
Stage.RUNTIME step. But we are still hitting cases where we have OSHs that try to do this
(see WFLY-9281). Since those OSHs have worked for years without this causing major
trouble, failing the op seems excessive.
Instead I would like to log -a WARN- an INFO, and have the problematic 'addStep'
call simply return without adding the step.
Perhaps this could be a DEBUG, but really if an OSH is doing this it is a bug and I'd
like to not hide that. A WARN OTOH seems to high, as this likely does not harm the end
user and there is nothing they can do about it other than not invoking the op.
Relax the WFCORE-2849 requirement
---------------------------------
Key: WFCORE-3217
URL:
https://issues.jboss.org/browse/WFCORE-3217
Project: WildFly Core
Issue Type: Task
Components: Domain Management
Affects Versions: 3.0.0.Final, 3.0.1.Final
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Blocker
Fix For: 4.0.0.Alpha1, 3.0.2.Final
WFCORE-2849 fails ops against domain profile resources if the OSH tries to register a
Stage.RUNTIME step. But we are still hitting cases where we have OSHs that try to do this
(see WFLY-9281). Since those OSHs have worked for years without this causing major
trouble, failing the op seems excessive.
Instead I would like to log -a WARN- an INFO, and have the problematic 'addStep'
call simply return without adding the step.
Perhaps this could be a DEBUG, but really if an OSH is doing this it is a bug and I'd
like to not hide that. A WARN OTOH seems too high, as this likely does not harm the end
user and there is nothing they can do about it other than not invoking the op.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)