See associated bug for details.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1544843 - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.6)
Per 10.5.x/10.6 Triage: 10.5.x
workaround exists
Metadata Update from @mharmsen: - Issue assigned to jmagne - Issue set to the milestone: 10.6 (was: 10.5)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
Metadata Update from @mharmsen: - Issue priority set to: critical (was: major)
Metadata Update from @mharmsen: - Issue priority set to: blocker (was: critical)
Metadata Update from @mharmsen: - Issue assigned to cfu (was: jmagne)
Metadata Update from @mharmsen: - Issue assigned to gkapoor (was: cfu)
Christina Fu 2018-06-05 20:36:59 EDT wrote:
Just to recap: This fix was suggested by Bob (rrelyea@redhat.com), and patch submitted by Geetika (gkapoor). I claim no credit and assume no blame ;-).
commit b0f9a67f4ee61c5ca1f020b0a6accefceb9bbe0b Author: gkapoor <gkapoor@redhat.com> Date: Tue May 29 19:52:15 2018 +0530 Fix for https://bugzilla.redhat.com/show_bug.cgi?id=1544843 Change-Id: Id8d45bfc804a9f26a1a475cb928cf184975a8f5f Signed-off-by: gkapoor <gkapoor@redhat.com>
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue set to the milestone: 10.5.9 (was: 10.5) - Issue status updated to: Closed (was: Open)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/3059
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Log in to comment on this ticket.