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 2063168 - [RFE] ipa user-undel <ipauser> doesnot restore the subid of the deleted user
Summary: [RFE] ipa user-undel <ipauser> doesnot restore the subid of the deleted user
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Florence Blanc-Renaud
QA Contact: ipa-qe
Depends On:
TreeView+ depends on / blocked
Reported: 2022-03-11 12:25 UTC by Sudhir Menon
Modified: 2023-09-11 07:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-09-11 07:28:41 UTC
Type: Story
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-7956 0 None None None 2022-03-11 12:32:09 UTC
Red Hat Issue Tracker RHELPLAN-115337 0 None None None 2022-03-11 12:32:15 UTC

Description Sudhir Menon 2022-03-11 12:25:19 UTC
Description of problem: ipa user-undel <ipauser> doesnot restore the subid of the deleted user.

Version-Release number of selected component (if applicable):

How reproducible: Always

Steps to Reproduce:
1. Install IPA and enable the below option. 
   #ipa config-mod --user-default-subid=true
2. Now create an ipauser and ensure that UniqueID gets generated for the user.
3. Now delete the ipauser using --preserve option and is listed under 'Preserved Users' tab.
4. Now restore the user again and run the 'ipa user-find and ipa subid-find' command respectively

Actual results:
ipa user-find displays the user, however ipa subid-find doesn't list the UniqueId set for the user.

[root@server ~]# ipa user-add test102
Added user "test102"
Subordinate ids: cd29793d-c5de-4846-a0c2-f5fb495b3627

[root@server ~]# ipa user-del --preserve
User login: test102
Deleted user "test102"

[root@server ~]# ipa subid-find
0 subordinate ids matched

[root@server ~]# ipa user-undel 
User login: test102
Undeleted user account "test102"

[root@server ~]# ipa subid-find
Number of entries returned 0

[root@server ~]# ipa user-find
  User login: test102
  First name: test102
  Last name: s
  Home directory: /home/test102
  Login shell: /bin/sh
  Principal name: test102
  Principal alias: test102
  Email address: test102
  UID: 794800007
  GID: 794800007
  Account disabled: False
Number of entries returned 3

Expected results:
When a user is preserved, the user restore should include all the attributes of the user when it was created.

Additional info:

Comment 4 RHEL Program Management 2023-09-11 07:28:41 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

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