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 1444701

Summary: Failed to run virt-who for rhevm4.1 with "KeyError: 'major'"
Product: Red Hat Satellite Reporter: Eko <hsun>
Component: PackagingAssignee: Eric Helms <ehelms>
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: urgent Docs Contact:
Priority: high    
Version: 6.2.9CC: bbuckingham, bcourt, bkearney, cwelton, egolov, ehelms, hsun, jcallaha, khowell, ktordeur, ktrufano, pcreech, pgagne, rjerrido, sgao, syangsao, tomckay, xdmoon, yuefliu
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: virt-who-0.19-5.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1436517 Environment:
Last Closed: 2018-02-21 16:54:17 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: 1436517    

Comment 2 Eko 2017-05-10 01:48:05 UTC
yes, this issue is fixed by the latest virt-who(virt-who-0.19-4.el7), but it's not shipped with satellite6.2.9, we need someone to sync the latest virt-who for SatTools repo.

Comment 6 Eko 2017-07-24 12:36:58 UTC
*** Bug 1473781 has been marked as a duplicate of this bug. ***

Comment 7 Eko 2017-07-25 05:50:28 UTC
The new virt-who package(virt-who-0.20.2-1.el6/7sat) is available in brew, but it's only for satellite-6.3, could we make it available for satellite-6.2 as well? because satellite6.2.11 is in progress. 
Thanks.

Comment 9 Eko 2017-07-25 06:39:08 UTC
virt-who testing for sat6.2.11 and sat6.3.0 are blocked by this BZ, 
besides this BZ, there is another blocker issue #1463996 caused by virt-who-0.19,
I have run some basic testing with virt-who-0.20.2-1, both of the blocked issues are fixed already,
so in my opinion, virt-who-0.20.2 is the better choice.

Comment 12 Perry Gagne 2017-10-10 17:42:07 UTC
Hey Eko is this something your team should be verifying? THis just looks to be a clone of a 6.2 bug verified by your team?

Comment 13 Eko 2017-10-12 02:12:31 UTC
Hi perry, yes, we will continue to follow this issue, thanks for the reminder.

Comment 15 Eko 2017-10-17 03:23:07 UTC
As the customers can use the repo "rhel-6-server-satellite-tools-6.3-rpms" in RHEL6.9, thus "virt-who-0.20.4-1.el6sat.noarch.rpm" can be installed to fix this issue, so I marked it to verified.

if virt-who-0.20.4-1.el6sat is not available for rhel6.9, may be we need to re-open it again, Thanks.

Comment 22 Satellite Program 2018-02-21 16:54:17 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.
> 
> https://access.redhat.com/errata/RHSA-2018:0336