#6902 ipa restore fails to restore IPA user
Closed: fixed 6 years ago Opened 6 years ago by pvoborni.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1442932

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

Metadata Update from @pvoborni:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1442932

6 years ago

Metadata Update from @pvoborni:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1442932

6 years ago

When I was testing this use case, find the user worked for me but I encountered other issue after backup which looks like #6775- user find ended with "RuntimeError: maximum recursion depth exceeded in cmp".

But 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

Metadata Update from @pvoborni:
- Issue priority set to: blocker
- Issue set to the milestone: FreeIPA 4.5.1
- Issue tagged with: regression

6 years ago

Metadata Update from @pvoborni:
- Issue assigned to pvoborni

6 years ago

Metadata Update from @pvoborni:
- Custom field on_review adjusted to https://github.com/freeipa/freeipa/pull/738

6 years ago

master:

  • 3a4c8e3 restore: restart/reload gssproxy after restore

ipa-4-5:

  • 04ed1fa restore: restart/reload gssproxy after restore

Metadata Update from @tkrizek:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata