Bug 1311678
Summary: | Repository refresh is updating certs on main pulp server | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | John Mitsch <jomitsch> |
Component: | Content Management | Assignee: | John Mitsch <jomitsch> |
Status: | CLOSED ERRATA | QA Contact: | Jitendra Yejare <jyejare> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | Nightly | CC: | bbuckingham, bkearney, cwelton, jomitsch, jyejare, sthirugn |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://projects.theforeman.org/issues/13863 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-27 09:23:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Mitsch
2016-02-24 17:34:32 UTC
Created from redmine issue http://projects.theforeman.org/issues/13863 When a repository is updated on the main katello server, certs are unnecessarily created in the importer on the pulp server Moving to POST since upstream bug http://projects.theforeman.org/issues/13863 has been closed ------------- John Mitsch Applied in changeset commit:katello|8ff40206a214d2fad9698465af4d94972822a120. Hi, please, provide verfication steps thanks Thanks and Regards, Tazim Tazim, Steps to verify are: 1) Create yum repositories 2) Sync yum repositories without error -John As per steps mentioned in comment 7, Verified on Sat 6.2 snap 9.2 The issue/error is nor reproducible. I set(custom) and synced rhel67 server repo without any errors in fg abd bg. Moving this to Verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501 |