Bug 1232890
| Summary: | [GSS] CLI Does Not Log History With "--file" and "--command(s)" Args | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Niall Munnelly <nmunnell> |
| Component: | CLI | Assignee: | Peter Palaga <ppalaga> |
| Status: | CLOSED WONTFIX | QA Contact: | Petr Kremensky <pkremens> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3.3 | CC: | bbaranow, bmaxwell, brian.stansberry, dchia, msochure, ppalaga |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-24 11:58:03 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: | |||
Should also note that the customer has history enabled in the CLI, as does my own installation. |
Description of problem: The CLI logs history in an interactive session, but commands run via the --file and --command or --commands arguments are not logged. This is affecting the customer's ability to troubleshoot an ongoing problem with management via the CLI. Version-Release number of selected component (if applicable): Seen in EAP versions 6.3.3GA and earlier; may be extant in 6.4, aswell. How reproducible: Readily reproducible Steps to Reproduce: 1. cp /dev/null ~/.jboss-cli-history 2. file ~/.jboss-cli-history [returns "empty"] 3. echo "/core-service=management/management-interface=native-interface:read-resource(recursive=true)" > ./foo.cli 4. cat foo.cli [should return the single line] 5. ./bin/jboss-cli.sh --connect --controller=localhost:9999 --file=foo.cli { "outcome" => "success", "result" => { "interface" => undefined, "port" => undefined, "security-realm" => "ManagementRealm", "socket-binding" => "management-native" } } 6. [nmunnell@nmunnell jboss-eap-6.3]$ file ~/.jboss-cli-history /home/nmunnell/.jboss-cli-history: empty 7. [nmunnell@nmunnell jboss-eap-6.3]$ ./bin/jboss-cli.sh --connect --controller=localhost:9999 --command="/core-service=management/management-interface=native-interface:read-resource(recursive=true)" { "outcome" => "success", "result" => { "interface" => undefined, "port" => undefined, "security-realm" => "ManagementRealm", "socket-binding" => "management-native" } } 8. [nmunnell@nmunnell jboss-eap-6.3]$ file ~/.jboss-cli-history /home/nmunnell/.jboss-cli-history: empty 9. [nmunnell@nmunnell jboss-eap-6.3]$ ./bin/jboss-cli.sh --connect --controller=localhost:9999 [standalone@localhost:9999 /] /core-service=management/management-interface=native-interface:read-resource(recursive=true) { "outcome" => "success", "result" => { "interface" => undefined, "port" => undefined, "security-realm" => "ManagementRealm", "socket-binding" => "management-native" } } [standalone@localhost:9999 /] quit 10. [nmunnell@nmunnell jboss-eap-6.3]$ file ~/.jboss-cli-history /home/nmunnell/.jboss-cli-history: ASCII text 11. [nmunnell@nmunnell jboss-eap-6.3]$ cat ~/.jboss-cli-history /core-service=management/management-interface=native-interface:read-resource(recursive=true) quit Actual results: CLI does not print commands to .jboss-cli-history when passing --file and --command args. Expected results: CLI should log the commands run as it does when they are run from within the CLI. Additional info: We're trying to help the customer resolve support case 0145433 (https://c.na7.visual.force.com/apex/Case_View?id=500A000000RPVwG&sfdc.override=1), but cannot log the commands they run using jboss-cli.sh --file or --commands.