Project

Profile

Help

Issue #5879

closed

Stale zchunk metadata breaks repo for Fedora 30

Added by mlesieur over 2 years ago. Updated about 2 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.19.1
Platform Release:
OS:
RHEL 7
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

After the fix for issue #4529 was applied to Pulp 2, zchunk metadata is no longer synchronized from repositories resulting in stale zchunk files in the repodata directories. Gzip metatada is updated correctly, but Fedora 30 is synchronizing stale zchunk files from the Pulp server resulting in a broken repository. What is the correct way to purge zchunk metadata from synchronized repositories? Configuring DNF on Fedora 30 to not use zchunk metadata results in a working repository. Zchunk files also found in the EPEL 7 repository. This problem has been observed on Satellite 6.6.1.

[ pulp]# ls l published/yum/http/repos/My_Organization/Library/custom/fedora-linux/fedora-30-updates-x86_64/repodata/
total 59848
-rw-r--r-
. 1 apache apache 2173501 Dec 3 19:02 00fc209ab5b8b7540846378f6e117f9290144c472f16f2125dc9f002e3238cdf-updateinfo.xml.zck
rw-r--r-. 1 apache apache 1693776 Dec 11 19:20 1e889c08ec54eabafe2023efd13c5453eb4f025410087ed72372430fc450ed0b-comps.xml
rw-r--r-. 1 apache apache 3969049 Dec 3 19:02 297893960a45f1b587a3c1b4174a06b1bc438e94bfb6bb035535b1024a179f0f-primary.xml.zck
rw-r--r-. 1 apache apache 5586185 Dec 11 19:19 3749d1f2c4b45f36015828678c79f4fcbeee5d6e06c3abf5abaa4ca5e5621c9c-other.xml.gz
rw-r--r-. 1 apache apache 216 Dec 3 19:02 37eba36c142775610eafb1306260050002b22afcd265f82508d3e87337678b7e-prestodelta.xml.zck
rw-r--r-. 1 apache apache 766905 Dec 11 19:20 3af66aaf8d5405fa29127fdcb20ef8461a047c04e3b2c0cc466e97a2630d46a9-updateinfo.xml.gz
rw-r--r-. 1 apache apache 2199475 Dec 3 19:02 45a7d51c82f5435829e72a2b0ad3e6fa3a6be3b86f6c3701ad2e48f7a44715fc-other.xml.zck
rw-r--r-. 1 apache apache 3657 Dec 11 19:19 62a889d80c247e82e981d199bb12bac33c0211a26d07f857a71d04b8dd857d7d-prestodelta.xml.gz
rw-r--r-. 1 apache apache 16810263 Dec 3 19:02 860c3133cbf7c91940e5702900dcffac87051ea200ede90408609970636eb4c5-filelists.xml.zck
rw-r--r-. 1 apache apache 5716640 Dec 11 19:19 882f9b951543da80dd4d13ac0135819b30eb05e96e429e6dcc549f635483bd78-primary.xml.gz
rw-r--r-. 1 apache apache 456936 Dec 3 19:02 96b92154d1e713885adda27c73eaf63cff633728ea757ac5f3a15c2a16138751-comps-Everything.x86_64.xml.zck
rw-r--r-. 1 apache apache 21872693 Dec 11 19:19 f1e8e19eca81cb29d4eeff44ec4df3a2c85cf8877905a25f2ca8c3b9230a23cc-filelists.xml.gz

[ pulp]# ls l published/yum/http/repos/Connecticut_State_Colleges_and_Universities/Library/custom/Extra_Packages_for_Enterprise_Linux/epel-el7-x86_64/repodata/
total 23784
-rw-r--r-
. 1 apache apache 1544328 Dec 3 19:12 23fd5449abb0af88869db0d40eb59c5c4f40038bfbb4a32c409ff76d6333ea63-updateinfo.xml.zck
rw-r--r-. 1 apache apache 5076721 Dec 10 19:50 4a6e83152b516c989dd5f65587612e14939ba823a5c67882a8ce6d01916485ad-primary.xml.gz
rw-r--r-. 1 apache apache 870116 Dec 10 19:52 6a4e97a0b285002b78f035707ff45734c1d6f44e43debc3b01b049c7f6ef80bc-updateinfo.xml.gz
rw-r--r-. 1 apache apache 12028210 Dec 10 19:50 7d814521b406bea7cecf0d6c2cddbb24544d6c6267ee24d74fb7e35785181620-filelists.xml.gz
rw-r--r-. 1 apache apache 1553 Dec 10 19:50 a99515ffcb90d067b67e5034c58d9daf2f3a27891f0e1a24abb53f79f4addbba-prestodelta.xml.gz
rw-r--r-. 1 apache apache 4429404 Dec 10 19:50 b62d9f521afe5f233f4373565364ff6f697d918382101ca8156fdf1ac2b27812-other.xml.gz
rw-r--r-. 1 apache apache 381860 Dec 10 19:52 c58735af7e39d7896bb726e95f8cb6888714ddc7db09c97cf4e63a226fe329ac-comps.xml
rw-r--r-. 1 apache apache 2913 Dec 10 19:52 repomd.xml

[ ~]# rpm -q pulp-server
pulp-server-2.19.1.1-1.el7sat.noarch
[ ~]# rpm -q satellite
satellite-6.6.1-1.el7sat.noarch

Actions #1

Updated by ipanova@redhat.com over 2 years ago

Have you tried to trigger force publish? This will clean up old/stale metadata and re-generate new one.

Actions #2

Updated by mlesieur over 2 years ago

Yes, I have tried to force a publish. I still get the stale zchunk files in the repodata.

Actions #3

Updated by ggainey over 2 years ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 63
Actions #4

Updated by rchan over 2 years ago

  • Sprint changed from Sprint 63 to Sprint 64
Actions #5

Updated by rchan over 2 years ago

  • Sprint deleted (Sprint 64)
Actions #6

Updated by ttereshc over 2 years ago

To solve it, a migration is needed.
In a migration, yum_repo_metadata_file content units should be checked and zchunk ones should be unassociated from a repo.
After that a force_full publish is recommended to users.
zchunk metadata is identified my data_type which ends with _zck (to be confirmed).

Actions #8

Updated by ttereshc about 2 years ago

  • Status changed from NEW to CLOSED - WONTFIX

Pulp 2 is in maintenance mode and currently accepts only critical/security issues. The main focus is on Pulp 3 and some of the requests will be satisfied in the newer version.We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in Pulp 2. As this issue is not relevant for Pulp 3, we are therefore closing this out as WONTFIX.

Also available in: Atom PDF