RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1314763 - targetcli: Call trace when executing invalid command when using python
Summary: targetcli: Call trace when executing invalid command when using python
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: fcoe-target-utils
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Maurizio Lombardi
QA Contact: Bruno Goncalves
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-04 12:26 UTC by Bruno Goncalves
Modified: 2017-12-06 11:22 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 11:22:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Bruno Goncalves 2016-03-04 12:26:34 UTC 
Description of problem:
Got call trace when executing an invalid command when target targetcli from a python script.

Traceback (most recent call last):
  File "/usr/bin/targetcli", line 90, in <module>
    main()
  File "/usr/bin/targetcli", line 73, in main
    shell.run_cmdline(" ".join(sys.argv[1:]))
  File "/usr/lib/python2.6/site-packages/configshell/shell.py", line 934, in run_cmdline
    self._execute_command(path, command, pparams, kparams)
  File "/usr/lib/python2.6/site-packages/configshell/shell.py", line 899, in _execute_command
    self.log.error(msg)
  File "/usr/lib/python2.6/site-packages/configshell/log.py", line 159, in error
    self._log('error', msg)
  File "/usr/lib/python2.6/site-packages/configshell/log.py", line 112, in _log
    self.con.display(msg)
  File "/usr/lib/python2.6/site-packages/configshell/console.py", line 151, in display
    self.raw_write(text)
  File "/usr/lib/python2.6/site-packages/configshell/console.py", line 139, in raw_write
    self._stdout.write(text)
TypeError: argument 1 must be string or read-only character buffer, not exceptions.ValueError


Version-Release number of selected component (if applicable):
fcoe-target-utils-2.0rc1.fb16-6.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1.Run the following script
# python
>>> import subprocess
>>> p=subprocess.Popen("targetcli /tcm_fc/10:00:5c:b9:01:c1:ec:75/ ls", stdout=subprocess.PIPE, stderr=subprocess.PIPE, shell=True)
>>> stdout, stderr = p.communicate()
>>> print stderr


####### 

I do not see the call trace if I run the command directly from shell.
# targetcli /tcm_fc/10:00:5c:b9:01:c1:ec:75/ ls
No such path /tcm_fc/10:00:5c:b9:01:c1:ec:75
Comment 3 Jan Kurik 2017-12-06 11:22:16 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.