Bug 1198785

Summary: [GSS] (6.4.z) Appending :remove to a CLI command without a qualifier removes the entire subsystem
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Matthew Robson <mrobson>
Component: CLIAssignee: Alexey Loubyansky <olubyans>
Status: CLOSED DUPLICATE QA Contact: Petr Kremensky <pkremens>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.3CC: brian.stansberry, dereed
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 06:17:17 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 Matthew Robson 2015-03-04 19:52:36 UTC 
Description of problem:
Appending :remove to a CLI command without a qualifier removes the entire subsystem.

Removes entire logging subsystem, as expected.

/subsystem=logging:remove()


Also removes entire logging subsystem when the package is missing from the logger.

/subsystem=logging/logger=:remove

These all show the same results, removes the entire logging subsystem:

/subsystem=logging/:remove
/subsystem=logging/root-logger=:remove
/subsystem=logging/syslog-handler=:remove
ect..

Seems to apply to anything, just adding :remove gets rid of the entire subsystem even if you don't have a syslog-handler or root-logger configured.

Removes the entire datasource subsystem:

/subsystem=datasources/data-source=:remove


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

How reproducible:
100%


Steps to Reproduce:
1. Start a clean EAP container.
2. Start CLI
3. Execute CLI command as above


Actual results:
Entire subsystem is removed.

Expected results:
Should result in an error as it's not a valid command or the intended action.

Additional info:
Comment 1 Petr Kremensky 2015-03-05 06:17:17 UTC 

*** This bug has been marked as a duplicate of bug 1169342 ***