Bug 1263337

Summary: IPA Restore failed with installed KRA
Product: Red Hat Enterprise Linux 7 Reporter: Petr Vobornik <pvoborni>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: ksiddiqu, mbasti, mkosek, rcritten, tlavigne
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.2.0-12.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 12:06:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
console output with verification steps none

Description Petr Vobornik 2015-09-15 14:56:11 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/5297

Steps to reproduce:
1. install IPA
1. install KRA
1. backup
1. uninstall IPA
1. restore


Journal output
{{{
systemd[1]: Starting PKI Tomcat Server pki-tomcat...
pkidaemon[31532]: WARNING:  Symbolic link '/var/lib/pki/pki-tomcat/kra/logs' does NOT exist!
pkidaemon[31532]: INFO:  Attempting to create '/var/lib/pki/pki-tomcat/kra/logs' -> '/var/log/pki/pki-tomcat/kra' . . .
pkidaemon[31532]: ERROR:  Failed making '/var/lib/pki/pki-tomcat/kra/logs' -> '/var/log/pki/pki-tomcat/kra' since target '/var/log/pki/pki-tomcat/kra' does NOT exist!
systemd[1]: pki-tomcatd: control process exited, code=exited status=1
systemd[1]: Failed to start PKI Tomcat Server pki-tomcat.
systemd[1]: Unit pki-tomcatd entered failed state.
systemd[1]: pki-tomcatd failed.
systemd[1]: Reached target PKI Tomcat Server.
}}}

Comment 4 Kaleem 2015-09-30 06:58:32 UTC
Created attachment 1078544 [details]
console output with verification steps

Verified.

Please find the attached verification logs.

Comment 5 errata-xmlrpc 2015-11-19 12:06:38 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://rhn.redhat.com/errata/RHBA-2015-2362.html