Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionAbhijeet Kasurde
2017-04-18 06:45:56 UTC
Description of problem:
ipa restore fails to restore IPA user after restoring backup which contains specified IPA User.
Version-Release number of selected component (if applicable):
# rpm -qa ipa-server selinux-policy 389-ds-base pki-server
selinux-policy-3.13.1-142.el7.100.noarch
ipa-server-4.5.0-6.el7.x86_64
pki-server-10.4.1-1.el7.noarch
389-ds-base-1.3.6.1-7.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Install IPA server on fresh installation
2. Create a IPA user
3. Take a full backup of IPA server
4. Uninstall IPA server
5. Restore backup using ipa-restore
6. Check if user exists
Actual results:
IPA User not found
Expected results:
IPA user should be available
Is the test correct?
The user is added with:
[root@ipaserver01 ~]# echo Password | ipa user-add --first testuser1 --last testuser1 testuser1 --password
but checked with:
[root@ipaserver01 ~]# ipa user-find f
which is completely different user
(In reply to Petr Vobornik from comment #4)
> Is the test correct?
>
> The user is added with:
>
> [root@ipaserver01 ~]# echo Password | ipa user-add --first testuser1 --last
> testuser1 testuser1 --password
>
> but checked with:
>
> [root@ipaserver01 ~]# ipa user-find f
>
> which is completely different user
My bad. I meant to say
[root@ipaserver01 ~]# ipa user-find testuser1
Tried, backup and restore. It works for me, but I encountered other issue after backup which looks like bug 1436642 - user find ended with "RuntimeError: maximum recursion depth exceeded in cmp".
After
# systemctl restart gssproxy
# systemctl restart httpd.service
# kdestroy -A
# kinit admin
User find returned expected output (test user was there).
# rpm -q ipa-server gssproxy mod_auth_gssapi
ipa-server-4.5.0-7.el7.x86_64
gssproxy-0.7.0-3.el7.x86_64
mod_auth_gssapi-1.5.1-2.el7.x86_64
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-2017:2304