katello-nightly-rpm-pipeline 672 failed

Infra & CI
1

Katello nightly pipeline failed:

https://ci.theforeman.org/job/katello-nightly-rpm-pipeline/672/

foreman-pipeline-katello-nightly-centos7-install (failed)
foreman-pipeline-katello-nightly-centos7-upgrade (failed)

2

Looks like Pulp is not responding which results in HTTP 502 and 503 responses. Probably related to Pulp 3.6. @Justin_Sherrill are you aware of this?

3

it got past yesterday’s failure, looking at this one

4

Haven’t run through all tests yet, but this is the cause of the current
failure:

5

To provide an update, there are two failures still:

  1. uploads from hammer fail
    fixed here: https://github.com/Katello/katello/pull/8927
  2. container registry pull fails
    a slew of issues with this including:
    a) partially fixed by https://github.com/Katello/katello/pull/8927
    b) requires an installer update, as now the pulp registry is served by the api app, redirecting to the content app. Will work on that
    c) some unknown issue where this redirect isn’t working properly. This may be a bug in pulp, or a misconfiguration, i’ve been working with the pulp team to try to identify the issue.
6

[Justin_Sherrill] Justin_Sherrill
https://community.theforeman.org/u/justin_sherrill Katello
September 4

To provide an update, there are two failures still:

  1. uploads from hammer fail
    fixed here: https://github.com/Katello/katello/pull/8927
  2. container registry pull fails
    a slew of issues with this including:
    a) partially fixed by https://github.com/Katello/katello/pull/8927
    b) requires an installer update, as now the pulp registry is
    served by the api app, redirecting to the content app. Will work
    on that
    c) some unknown issue where this redirect isn’t working properly.
    This may be a bug in pulp, or a misconfiguration, i’ve been
    working with the pulp team to try to identify the issue.

I’m tracking this issue #2) here with
https://projects.theforeman.org/issues/30780

7

2 c) was identified as pulp_container bug, filed here: https://pulp.plan.io/issues/7462

the pulp team is prioritizing it and are hoping to have a fix’d build mid-next week.

8

I didn’t check if this solves it, but reading the issue description I think this might help:

If it doesn’t fix it, it’s good to at least make Django aware of where it’s running.

9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.