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.
+++ This bug was initially created as a clone of Bug #1940261 +++
Description of problem:
The 'getcert list' command displays the 'NotAfter' date of tracked certificates, but omits the 'NotBefore' date that indicates when the certificates became valid for use.
Including the NotBefore date in the command output will be beneficial for administrative and troubleshooting purposes.
How reproducible:
Always
Steps to Reproduce:
1. Root user runs the 'getcert list' command.
Actual results (example):
Request ID '20200930052944':
status: MONITORING
stuck: no
key pair storage: type=NSSDB,location='/etc/pki/pki-tomcat/alias',nickname='ocspSigningCert cert-pki-ca',token='NSS Certificate DB',pin set
certificate: type=NSSDB,location='/etc/pki/pki-tomcat/alias',nickname='ocspSigningCert cert-pki-ca',token='NSS Certificate DB'
CA: dogtag-ipa-ca-renew-agent
issuer: CN=Certificate Authority,O=IPA.CORP.EXAMPLE.COM
subject: CN=OCSP Subsystem,O=IPA.CORP.EXAMPLE.COM
expires: 2021-11-23 18:19:33 UTC
eku: id-kp-OCSPSigning
pre-save command: /usr/libexec/ipa/certmonger/stop_pkicad
post-save command: /usr/libexec/ipa/certmonger/renew_ca_cert "ocspSigningCert cert-pki-ca"
track: yes
auto-renew: yes
Proposed output (example):
Request ID '20200930052944':
status: MONITORING
stuck: no
key pair storage: type=NSSDB,location='/etc/pki/pki-tomcat/alias',nickname='ocspSigningCert cert-pki-ca',token='NSS Certificate DB',pin set
certificate: type=NSSDB,location='/etc/pki/pki-tomcat/alias',nickname='ocspSigningCert cert-pki-ca',token='NSS Certificate DB'
CA: dogtag-ipa-ca-renew-agent
issuer: CN=Certificate Authority,O=IPA.CORP.EXAMPLE.COM
subject: CN=OCSP Subsystem,O=IPA.CORP.EXAMPLE.COM
valid from: 2019-11-21 18:19:33 UTC
expires: 2021-11-23 18:19:33 UTC
eku: id-kp-OCSPSigning
pre-save command: /usr/libexec/ipa/certmonger/stop_pkicad
post-save command: /usr/libexec/ipa/certmonger/renew_ca_cert "ocspSigningCert cert-pki-ca"
track: yes
auto-renew: yes
Before cloning I missed that this change, 84d575da7516cae1ee94099317cf0f8fae2c7ea1, is already included in the 0.79.14 rebase, https://bugzilla.redhat.com/show_bug.cgi?id=1969537
Kaleem do you want to keep this BZ open for QE purposes?
(In reply to Rob Crittenden from comment #1)
> Before cloning I missed that this change,
> 84d575da7516cae1ee94099317cf0f8fae2c7ea1, is already included in the 0.79.14
> rebase, https://bugzilla.redhat.com/show_bug.cgi?id=1969537
>
> Kaleem do you want to keep this BZ open for QE purposes?
Rob,
Since change for this already verified in above bug, so we can close this bug with same reasoning.
I think verify in this case would just involve ensuring the automated test was successful. I don't think taking a previous release VERIFIED for the current one is generally acceptable. Or we can close this as INVALID as that verification is already going to take place automatically in gating.
Comment 4Florence Blanc-Renaud
2021-11-16 09:50:40 UTC
As agreed with Rizwan, closing this BZ as invalid since rhel 9.0 already contains the fix (RHEL 9.0 ships certmonger-0.79.14-5.el9 and the fix was included in the rebase to 0.79.14)