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 1458379 - Upgrade script for keepAliveTimeout parameter
Summary: Upgrade script for keepAliveTimeout parameter
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Endi Sukma Dewata
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-02 17:32 UTC by Matthew Harmsen
Modified: 2020-10-04 21:29 UTC (History)
3 users (show)

Fixed In Version: pki-core-10.4.1-8.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-08-01 22:52:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github dogtagpki pki issues 2807 0 None None None 2020-10-04 21:29:26 UTC
Red Hat Product Errata RHBA-2017:2110 0 normal SHIPPED_LIVE pki-core bug fix and enhancement update 2017-08-01 19:36:59 UTC

Description Matthew Harmsen 2017-06-02 17:32:09 UTC
This bug is created as a clone of upstream ticket:
https://pagure.io/dogtagpki/issue/2687

In PKI 10.4 the keepAliveTimeout parameter was added to server.xml to specify the session timeout for PKI Console. This parameter did not exist in PKI 10.3 so an upgrade script needs to be written to add the parameter into existing instances.

See also: http://pki.fedoraproject.org/wiki/Access_Banner

Comment 4 Amol K 2017-06-23 09:32:57 UTC
Hi Endi,

I did not get what exactly needs to be tested in this bug. Can you please provide information on this bug.

Comment 5 Endi Sukma Dewata 2017-06-23 14:55:11 UTC
Hi Amol,

Here are the steps:
1. Install PKI packages earlier than 10.4.1-8.el7.
2. Install CA. Make sure the server doesn't have keepAliveTimeout="300000" (see the wiki page in the bug description).
3. Upgrade to PKI 10.4.1-8.el7.

Expected result: The keepAliveTimeout="300000" should be added automatically into the server.xml.

The problem is I'm not sure if we have official 10.4.x packages prior to this. Is it possible to upgrade from 10.3.x (i.e. RHEL 7.3)?

Comment 6 Endi Sukma Dewata 2017-06-23 14:57:05 UTC
Correction: In step 2 I meant to say "Make sure the server.xml ..."

Comment 8 errata-xmlrpc 2017-08-01 22:52:53 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-2017:2110


Note You need to log in before you can comment on or make changes to this bug.