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 2049587 - ipa-restore command is failing when restored after uninstalling the server
Summary: ipa-restore command is failing when restored after uninstalling the server
Keywords:
Status: CLOSED DUPLICATE of bug 2045223
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Florence Blanc-Renaud
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-02 12:07 UTC by Sudhir Menon
Modified: 2022-02-02 13:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-02 13:51:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-7782 0 None None None 2022-02-02 12:11:13 UTC
Red Hat Issue Tracker RHELPLAN-110707 0 None None None 2022-02-02 12:11:18 UTC

Description Sudhir Menon 2022-02-02 12:07:18 UTC 
Description of problem: ipa-restore command is failing when restore after uninstalling the server

Version-Release number of selected component (if applicable):
ipa-server-4.9.8-2.module+el8.6.0+13621+937b8cd9.x86_64

How reproducible:
Always

Steps to Reproduce:
1. ipa backup on replica
2. ipa-server-install', '--uninstall', '-U', '--ignore-topology-disconnect', '--ignore-last-of-role'
3. ipa-restore', '/var/lib/ipa/backup/ipa-full-date'

Actual results:
1. ipa-backup', '-v', '--disable-role-check'
Backup path for replica1.testrelm.test is /var/lib/ipa/backup/ipa-full-date

2. The ipa-server-install command was successful

3. ipactl start fails. 

CalledProcessError(Command ['/usr/sbin/ipactl', 'start'] returned non-zero exit status 1: 'Existing service file detected!\nAssuming stale, cleaning and proceeding\nFailed to start Directory Service: CalledProcessError(Command [\'/bin/systemctl\', \'start\', \'dirsrv\'] returned non-zero exit status 1: \'Job for dirsrv failed because the control process exited with error code.\\nSee "systemctl status dirsrv" and "journalctl -xe" for details.\\n\')\n')
The ipa-restore command failed. See /var/log/iparestore.log for more information

Expected results:
restore should work fine.

Additional info:
Comment 2 Florence Blanc-Renaud 2022-02-02 12:42:01 UTC 
This looks like a duplicate of Bug 2045223 - ipa-restore command is failing when restore after uninstalling the server
The fix will be delivered by 389-ds team, in 389-ds-1.4-8060020220128214755.ce3e8c9c.

Which version of 389-ds is installed in your test?
Comment 4 Florence Blanc-Renaud 2022-02-02 13:51:54 UTC 
The issue was reproduced with 389-ds-base-1.4.3.28-3.module+el8.6.0+13706+e2f14737.x86_64.

Bug 2045223 is fixed in 389-ds-1.4-8060020220128214755.ce3e8c9c, which is shipping 389-ds-base-1.4.3.28-5.module+el8.6.0+14049+0319e5ef => the fix is available in the most recent build. Closing this issue as a duplicate of Bug 2045223

*** This bug has been marked as a duplicate of bug 2045223 ***
Note You need to log in before you can comment on or make changes to this bug.