Project

General

Profile

Actions

Bug #31362

closed

podman pull 404 error only on Katello 3.17

Added by Ian Ballou over 3 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Container
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

For some reason, podman pull fails with the following error only on Katello 3.17.0:

error parsing HTTP 404 response body: invalid character ':' after top-level value: "404: Not Found" 

The error still occurs even after I upgraded the pulp-container plugin to the latest we offer in the Pulpcore 3.7 repo. The error is not existent in 3.18.

Related user thread: https://community.theforeman.org/t/foreman-2-2-and-katello-3-16-docker-pull/20917

I've found this to be consistently reproducible on our 3.17 vagrant box.

Actions #1

Updated by Evgeni Golov over 3 years ago

I've seen this on nightly yesterday, while playing with https://github.com/theforeman/forklift/pull/1224, but couldn't repro today.

Could it be an issue fetching things from the upstream repo and pulpcore not properly catching that?

And by nightly I mean tfm-rubygem-katello-4.0.0-0.1.pre.master.20201106070834git2d977a4.el7.noarch.rpm -- as we hadn't green nightlies in a while.

Actions #2

Updated by Chris Roberts over 3 years ago

  • Target version changed from Katello 3.17.1 to Katello 3.17.2
Actions #3

Updated by Jonathon Turel over 3 years ago

  • Triaged changed from No to Yes
Actions #4

Updated by Chris Roberts about 3 years ago

  • Target version changed from Katello 3.17.2 to Katello 3.17.3
Actions #5

Updated by Jonathon Turel about 3 years ago

  • Status changed from New to Rejected
  • Target version deleted (Katello 3.17.3)

Closing since not reproducible on 3.18+ and there's a workaround in the discourse thread

Actions

Also available in: Atom PDF