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 921186 - [RFE] Reclaim DNA ranges when uninstalling replicas
Summary: [RFE] Reclaim DNA ranges when uninstalling replicas
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: IDM QE LIST
URL:
Whiteboard:
: 864735 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-13 16:26 UTC by Namita Soman
Modified: 2018-11-30 21:15 UTC (History)
5 users (show)

Fixed In Version: ipa-3.2.1-1.el7
Doc Type: Enhancement
Doc Text:
Feature: Allow reclaiming UID/GID ranges that belong to deleted replicas. Reason: When a replica is installed a UID/GID range is automatically allocated and provisioned to the replica. If many replicas are recycled the ID space can be exhausted. Result (if any): When a replica is deleted, the remaining ID range is transferred to a suitable replica, if there is one. Additionally, ID ranges can be managed manually with ipa-replica-manage.
Clone Of:
Environment:
Last Closed: 2014-06-13 13:29:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Namita Soman 2013-03-13 16:26:08 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/3321

When uninstalling replicas currently unused ID ranges are simply lost.
On a 2 replica server setup uninstalling an reinstalling a replica may loose as much as half of the total original range.

We need to add means to reclaim unused ranges by adding them back to one of the masters when a replica is uninstalled or forcibly deleted.
Comment 1 Rob Crittenden 2013-03-13 16:54:23 UTC 
Fixed upstream

master: 9005b9bc8aac7c1381aadb7d17107ebbebae005d

See http://freeipa.org/page/V3/Recover_DNA_Ranges for the design details.
Comment 4 Martin Kosek 2013-10-01 08:09:02 UTC 
*** Bug 864735 has been marked as a duplicate of this bug. ***
Comment 5 Scott Poore 2014-02-03 22:34:48 UTC 
Verified.

Version ::

ipa-server-3.3.3-15.el7.x86_64

Results ::

ON MASTER:

[root@rhel7-1 ~]# ipa-replica-manage dnarange-show
master.ipa1.example.test: 445600000-445799999
replica1.ipa1.example.test: No range set

[root@rhel7-1 ~]# ipa-replica-manage dnanextrange-show
master.ipa1.example.test: No on-deck range set
replica1.ipa1.example.test: No on-deck range set

ON REPLICA:

[root@rhel7-2 ~]# kinit admin
Password for admin.TEST: 

[root@rhel7-2 ~]# ipa user-add --first=f --last=l testuser1
----------------------
Added user "testuser1"
----------------------
  User login: testuser1
  First name: f
  Last name: l
  Full name: f l
  Display name: f l
  Initials: fl
  Home directory: /home/testuser1
  GECOS: f l
  Login shell: /bin/sh
  Kerberos principal: testuser1.TEST
  Email address: testuser1.test
  UID: 445700000
  GID: 445700000
  Password: False
  Member of groups: ipausers
  Kerberos keys available: False

ON MASTER:

[root@rhel7-1 ~]# ipa-replica-manage dnarange-show
master.ipa1.example.test: 445600000-445699999
replica1.ipa1.example.test: 445700001-445799999

[root@rhel7-1 ~]# ipa-replica-manage dnanextrange-show
master.ipa1.example.test: No on-deck range set
replica1.ipa1.example.test: No on-deck range set

[root@rhel7-1 ~]# ipa-replica-manage del replica1.ipa1.example.test --force
Deleting replication agreements between replica1.ipa1.example.test and master.ipa1.example.test
ipa: INFO: Setting agreement cn=meTomaster.ipa1.example.test,cn=replica,cn=dc\=ipa1\,dc\=example\,dc\=test,cn=mapping tree,cn=config schedule to 2358-2359 0 to force synch
ipa: INFO: Deleting schedule 2358-2359 0 from agreement cn=meTomaster.ipa1.example.test,cn=replica,cn=dc\=ipa1\,dc\=example\,dc\=test,cn=mapping tree,cn=config
ipa: INFO: Replication Update in progress: TRUE: status: 0 Replica acquired successfully: Incremental update started: start: 0: end: 0
ipa: INFO: Replication Update in progress: FALSE: status: 0 Replica acquired successfully: Incremental update succeeded: start: 0: end: 0
Deleted replication agreement from 'master.ipa1.example.test' to 'replica1.ipa1.example.test'
Background task created to clean replication data. This may take a while.
This may be safely interrupted with Ctrl+C

[root@rhel7-1 ~]# ipa-replica-manage dnarange-show
master.ipa1.example.test: 445600000-445699999

[root@rhel7-1 ~]# ipa-replica-manage dnanextrange-show
master.ipa1.example.test: 445700001-445799999
Comment 6 Ludek Smid 2014-06-13 13:29:07 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.