RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1733586 - Rebase pki-core from 10.5.16 to 10.5.17 (RHEL)
Summary: Rebase pki-core from 10.5.16 to 10.5.17 (RHEL)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Matthew Harmsen
QA Contact: PKI QE
URL:
Whiteboard:
Depends On:
Blocks: 1733588
TreeView+ depends on / blocked
 
Reported: 2019-07-26 16:19 UTC by Matthew Harmsen
Modified: 2020-03-31 19:54 UTC (History)
3 users (show)

Fixed In Version: pki-core-10.5.17-1.el7
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 19:54:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
rebase.diffs (14.00 KB, text/plain)
2019-08-14 00:07 UTC, Matthew Harmsen
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1078 0 None None None 2020-03-31 19:54:23 UTC

Description Matthew Harmsen 2019-07-26 16:19:25 UTC
DDogtag 10.5.x updates are designed to address critical bug fixes.  We should re-base pki-core in RHEL 7.8 to the latest 10.5.x release (exact number TBD) as a new tarball in order to include these bug fixes as well as consolidate all of the existing patches from the previous version.

Comment 2 Matthew Harmsen 2019-08-14 00:07:35 UTC
Created attachment 1603573 [details]
rebase.diffs

Comment 3 Matthew Harmsen 2019-08-14 00:08:32 UTC
Test Procedure:  Sanity Only

Comment 4 Matthew Harmsen 2019-08-14 00:18:06 UTC
DOGTAG_10_5_17_RHEL_BRANCH:

commit 5f00fcc9588ee626c222870e4da4dfeb11ec9d91
Author: Matthew Harmsen <mharmsen>
Date:   Tue Aug 13 18:12:39 2019 -0600

    Resolves: rhbz #1718418, 1733586, 1733588
    
    Re-base package versions from 10.5.16 ==> 10.5.17 (RHEL, RHCS)
    
    Update RHCS to "Red Hat Certificate System 9.6"

Comment 6 Geetika Kapoor 2019-11-12 06:41:29 UTC
Testing Scenario:

We have run QE CI and make sure pki-core build is picked correctly.(https://gitlab.cee.redhat.com/idm/pki-pytest-ansible/-/jobs/1007520/raw)

Package pki-ca.noarch 0:10.5.17-4.el7 will be installed

Comment 8 errata-xmlrpc 2020-03-31 19:54:16 UTC
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-2020:1078


Note You need to log in before you can comment on or make changes to this bug.