| 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: | Pulp | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Ivan Necas <inecas> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.2 | CC: | 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
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. 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 Thanks for the details! This was fixed upstream in pulp 2.8.5. https://pulp.plan.io/issues/858 This can probably be closed as a duplicate of this: https://bugzilla.redhat.com/show_bug.cgi?id=1209623 The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug. The Pulp upstream bug priority is at High. Updating the external tracker on this bug. All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST. 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: 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
|