Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 864372

Summary:	CLI - some keys does not work in "shell"
Product:	Red Hat Satellite	Reporter:	Hayk Hovsepyan <hhovsepy>
Component:	API	Assignee:	Martin Bacovsky <mbacovsk>
Status:	CLOSED ERRATA	QA Contact:	Corey Welton <cwelton>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	asettle, bkearney, dmacpher, gkhachik, inecas, mbacovsk, mmccune, omaciel
Target Milestone:	Unspecified	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Arrow keys and Tab failed to execute when typing commands in the System Engine shell. As a result, auto-completion failed. This fix encodes stdout to run commands. Arrow keys and Tab are now active.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-04 19:57:04 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 Hayk Hovsepyan 2012-10-09 09:19:08 UTC

Description of problem:
Open katello CLI by "katello -u admin -p admin shell".
Try to type some commands by using "tab", "left", "right", "up", "down" keys.
They does not work.

Version-Release number of selected component (if applicable):
katello-configure-1.1.9-7.el6cf.noarch
katello-common-1.1.12-14.el6cf.noarch
katello-1.1.12-14.el6cf.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-agent-1.1.2-1.el6cf.noarch
katello-certs-tools-1.1.8-1.el6cf.noarch
katello-selinux-1.1.1-1.el6cf.noarch
katello-glue-pulp-1.1.12-14.el6cf.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-cli-1.1.8-7.el6cf.noarch
katello-glue-candlepin-1.1.12-14.el6cf.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-cli-common-1.1.8-7.el6cf.noarch

How reproducible:
always

Comment 2 Ivan Necas 2012-10-09 09:29:02 UTC

Which commands are not working for example? Also only the autocompletion does not work, or the commands itself?

Comment 3 Hayk Hovsepyan 2012-10-09 09:31:39 UTC

Autocompletion does not work.

Comment 5 Bryan Kearney 2012-10-09 12:27:06 UTC

addedbeta 5.

Comment 6 Martin Bacovsky 2012-10-12 10:45:59 UTC

PR for bug #858960 brings in stdout encoding which is not supoprted by python readline that provides shell completion and history. PR  https://github.com/Katello/katello/pull/841 makes the stdout encoding active just for the time the commands executes. 

Merged in commit 28f5d12.

Comment 11 Corey Welton 2012-10-23 15:53:48 UTC

QE verified; arrow keys and tab now work.

CloudForms System Engine Version: 1.1.12-17.el6cf

Comment 13 errata-xmlrpc 2012-12-04 19:57:04 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-1543.html