Project

General

Profile

Actions
Copy link

Bug #31401

closed

can't sync quay.io/foreman/busybox-test to a proxy on nightly

Added by Evgeni Golov about 4 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Container
Target version:
Katello 4.0.0
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Katello 4.0.0
Red Hat JIRA:

Description

Ohai,

while working on https://github.com/theforeman/forklift/pull/1224, I noticed an interesting behaviour on nightly (3.18 and older is OK):

I am syncing quay.io/foreman/busybox-test to Katello, which works fine. But when I try to sync the same content out to the proxy (as done by the fb-proxy.bats test), it fails with:

    # Error: PLP0000: The Manifest digest does not match the expected value. The remote feed announced a digest of sha256:13280b5914050853a87d662c3229d42b61544e36dd4515f06e188835f3407468, but the downloaded digest was sha256:fc5dcad1472b8d34fe1bd242d160f1a337f3c5a2f22c28169656d13e3a14acb4.
    # PLP0000: The Manifest digest does not match the expected value. The remote feed announced a digest of sha256:13280b5914050853a87d662c3229d42b61544e36dd4515f06e188835f3407468, but the downloaded digest was sha256:f389f3a04fa07bca55074cafefe2a70a7b562974ba83c8642d979d003be21abf.
    # PLP0000: The Manifest digest does not match the expected value. The remote feed announced a digest of sha256:13280b5914050853a87d662c3229d42b61544e36dd4515f06e188835f3407468, but the downloaded digest was sha256:087ebbb66938dbac6031b01c006dae2e56b5e836c2a00b08398552273c9396ce.

The "wrong" digests are the same on every run (just their order in the error differs). 13280b5914050853a87d662c3229d42b61544e36dd4515f06e188835f3407468 is the digest of the container I synced.

Actions
Copy link
 #1

Updated by Evgeni Golov about 4 years ago

phew, I never tested before my change, but that also fails with the same error, so it's not my change :)

Actions
Copy link
 #2

Updated by Evgeni Golov about 4 years ago

the last nightly that passed this test is 646e49f, and after that there are only two commits:

commit 7e55311073c7f26b9fbbaa31a60a42cd9adf1525 (HEAD -> master, origin/master, origin/HEAD)
Author: Justin Sherrill <jsherril@redhat.com>
Date:   Mon Nov 23 15:27:54 2020 -0500

    Fixes #31334 - fix export transient failure

commit ced5376fa9412ad0cb4fe3512ee69d41b18a5021
Author: Jonathon Turel <jturel@gmail.com>
Date:   Thu Nov 19 22:39:20 2020 +0000

    Refs #30832 - check for pulp2 presence rather than pulp3 yum support
Actions
Copy link
 #3

Updated by Jonathon Turel about 4 years ago

  • Target version set to Katello 4.0.0
  • Triaged changed from No to Yes
Actions
Copy link
 #4

Updated by Justin Sherrill almost 4 years ago

  • Status changed from New to Rejected

I filed the pulp bug around this here: https://pulp.plan.io/issues/7923

but i think we resolved the pipeline failure with some installer changes. I'm gonna reject this from now since the blockage was resolved and the seen behavior is fixed in pulp-container 2.3.0

Actions
Copy link

Also available in: Atom PDF