Bug 907281

Summary: Improper error handling when attempting to remove a server-config with a running server
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Osamu Nagano <onagano>
Component: Domain ManagementAssignee: Brian Stansberry <brian.stansberry>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: low Docs Contact: Russell Dickenson <rdickens>
Priority: low    
Version: 6.0.1CC: brian.stansberry, emuckenh, pkremens
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-17 06:06:38 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 Osamu Nagano 2013-02-04 02:49:22 UTC
Description of problem:
Trying to remove the config for server-one while it's still running produces an uninformative failure:

[domain@localhost:9999 /] /host=master/server-config=server-one:remove
{ "outcome" => "failed", "result" => undefined, "rolled-back" => true, "server-groups" => undefined }

An EAP 6 user reported a similar problem but with a different response:

[domain@localhost:9999 /] /host=xyz/server-config=as1:remove
{
"outcome" => "success",
"result" =>
{ "outcome" => "failed", "failure-description" => "[core-service, path, server-config, system-property, jvm, interface]", "rolled-back" => true },
"failure-description" => undefined
}


Steps to Reproduce:
1. Edit the host.xml so that all servers 'auto-start' to be 'false'.
2. Execute domain.sh. Only the process controller and the domain controller are started.
3. In the jboss-cli.sh, try to remove a server-config then you'll get the error.

[domain@localhost:9999 /] /host=master/server-config=server-three:remove
{
"outcome" => "failed",
"result" =>
{ "outcome" => "failed", "failure-description" => "[core-service, path, server-config, system-property, jvm, interface]", "rolled-back" => true },
"rolled-back" => true
}

4. If there are any running servers, the remove command succeeds as expected.

[domain@localhost:9999 /] /host=master/server-config=server-one:start
{
"outcome" => "success",
"result" => "STARTING"
}
[domain@localhost:9999 /] /host=master/server-config=server-three:remove
{
"outcome" => "success",
"result" =>
{"outcome" => "success"}
}

Comment 3 Petr Kremensky 2014-07-17 06:06:38 UTC
This issue reported against older version, cannot be reproduced against latest 6.3.0. bits, which means it was fixed earlier. Therefore, we are closing this bug. Thank you for reporting this issue.