Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1624003

Summary: debug.level for pki instance not functioning as expected
Product: Red Hat Enterprise Linux 8 Reporter: Pritam Singh <prisingh>
Component: pki-coreAssignee: RHCS Maintainers <rhcs-maint>
Status: CLOSED WONTFIX QA Contact: Asha Akkiangady <aakkiang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.3CC: ascheel, edewata, mharmsen
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-08 07:35:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pritam Singh 2018-08-30 16:01:27 UTC
Description of problem:

debug.level for pki instance not functioning as expected as after changing to different debug level.

Earlier it was debug.level=0, after changing it to debug.level=10 still not getting the least detailed debug log as expected.

Version-Release number of selected component (if applicable):

PKI Command-Line Interface 10.5.9-5.el7

How reproducible:

always

Steps to Reproduce:

1. Edit the configuration file /var/lib/pki/pki-tomcat/conf/ca/CS.cfg
2. find and set debug.level=10 
3. Save it and restart the instance
4. Issue the certificate so it will generate the log.

Actual results:

Debug log not generating user friendly log as expected.

Expected results:

Debug log should generate user friendly log

Additional info:

Please find the pastebin link for debug log:
http://pastebin.test.redhat.com/639507

Comment 2 Endi Sukma Dewata 2020-02-08 00:36:50 UTC
Hi Pritam,

The bug was originally opened for RHEL 7, but it was deferred to RHEL 8.3.
The pastebin is already gone so I cannot see the output. I do not see a
problem on RHEL 8.2, but could you check if it's working on both RHEL 7
and RHEL 8? Thanks.

Here's the doc for RHEL 8:
https://www.dogtagpki.org/wiki/PKI_10.7_Server_Debug_Log

and here's the doc for RHEL 7:
https://www.dogtagpki.org/wiki/PKI_10.5_Server_Debug_Log

Comment 4 Pritam Singh 2020-06-04 12:55:30 UTC
Tested on:

RHEL 79:
pki-core-10.5.18-7.el7.src.rpm
RHEL 82:
pki-core-10.8.3-2.module+el8.2.0+6294+b7db4606.src.rpm

There is no issue with RHEL82 and unable to reproduce on it.

on RHEL 79 -

By default, it's debug.level=0 and I changed it to 6 and restarted the server but it's not generating the debug logs even after requesting and approving the cert.

POC:

1. Changed the debug.level=6 and restarted the CA server

CA Debug log:

[04/Jun/2020:08:16:24][localhost-startStop-1]: ============================================
[04/Jun/2020:08:16:24][localhost-startStop-1]: =====  DEBUG SUBSYSTEM INITIALIZED   =======
[04/Jun/2020:08:16:24][localhost-startStop-1]: ============================================

2. Request Certificate:

[root@pki1 ~]# pki -d /root/nssdb/ -c SECret.123 -p 20080 client-cert-request 'uid=test6'
-----------------------------
Submitted certificate request
-----------------------------
  Request ID: 74
  Type: enrollment
  Request Status: pending
  Operation Result: success

CA Debug log:

[04/Jun/2020:08:16:24][localhost-startStop-1]: ============================================
[04/Jun/2020:08:16:24][localhost-startStop-1]: =====  DEBUG SUBSYSTEM INITIALIZED   =======
[04/Jun/2020:08:16:24][localhost-startStop-1]: ============================================



3. Approve request:

[root@pki1 ~]# pki -d /root/nssdb/ -c SECret.123 -p 20080 -n 'PKI CA Administrator for Example.Org' ca-cert-request-review --action approve 74
-------------------------------
Approved certificate request 74
-------------------------------
  Request ID: 74
  Type: enrollment
  Request Status: complete
  Operation Result: success
  Certificate ID: 0x33


CA Debug log:

[04/Jun/2020:08:16:24][localhost-startStop-1]: ============================================
[04/Jun/2020:08:16:24][localhost-startStop-1]: =====  DEBUG SUBSYSTEM INITIALIZED   =======
[04/Jun/2020:08:16:24][localhost-startStop-1]: ============================================


Actual Result:
It's not generating the logs for performed operations.

Expected Result:

As per the https://www.dogtagpki.org/wiki/PKI_10.5_Server_Debug_Log#Log_Files it should be supposed to generate some VERBOSE logs indicating the performed operations.

Comment 8 RHEL Program Management 2021-01-08 07:35:00 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.