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 1715950 - Renaming stream branches in PKI 10.6 modules for RHEL 8.1
Summary: Renaming stream branches in PKI 10.6 modules for RHEL 8.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pki-core
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.1
Assignee: RHCS Maintainers
QA Contact: PKI QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-31 17:55 UTC by Endi Sukma Dewata
Modified: 2020-11-14 13:17 UTC (History)
3 users (show)

Fixed In Version: pki-core-10.6-8010020190604003827.1c24d066
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 21:06:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3416 0 None None None 2019-11-05 21:08:39 UTC

Description Endi Sukma Dewata 2019-05-31 17:55:44 UTC
Currently many components in pki-core:10.6 and pki-deps:10.6 for RHEL 8.1 are
still pointing to stream-pki-10.6 branch:

http://pkgs.devel.redhat.com/cgit/modules/pki-deps/tree/pki-deps.yaml?h=10.6-rhel-8.1.0&id=c15a1f118abe34459f888809cbfa1b0fd464097c
http://pkgs.devel.redhat.com/cgit/modules/pki-core/tree/pki-core.yaml?h=10.6-rhel-8.1.0&id=9c0613aa4f24acca7579a33acbf82a956e6644a7

They should be changed to stream-pki-10.6-rhel-8.1.0.

Comment 1 Endi Sukma Dewata 2019-06-01 01:59:42 UTC
The pki-deps:10.6 build is available at: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=905789
I was able to install CA and KRA successfully.

Comment 2 Endi Sukma Dewata 2019-06-05 20:15:18 UTC
The pki-core:10.6 build is available at: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=906274

Comment 4 Amol K 2019-07-11 15:03:43 UTC
I have performed basic sanity with this bug.

I installed RHEL 8.1. 
I could see that there are 10.6 stream pki-core and pki-deps modules.

```
pki-core                              10.6 [e]                                                                                 PKI Core module for PKI 10.6 or later                                               
pki-deps                              10.6 [e]                                                                                 PKI Dependencies module for PKI 10.6 or later 
```

- Installed modules.
- Installed packages.
- Able to setup CA and KRA.


Marking this bz as verified.

Comment 6 errata-xmlrpc 2019-11-05 21:06:55 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-2019:3416


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