Project

General

Profile

Bug #26032

Unable to update certificates belonging to a repository

Added by Partha Aji 11 months ago. Updated 11 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

1) Create a couple of ContentCredential certificates
2) Create a yum repo.
3) Edit the repo in the UI and change any of the SSL certs/ SSL CA Cert/SSL Key entries
4) Get the backend identifier of this repo and run the following pulp-admin command

pulp-admin -u admin -p <....> repo list --detail --repo-id=<backend_identifier>

Expected:
SSL Client Cert/SSL Client Key/SSL Client CA populated

Actual:
None of the above entries are populated.


Related issues

Has duplicate Katello - Bug #26096: yum repository change not propagated to pulpDuplicate

Associated revisions

Revision d6f1515a (diff)
Added by Partha Aji 11 months ago

Fixes #26032- Repo certs propagated on save (#7975)

  • Fixes #26032 - Repo certs propagated on save

This commit updates pulp when SSL Certs/Keys are changed in a
repository.

  • Refs #26032 - Spacing fixes in js

History

#1 Updated by Partha Aji 11 months ago

  • Bugzilla link set to 1670276

#2 Updated by The Foreman Bot 11 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/7975 added

#3 Updated by Christine Fouant 11 months ago

  • Triaged changed from No to Yes
  • Target version set to Katello 3.11.1

#4 Updated by Anonymous 11 months ago

  • Status changed from Ready For Testing to Closed

#5 Updated by Chris Roberts 11 months ago

  • Has duplicate Bug #26096: yum repository change not propagated to pulp added

Also available in: Atom PDF