1645429 – pkispawn fails due to name collision with /var/log/pki/<instance> [rhel-7.6.z]

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 1645429 - pkispawn fails due to name collision with /var/log/pki/<instance> [rhel-7.6.z]

Summary: pkispawn fails due to name collision with /var/log/pki/<instance> [rhel-7.6.z]

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	pki-core
Sub Component:
Version:	7.7
Hardware:	All
OS:	Linux
Priority:	high
Severity:	high
Target Milestone:	rc
Target Release:	---
Assignee:	Dinesh Prasanth
QA Contact:	Asha Akkiangady
Docs Contact:	Marc Muehlfeld
URL:
Whiteboard:
Depends On:	1644769
Blocks:
TreeView+	depends on / blocked

Reported:	2018-11-02 08:35 UTC by Oneata Mircea Teodor
Modified:	2019-01-29 17:22 UTC (History)
CC List:	5 users (show)
Fixed In Version:	pki-core-10.5.9-8.el7_6
Doc Type:	Enhancement
Doc Text:	Previously, the pkispawn utility reported a name collision error when installing a Certificate System subsystem on a server with an existing Certificate System log directory structure. With this enhancement, Certificate System reuses the existing log directory structure to preserve logs of previous installations.
Clone Of:	1644769
Environment:
Last Closed:	2019-01-29 17:21:57 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2019:0168	0	None	None	None	2019-01-29 17:22:00 UTC

Description Oneata Mircea Teodor 2018-11-02 08:35:02 UTC

This bug has been copied from bug #1644769 and has been proposed to be backported to 7.6 z-stream (EUS).

Comment 2 Matthew Harmsen 2018-11-02 15:15:14 UTC

Test Procedure

* https://bugzilla.redhat.com/show_bug.cgi?id=1644769#c3

Comment 3 Matthew Harmsen 2018-11-30 00:31:43 UTC

commit 24405fac463e59250ccf42507bba7fb811e3a2fb
Author: Dinesh Prasanth M K <dmoluguw>
Date:   Thu Nov 1 17:02:03 2018 -0400

    Reuse same instance log dirs (if exists)
    
    Resolves: Bug 1644769
    Ticket: https://pagure.io/dogtagpki/issue/3077
    
    - `pkidestroy` behaviour was chagned to preserve the logs by default.
      When `pkispawn` is run, it throws a name space collision error.
    - This patch reuses the log dir and appends logs to the same log dir
      structure (if exists) and logs it accordingly.
    
    `Signed-off-by: Dinesh Prasanth M K <dmoluguw>`
    
    (cherry picked from commit c6c6757b4c566d10d25fe220fa9f59539c7a55ee)

Comment 4 Matthew Harmsen 2018-11-30 00:33:14 UTC

(In reply to Matthew Harmsen from comment #3)
> commit 24405fac463e59250ccf42507bba7fb811e3a2fb
> Author: Dinesh Prasanth M K <dmoluguw>
> Date:   Thu Nov 1 17:02:03 2018 -0400
> 
>     Reuse same instance log dirs (if exists)
>     
>     Resolves: Bug 1644769
>     Ticket: https://pagure.io/dogtagpki/issue/3077
>     
>     - `pkidestroy` behaviour was chagned to preserve the logs by default.
>       When `pkispawn` is run, it throws a name space collision error.
>     - This patch reuses the log dir and appends logs to the same log dir
>       structure (if exists) and logs it accordingly.
>     
>     `Signed-off-by: Dinesh Prasanth M K <dmoluguw>`
>     
>     (cherry picked from commit c6c6757b4c566d10d25fe220fa9f59539c7a55ee)

Cherry-picked to DOGTAG_10_5_9_RHEL_BRANCH

Comment 6 Deepak Punia 2018-12-14 11:39:10 UTC

#module list
OS - RHEL7.6Zupdate2
pki version 10.5.9-7.el7_6

1> pkispawn -s CA -f ca.inf -vv
2> ls /var/log/pki/
	drwxrwx---. 3 pkiuser pkiuser  187 Dec 14 06:18 rhcs93-TMS-CA
	-rw-rw----. 1 pkiuser pkiuser 175K Dec 14 06:18 pki-ca-spawn.20181214061802.log
3> pkidestroy -s CA -i rhcs93-TMS-CA
4> [root@cloud-qe-05 ~]# ls -rlth /var/log/pki/
	-rw-rw----. 1 pkiuser pkiuser 175K Dec 14 06:18 pki-ca-spawn.20181214061802.log
	-rw-rw----. 1 pkiuser pkiuser  31K Dec 14 06:30 pki-ca-destroy.20181214063012.log
	[root@cloud-qe-05 ~]# 
5> pkispawn -s CA -f ca.inf -vv 
		Successfully installed without any error.
6> [root@cloud-qe-05 ~]# ls -rlth /var/log/pki/
-rw-rw----. 1 pkiuser pkiuser 175K Dec 14 06:18 pki-ca-spawn.20181214061802.log
-rw-rw----. 1 pkiuser pkiuser  31K Dec 14 06:30 pki-ca-destroy.20181214063012.log
drwxrwx---. 3 pkiuser pkiuser  187 Dec 14 06:32 rhcs93-TMS-CA
-rw-rw----. 1 pkiuser pkiuser 175K Dec 14 06:32 pki-ca-spawn.20181214063200.log
-rw-rw-r--. 1 root    root     32K Dec 14 06:33 pki-ca-spawn.20181214063342.log

Comment 10 errata-xmlrpc 2019-01-29 17:21:57 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-2019:0168

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