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 1750477 - Backport the patch removing key caching to unbreak libcacard for CI usage [rhel-8.1.0.z]
Summary: Backport the patch removing key caching to unbreak libcacard for CI usage [rh...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libcacard
Version: 8.1
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: 8.1
Assignee: Jakub Jelen
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On: 1746883
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-09 16:41 UTC by Oneata Mircea Teodor
Modified: 2020-11-14 08:17 UTC (History)
6 users (show)

Fixed In Version: libcacard-2.7.0-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1746883
Environment:
Last Closed: 2019-11-07 12:36:03 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:3785 0 None None None 2019-11-07 12:36:05 UTC

Comment 3 Jakub Jelen 2019-09-16 07:17:00 UTC 
I do not seem to be able to push to the rhel-8.1.0 branch with this z-stream bug referenced.

If I read the dist-git policy right, this bug needs blocker or exception? Or should I wait after the RHEL 8.1 release?

remote: *** Checking commit a831399ff1ce08e7c9dec074d47c71076ea66a80
remote: *** Related:
remote: ***   Unapproved:
remote: ***     rhbz#1750477 (qa_ack+, devel_ack+, pm_ack+, mirror+, release+, zstream+, zstream_target_release=8.1.0, Patch, Triaged, ZStream)
remote: *** No approved issue IDs referenced in log message or changelog for a831399ff1ce08e7c9dec074d47c71076ea66a80
remote: *** Unapproved issue IDs referenced in log message or changelog for a831399ff1ce08e7c9dec074d47c71076ea66a80
remote: *** Commit a831399ff1ce08e7c9dec074d47c71076ea66a80 denied
remote: *** Current checkin policy requires:
remote:     (((release == + and internal_target_release == 8.1.0) and (blocker == + or exception == +)) or (((jiraProject == RHELPLAN) and ((jiraField(release) == +) or (jiraField(BZ release) == +)) and (jiraField(fixVersions) == 8.1.0)) and (((jiraField(blocker) == +) or (jiraField(BZ blocker) == +)) or ((jiraField(exception) == +) or (jiraField(BZ exception) == +)))))
remote: *** See https://mojo.redhat.com/docs/DOC-1020853 for more information
Comment 10 errata-xmlrpc 2019-11-07 12:36:03 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:3785
Note You need to log in before you can comment on or make changes to this bug.