Project

Profile

Help

Issue #2506

closed

Pulp 2.9.2 has issues using new feed-cert when syncing to Redhat CDN repos

Added by bremnertech over 7 years ago. Updated about 5 years ago.

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

Description

Raising this issue under instruction:

Our Redhat subscriptions were renewed generating new subscription certificate pem files. It was perceived that we could run:

pulp-admin rpm repo update --feed-cert=/path/to/newcert --repo-id=rhelrepo

The update is accepted but when we run a sync of the repo to ensure pulp can still communicate with Redhat's CDN, we are unable to connect.

If we trash the old rhelrepo, and then recreate it with the new --feed-cert entry, the repo then syncs happily. We intend to upgrade our version of pulp shortly anyway but keen to know if this is in fact a known issue.

Actions #1

Updated by bmbouter over 7 years ago

  • Description updated (diff)

I don't believe this is a known issue. I would like some more information. Can you post the "repo details":

  • of the repo you want to update prior to update
  • of the repo you want to update post update (that isn't working)
  • of the new repo you create that is working

You can get this output to paste using a command like: pulp-admin repo list --repo-id rhelrepo --details

Actions #2

Updated by bremnertech over 7 years ago

I have discovered my error- the feed-key was missing and is required to acccompany an updated feed-cert.

Thanks for looking in to this .

Actions #3

Updated by bmbouter over 7 years ago

  • Status changed from NEW to CLOSED - WORKSFORME

That is great! It sounds like it's working, so I'm going to close as WORKSFORME.

Actions #4

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF