Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1175287 - No error message thrown on restore(full kind) on replica from full backup taken on master
No error message thrown on restore(full kind) on replica from full backup tak...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa (Show other bugs)
7.1
Unspecified Unspecified
medium Severity unspecified
: rc
: ---
Assigned To: IPA Maintainers
Namita Soman
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-12-17 08:01 EST by Kaleem
Modified: 2015-03-05 05:19 EST (History)
2 users (show)

See Also:
Fixed In Version: ipa-4.1.0-14.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-05 05:19:02 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
contains snip for restore.log and named service log (3.14 KB, text/plain)
2014-12-17 08:01 EST, Kaleem
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0442 normal SHIPPED_LIVE Moderate: ipa security, bug fix, and enhancement update 2015-03-05 09:50:39 EST

  None (edit)
Description Kaleem 2014-12-17 08:01:18 EST
Created attachment 970089 [details]
contains snip for restore.log and named service log

Description of problem:
I tried to run ipa-restore (full kind) on replica from full backup taken on master and was expecting an error message that restore can not proceed and only data restore possible.

Following shown on console :

"Host name dhcp207-133.testrelm.test does not match backup name dhcp207-214.testrelm.test"

And as expected restore failed.

[root@dhcp207-133 ~]# ipa-restore -p xxxxxxxx /var/lib/ipa/backup/ipa-full-2014-12-16-16-16-53/ -U
Preparing restore from /var/lib/ipa/backup/ipa-full-2014-12-16-16-16-53/ on dhcp207-133.testrelm.test
Host name dhcp207-133.testrelm.test does not match backup name dhcp207-214.testrelm.test
Each master will individually need to be re-initialized or
re-created from this one. The replication agreements on
masters running IPA 3.1 or earlier will need to be manually
re-enabled. See the man page for details.
Disabling all replication.
Disabling replication agreement on dhcp207-214.testrelm.test to dhcp207-133.testrelm.test
Stopping IPA services
Systemwide CA database updated.
Restoring files
Systemwide CA database updated.
Restoring from userRoot in TESTRELM-TEST
Starting IPA services
Command ''ipactl' 'start'' returned non-zero exit status 1
[root@dhcp207-133 ~]# echo $?
1
[root@dhcp207-133 ~]# 

Version-Release number of selected component (if applicable):
ipa-server-4.1.0-12.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Take full backup on master and copy it on replica
2. Run ipa-restore (full kind) from full backup copied from master


Actual results:
Restore fails as expected. 

Expected results:
Restore process should not proceed throwing an error message that cannot restore from full backup taken on another master.

Additional info:
(1)Please find the attached file for snip from iparestore.log
Comment 2 Martin Kosek 2015-01-05 11:13:12 EST
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4823
Comment 5 Kaleem 2015-01-16 04:15:42 EST
Verified.
IPA restore does not proceeds further now if hostname does not matches backup name,
IPA Version:
============
[root@dhcp207-133 ~]# rpm -q ipa-server
ipa-server-4.1.0-15.el7.x86_64
[root@dhcp207-133 ~]# 


[root@dhcp207-133 ~]# ipa-restore -p xxxxxxxx /var/lib/ipa/backup/ipa-full-2015-01-16-14-36-18/ -U 
Preparing restore from /var/lib/ipa/backup/ipa-full-2015-01-16-14-36-18/ on dhcp207-133.testrelm.test
Performing FULL restore from FULL backup
Host name dhcp207-133.testrelm.test does not match backup name master.testrelm.test
[root@dhcp207-133 ~]#
Comment 7 errata-xmlrpc 2015-03-05 05:19:02 EST
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/RHSA-2015-0442.html

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