Bug 1397447

Summary: Red Hat Satellite didn't update Errata based on date if metadata was updated after errata publication
Product: Red Hat Satellite Reporter: Franck Grosjean <fgrosjea>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Ivan Necas <inecas>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.2CC: bbuckingham, bmbouter, crt.hebergement, daviddavis, dkliban, fgrosjea, ggainey, inecas, ipanova, jcallaha, mhrivnak, mkalyat, pcreech, rchan, ttereshc
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:51: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:

Description Franck Grosjean 2016-11-22 14:32:01 UTC
Description of problem:

Updated metadate from a published errata on CDN didn't update satellite content

Version-Release number of selected component (if applicable):

Red Hat Enterprise 7
Red Hat Satellite 6.2.2

How reproducible:

Update metadata on an errata into CDN and sync Red Hat Satellite

Steps to Reproduce:
1. Update metadata on an errata into CDN
2. Sync Red Hat Satellite
3. Errata not updated on Red Hat Satellite

Actual results:

Red Hat Satellite doesn't download new errata

Expected results:

Red Hat Satellite download new errata based on new Update date in errata

Additional info:

Link bugzilla : https://bugzilla.redhat.com/show_bug.cgi?id=1383702

Comment 4 Michael Hrivnak 2016-11-28 13:47:32 UTC
It would also be helpful to have a specific repo, a specific errata ID, the time at which the repo was sync'd, and where exactly you looked to see that the errata was not updated. This issue will be difficult to reproduce without those details.

I'm not sure if this explains what you saw, but it's important to know that when an erratum gets updated, that change isn't visible until the repo gets published. Usually that happens right after the sync, but if an erratum shows up in more than one repo, there may not be a publish automatically triggered for those other repos.

I'm not sure what to put in an upstream pulp bug report given the info currently on this issue, so please NEEDSINFO me again when there are additional details available.

Comment 5 Franck Grosjean 2016-11-28 13:57:28 UTC
Here after the specific errata with original wrong metadata

----------------------------------------------------------
hammer erratum info --id RHBA-2015:1426 --repository-id 2
ID:          ff2f1623-0fe6-4c7b-b32d-9530b02237bd
Errata ID:   RHBA-2015:1426
Title:       grub bug fix update
Type:        bugfix
Severity:    
Issued:      2015-07-22  <---- match info from access.redhat.com
Updated:     2015-04-07  <---- Back to the futur ?

Description: The grub packages provide Grand Unified Boot Loader (GRUB), a boot loader
capable of booting a wide variety of operating systems.
----------------------------------------------------------

those metadata were fixed by Red Hat support but Satellite 6 still refuses to sync this errata again. it sounds like since this errata already exists satellite doesn't try to (re)sync it

Comment 7 Michael Hrivnak 2016-12-02 21:45:50 UTC
Thanks for the details! This was fixed upstream in pulp 2.8.5.

https://pulp.plan.io/issues/858

Comment 8 Michael Hrivnak 2016-12-02 21:46:46 UTC
This can probably be closed as a duplicate of this: https://bugzilla.redhat.com/show_bug.cgi?id=1209623

Comment 9 pulp-infra@redhat.com 2016-12-02 22:03:34 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 10 pulp-infra@redhat.com 2016-12-02 22:03:36 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.

Comment 11 pulp-infra@redhat.com 2016-12-02 22:03:39 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 15 Ivan Necas 2017-09-06 12:28:08 UTC
Verified against Satellite 6.3 Beta, snap 14

Steps:

1. synchronize https://inecas.fedorapeople.org/fakerepos/update-errata/
2. show errata details:
h erratum info --repository-id 3  --id 'RHEA-2012:1013'
ID:          4e187e1d-f10f-487f-b62b-4bbd631b6c61
Errata ID:   RHEA-2012:1013
Title:       Gorilla_Erratum
Type:        bugfix
Severity:    moderate
Issued:      2013-01-08
Updated:     2013-01-09
Description: Gorilla_Erratum
Summary:     
Solution:
3. update updated at attribute on errata and synchronize again https://inecas.fedorapeople.org/fakerepos/update-errata/
4. the updated attribute changed properly
h erratum info --repository-id 3  --id 'RHEA-2012:1013'
ID:          4e187e1d-f10f-487f-b62b-4bbd631b6c61
Errata ID:   RHEA-2012:1013
Title:       Gorilla_Erratum
Type:        bugfix
Severity:    moderate
Issued:      2013-01-08
Updated:     2013-01-10
Description: Gorilla_Erratum
Summary:     
Solution:

Comment 16 Satellite Program 2018-02-21 16:51:07 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