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 1584612 - iotop: ValueError: need more than 1 value to unpack
Summary: iotop: ValueError: need more than 1 value to unpack
Keywords:
Status: CLOSED DUPLICATE of bug 1582821
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iotop
Version: 7.5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-31 10:05 UTC by adam winberg
Modified: 2021-09-09 14:20 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-09 14:29:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1583248 1 None None None 2021-09-09 14:16:13 UTC
Red Hat Knowledge Base (Solution) 3467211 0 None None None 2018-06-12 11:33:59 UTC

Internal Links: 1583248

Description adam winberg 2018-05-31 10:05:13 UTC
Description of problem:
After updating to latest 7.5 kernel, 'iotop' reports error:

Traceback (most recent call last):
  File "/usr/sbin/iotop", line 17, in <module>
    main()
  File "/usr/lib/python2.7/site-packages/iotop/ui.py", line 620, in main
    main_loop()
  File "/usr/lib/python2.7/site-packages/iotop/ui.py", line 610, in <lambda>
    main_loop = lambda: run_iotop(options)
  File "/usr/lib/python2.7/site-packages/iotop/ui.py", line 508, in run_iotop
    return curses.wrapper(run_iotop_window, options)
  File "/usr/lib64/python2.7/curses/wrapper.py", line 43, in wrapper
    return func(stdscr, *args, **kwds)
  File "/usr/lib/python2.7/site-packages/iotop/ui.py", line 501, in run_iotop_window
    ui.run()
  File "/usr/lib/python2.7/site-packages/iotop/ui.py", line 155, in run
    self.process_list.duration)
  File "/usr/lib/python2.7/site-packages/iotop/ui.py", line 434, in refresh_display
    lines = self.get_data()
  File "/usr/lib/python2.7/site-packages/iotop/ui.py", line 415, in get_data
    return list(map(format, processes))
  File "/usr/lib/python2.7/site-packages/iotop/ui.py", line 388, in format
    cmdline = p.get_cmdline()
  File "/usr/lib/python2.7/site-packages/iotop/data.py", line 292, in get_cmdline
    proc_status = parse_proc_pid_status(self.pid)
  File "/usr/lib/python2.7/site-packages/iotop/data.py", line 196, in parse_proc_pid_status
    key, value = line.split(':\t', 1)
ValueError: need more than 1 value to unpack


Version-Release number of selected component (if applicable):
kernel-3.10.0-862.3.2.el7.x86_64
iotop-0.6-2.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. run iotop
2.
3.

Actual results:
Error

Expected results:
No error

Additional info:
Seems to be connected to a change in kernel:
https://unix.stackexchange.com/questions/446624/error-with-command-iotop-on-centos

Comment 4 Andrew Meredith 2018-06-18 10:47:44 UTC
Fix illustrated in: https://unix.stackexchange.com/questions/446624/error-with-command-iotop-on-centos

Comment 5 Andrew Meredith 2018-06-19 09:59:38 UTC
Please note that this fix does indeed solve the issue

Comment 6 Arjen Heidinga 2018-07-05 13:13:18 UTC
I confirm this fixes it.

Comment 7 Michal Hlavinka 2018-07-09 14:29:55 UTC
this is already tracked as bug #1582821 which is in a modified state and if nothing happens, on its way to next rhel update release

*** This bug has been marked as a duplicate of bug 1582821 ***

Comment 8 Andrew Meredith 2018-07-09 14:38:54 UTC
"You are not authorized to access bug #1582821.

Most likely the bug has been restricted for internal development processes and we cannot grant access."

Comment 9 Carl George 2018-07-09 14:40:49 UTC
Please be aware that it's rather annoying for a bug to be closed as a duplicate of a private bug.  Hopefully someone with rights to view bug 1582821 can manually update this bug as future changes are made.

Comment 10 Arjen Heidinga 2018-07-09 14:44:05 UTC
I find it quite odd for a bug, which makes a package utterly useless, to only be fixed at the next update-release. Why not as a regular fix, so that all machines running 7.5 can use this package again (without custom patching/rebuild etc)

Comment 11 Michal Hlavinka 2018-07-10 07:15:22 UTC
@ Andrew and Carl: I know that it's not an ideal situation, that's why I wrote what is going to happen next instead of just closing it as duplicate. Sorry, for the inconvenience. 

@ Arjen: (Almost) all bug fixes are released in batches, except security and similar stuff. That is for the reason to be properly tested and deliver quality updates, which takes some time. If this bug is critical for you with a business impact, please open a support ticket through proper support channels at https://access.redhat.com/support/cases/


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