Bug 994944

Summary: spacewalk-report crashes with traceback on multival columns
Product: Red Hat Satellite 5 Reporter: Jiří Mikulka <jmikulka>
Component: ServerAssignee: Tomáš Kašpárek <tkasparek>
Status: CLOSED CURRENTRELEASE QA Contact: Jiří Mikulka <jmikulka>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 560CC: cperry, ggainey, tkasparek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spacewalk-reports-2.0.1-4-sat Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-01 21:50:07 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:
Bug Depends On:    
Bug Blocks: 924171    

Description Jiří Mikulka 2013-08-08 09:36:23 UTC
Description of problem:
spacewalk-report is trying to sort multival columns so reports are consistent. But when trying to sort (so far) empty multival column it fails with traceback:

Traceback (most recent call last):
  File "/usr/bin/spacewalk-report", line 247, in ?
    outrow[m] = options.multivalseparator.join(sorted(outrow[m].split(options.multivalseparator)))
AttributeError: 'NoneType' object has no attribute 'split'

Version-Release number of selected component (if applicable):
spacewalk-reports-2.0.1-3.el5sat

How reproducible:
always on report which might have multival column

Steps to Reproduce:
1. create user with more than 1 role
2. run spacewalk-report users
3. see the output

Actual results:
Traceback (most recent call last):
  File "/usr/bin/spacewalk-report", line 247, in ?
    outrow[m] = options.multivalseparator.join(sorted(outrow[m].split(options.multivalseparator)))
AttributeError: 'NoneType' object has no attribute 'split'

Expected results:
users info are shown correctly

Additional info:

Comment 4 Clifford Perry 2013-10-01 21:50:07 UTC
Satellite 5.6 has been released. This bug was tracked under the release.  

This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly
before release). 

Moving to CLOSED CURRENT_RELEASE. 

Text from Upgrade Erratum follows:

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/RHEA-2013-1395.html