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 1733884 - Unassign cert enrollment request does not work in agent page of the CA instance
Summary: Unassign cert enrollment request does not work in agent page of the CA instance
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pki-core-10.7-module
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: RHCS Maintainers
QA Contact: PKI QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-29 06:21 UTC by shalini
Modified: 2020-10-04 21:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-03 17:53:53 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure dogtagpki issue 3126 0 None None None 2020-03-10 21:08:06 UTC
Github dogtagpki pki issues 3243 0 None open Unassign cert enrollment request does not work in agent page 2021-01-31 15:42:23 UTC

Description shalini 2019-07-29 06:21:06 UTC 
Description of problem:
Unassign cert enrollment request does not work in agent page of the CA instance

Version-Release number of selected component (if applicable) Red Hat Enterprise Linux release 8.1 Beta (Ootpa)
:
[root@pki ~]# rpm -qa | grep pki
pki-server-10.7.1-2.module+el8.1.0+3386+52d02a00.noarch
pki-symkey-10.7.1-2.module+el8.1.0+3386+52d02a00.x86_64
pki-base-java-10.7.1-2.module+el8.1.0+3386+52d02a00.noarch
pki-servlet-engine-9.0.7-16.module+el8.1.0+3366+6dfb954c.noarch
pki-base-10.7.1-2.module+el8.1.0+3386+52d02a00.noarch
pki-servlet-4.0-api-9.0.7-16.module+el8.1.0+3366+6dfb954c.noarch
pki-ca-10.7.1-2.module+el8.1.0+3386+52d02a00.noarch
python3-pki-10.7.1-2.module+el8.1.0+3386+52d02a00.noarch
pki-tools-10.7.1-2.module+el8.1.0+3386+52d02a00.x86_64


How reproducible:
always

Steps to Reproduce:
1. Enrol for a cert through the EE page of the CA
2. In the Agent Page (caadmin), select the pending and select assign request and submit.
3. Go to List request and show pending enrolment requests. > It should show assigned to caadmin.
4. click on the cert request with assignee caadmin and select unassign request and submit.
5. Revisit List request > show pending enrolment requests .

Actual results:
List request page showing assignee as caadmin .

Expected results:
List request page should show unassigned instead of caadmin .
Comment 1 Endi Sukma Dewata 2020-03-03 17:53:53 UTC 
This issue will be addressed upstream:
https://pagure.io/dogtagpki/issue/3126
Note You need to log in before you can comment on or make changes to this bug.