Bug 1479450

Summary: hammer erratum list order option has no effect
Product: Red Hat Satellite Reporter: Djebran Lezzoum <dlezzoum>
Component: Errata ManagementAssignee: Partha Aji <paji>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: bbuckingham, cwelton, dhlavacd, ehelms, mhulan, tstrachota
Target Milestone: UnspecifiedKeywords: Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 17:30:24 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:

Comment 4 Brad Buckingham 2017-08-14 12:25:52 UTC
Created redmine issue http://projects.theforeman.org/issues/20579 from this bug

Comment 5 Satellite Program 2017-08-17 18:12:49 UTC
Upstream bug assigned to paji

Comment 6 Satellite Program 2017-09-13 20:13:03 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20579 has been resolved.

Comment 7 Corey Welton 2017-10-23 15:38:52 UTC
Seems to be ok in snap 20.

Process:
* Exported CSV as created by method above and edited it to only include errata ids
* Parsed these IDs sequentially, with 'erratum info' hammer command.

[root@dell-per230-02 ~]# cat werrata.txt 
02633f6d-eb20-4932-9715-2bb0d66e07da
95554479-a113-4a45-b870-29423abafa13
7e93f656-1d70-4212-b1b6-47a99ed8d64c
6627346a-6cc5-4628-9022-32602a2d1e5b
[root@dell-per230-02 ~]# for i in `cat werrata.txt`; do hammer -u admin -p changeme --output json erratum info --id $i | grep Issued; done
  "Issued": "2012-01-27",
  "Issued": "2013-01-27",
  "Issued": "2013-01-27",
  "Issued": "2013-01-27",

Result: 
Oldest errata correctly show first.

Comment 8 Bryan Kearney 2018-02-21 17:30:24 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