Bug 1262322
| Summary: | Failed to backup CS.cfg message in upgrade. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Martin Bašti <mbasti> |
| Component: | ipa | Assignee: | IPA Maintainers <ipa-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Namita Soman <nsoman> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | ksiddiqu, mkosek, rcritten, spoore, tlavigne |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ipa-4.2.0-10.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 12:06:34 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: | |||
|
Description
Martin Bašti
2015-09-11 12:19:44 UTC
Fixed upstream master: https://fedorahosted.org/freeipa/changeset/5762ad951fca025f17d00095bd7d89a14536ae85 ipa-4-2: https://fedorahosted.org/freeipa/changeset/c3d8a138aaad52af9c10ef8816b23cc81d79a680 How can I verify this? I see CS.cfg backed up during ipa-server-install on RHEL7.1 in the ipaserver-install.log. But, after upgrade, I don't see any mention of backing up the CS.cfg file in the ipaupgrade.log file. It does look from timestamps though as if it was backed up: [root@rhel7-9 ca]# ls -l /var/log/ipaupgrade.log -rw-------. 1 root root 5338433 Oct 2 13:22 /var/log/ipaupgrade.log [root@rhel7-9 ca]# ls -l /var/lib/pki/pki-tomcat/conf/ca/CS* -rw-rw----. 1 pkiuser pkiuser 82227 Oct 2 13:22 /var/lib/pki/pki-tomcat/conf/ca/CS.cfg lrwxrwxrwx. 1 pkiuser pkiuser 66 Oct 2 13:21 /var/lib/pki/pki-tomcat/conf/ca/CS.cfg.bak -> /var/lib/pki/pki-tomcat/conf/ca/archives/CS.cfg.bak.20151002132122 -rw-rw----. 1 root root 82223 Oct 2 13:20 /var/lib/pki/pki-tomcat/conf/ca/CS.cfg.ipabkp Unless that comes from a pki restart. How can I confirm this fix? Or is this what I'm looking for? [root@rhel7-9 log]# grep "Successfully backed up.*CS.cfg" /var/log/messages Oct 2 13:20:37 rhel7-9 pkidaemon: SUCCESS: Successfully backed up '/var/lib/pki/pki-tomcat/conf/ca/CS.cfg.bak' Oct 2 13:21:22 rhel7-9 pkidaemon: SUCCESS: Successfully backed up '/var/lib/pki/pki-tomcat/conf/ca/CS.cfg.bak' Or is it enough to make sure the error messages is not there? [root@rhel7-9 log]# grep "Dogtag must be stopped when creating backup of.*CS.cfg" /var/log/messages [root@rhel7-9 log]# grep "Dogtag must be stopped when creating backup of.*CS.cfg" /var/log/ipaupgrade.log [root@rhel7-9 log]# grep "Dogtag must be stopped when creating backup of.*CS.cfg" /tmp/yum.update.out [root@rhel7-9 log]# Thanks Verified. Version :: ipa-server-4.2.0-12.el7.x86_64 Results :: [root@rhel7-9 log]# grep "Dogtag must be stopped when creating backup of.*CS.cfg" /var/log/messages [root@rhel7-9 log]# grep "Dogtag must be stopped when creating backup of.*CS.cfg" /var/log/ipaupgrade.log [root@rhel7-9 log]# grep "Dogtag must be stopped when creating backup of.*CS.cfg" /tmp/yum.update.out [root@rhel7-9 log]# ls -l /var/log/ipaupgrade.log -rw-------. 1 root root 5338433 Oct 2 13:22 /var/log/ipaupgrade.log [root@rhel7-9 log]# ls -l /var/lib/pki/pki-tomcat/conf/ca/CS.cfg.ipabkp -rw-rw----. 1 root root 82223 Oct 2 13:20 /var/lib/pki/pki-tomcat/conf/ca/CS.cfg.ipabkp [root@rhel7-9 log]# Verification steps looks good for me 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 |