-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Katello: Pulp-To-Pulp sync ends in 403 error #1555
Labels
Comments
gerrod3
added a commit
to gerrod3/pulp_ansible
that referenced
this issue
Aug 23, 2023
gerrod3
added a commit
to gerrod3/pulp_ansible
that referenced
this issue
Aug 23, 2023
gerrod3
added a commit
to gerrod3/pulp_ansible
that referenced
this issue
Aug 23, 2023
gerrod3
added a commit
to gerrod3/pulp_ansible
that referenced
this issue
Aug 23, 2023
gerrod3
added a commit
to gerrod3/pulp_ansible
that referenced
this issue
Aug 28, 2023
gerrod3
added a commit
that referenced
this issue
Sep 8, 2023
gerrod3
added a commit
to gerrod3/pulp_ansible
that referenced
this issue
Sep 21, 2023
gerrod3
added a commit
to gerrod3/pulp_ansible
that referenced
this issue
Sep 21, 2023
gerrod3
added a commit
that referenced
this issue
Sep 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Katello versions:
Smart proxy 1 versions:
Smart proxy 2 versions:
Describe the bug
On both smart proxy one and smart proxy 2 (versions above) in Katello, we hit the following error when syncing ansible repositories from one Pulp to another:
To Reproduce
Sync any ansible repo from Katello to a smart proxy (using Foreman).
Remote on the smart proxy 2 for example:
Expected behavior
Sync succeeds
Additional context
We just upgraded from Pulpcore 3.22 / pulp_ansible 0.16 to 3.28 and 0.18... were there any new features that would make the "upstream" Pulp ansible content inaccessible even with certificates set up on the remote?
The text was updated successfully, but these errors were encountered: