Bug 1277320

Summary: (6.4.z) JBoss CLI tab completion cannot detect when command is deleted
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Bryan Parry <bparry>
Component: CLIAssignee: Chao Wang <chaowan>
Status: CLOSED EOL QA Contact: Petr Kremensky <pkremens>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.4CC: brian.stansberry, cdewolf, chaowan
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: 2019-08-19 12:44:54 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 Bryan Parry 2015-11-03 02:40:06 UTC 
Description of problem:
In the JBoss CLI when using tab completion, if the CLI presents the user with a choice of the next element, the CLI can "get stuck" if the user deletes [backspace] the command typed so far. If the user tries to exit, the CLI prints an error message.

Version-Release number of selected component (if applicable):
6.4.4

How reproducible:
yes

Steps to Reproduce:
1. Start JBoss in standalone
2. Start the CLI and connect
3. Type "/subsystem=security/security-domain="
4. Press [TAB]
5. Use the Backspace key to remove the text on the line
6. Type "exit" and press Enter
7. Error message is displayed


Actual results:

[standalone@localhost:9999 /] /subsystem=security/security-domain=  [TAB]
jboss-ejb-policy  jboss-web-policy  other             
[standalone@localhost:9999 /] /subsystem=security/security-domain=  [TAB]
jboss-ejb-policy  jboss-web-policy  other             
[standalone@localhost:9999 /]      [BACKSPACE TO CLEAR ALL TEXT] [ENTER]
[standalone@localhost:9999 /] exit
Node type is not complete at index 0
[standalone@localhost:9999 /] 


Expected results:
exit command is successful when typed as described above.
Comment 3 Mike McCune 2016-03-28 22:24:40 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions