Bug 2219757
| Summary: | CRB repo: invalid checksum for postgresql-docs on mirror.stream.centos.org | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | fossrob <fedora> |
| Component: | postgresql | Assignee: | Filip Januš <fjanus> |
| Status: | CLOSED MIGRATED | QA Contact: | RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | CentOS Stream | CC: | alciregi, bstinson, farrotin, jwboyer |
| Target Milestone: | rc | Keywords: | MigratedToJIRA |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| 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: | 2023-09-20 16:33:06 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: | |||
|
Description
fossrob
2023-07-05 07:26:57 UTC
As it was discussed on Discourse, it should be fixed in Cloudfront CDN. curl --silent https://mirror.stream.centos.org/9-stream/CRB/x86_64/os/Packages/postgresql-docs-13.7-1.el9.x86_64.rpm |sha256sum 59930a07af95a826b1d4b182b7895205e71bef2cbd1b5b7e3f992dcd19908dea - Explanation: one of the origin servers behind cloudfront had a corrupted pkg, then served by cloudfront depending on the location. Taken action: - identified which origin node had the problematic pkg and ensuring it got the correct one (it seems rsync doesn't complain which itself is a problem) - invalidated that pkg/path in cloudfront - test that it was serving correct pkg For people in charge of routing from Bugzilla to Jira CS (CentOS Stream) project: you can refer this one and it's already solved but can be used to add more checks to ensure it doesn't happen again Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |