Bug 1198785 - [GSS] (6.4.z) Appending :remove to a CLI command without a qualifier removes the entire subsystem
Summary: [GSS] (6.4.z) Appending :remove to a CLI command without a qualifier removes ...
Keywords:
Status: CLOSED DUPLICATE of bug 1169342
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI
Version: 6.3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Alexey Loubyansky
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-04 19:52 UTC by Matthew Robson
Modified: 2019-04-16 14:40 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-03-05 06:17:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.