#4826 ID range should be immutable
Closed: Fixed None Opened 9 years ago by pvoborni.

Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 1177706

Description of problem: On a fresh install of FreeIPA, if we do not set a ID
range during installation it will choose a randomly generated range. But after
the installation, if we want to change this under IPA Server --> ID Ranges -->
EXAMPLE.COM_id_range, the change is accepted but it appears that its not
getting honored.


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


How reproducible: On a fresh FC21 install.


Steps to Reproduce:
1. Install the freeipa-server using yum on a FC21.
2. Setup IPA using ipa-server-install command. Do not specify an ID range.
3. Login to the webUI and note the ID range
5. Change the ID Range.
5. Create a user or a group.

Actual results:
1. User or group gets an ID from range noted in step #3 above.

Expected results:
1. User or group should have an ID from range defined in step #4 above.

Additional info:
For adding 1 or 2 users by hand this is just a inconvenience as the ID can be
changed after adding the user to whatever we want. But if I'm automating and
adding 100s of users/groups it becomes a hassle.

I've also tried:

  • create new ID range
  • migrate all users and groups into the new ID range
  • delete old ID range
  • create new user

New user got UID from the old ID range.

this behavior is expected since there is no connection between ID ranges and DNA plugin yet, see #3609.

We may warn user after modification of local range about this behavior: http://www.redhat.com/archives/freeipa-devel/2015-January/msg00013.html

As agreed, for short term we should make local ranges immutable (and document why).

During processing of remaining tickets in 4.2 Backlog, this ticket was found as suitable to be fixed in the nearest bugfixing branch - which is 4.2.x.

Fixed by the following commits:

Metadata Update from @pvoborni:
- Issue assigned to mbabinsk
- Issue set to the milestone: FreeIPA 4.2.1

7 years ago

master:

  • 83ed8d2 WebUI Tests: fixing test_hbac
  • dae5bac WebUI Tests: fixing test_group
  • 3fa4378 WebUI Tests: fixing test_navigation
  • 7c3f9b7 WebUI Tests: refactoring login method to be more readable
  • 49a17e9 WebUI Tests: changing how the login screen is detected
  • 12da43c WebUI Tests: fixing test_range test case
  • a072fe9 WebUI Tests: Changing how the initial load process is done
  • 81fb7e5 WebUI Tests: fixing test_user.py::test_test_noprivate_posix
  • a5bd7bf WebUI Tests: changing the ActionsChains.move_to_element to a new approach

ipa-4-6:

  • a4e7a20 WebUI Tests: fixing test_hbac
  • c5e2dee WebUI Tests: fixing test_group
  • 19fb8b9 WebUI Tests: fixing test_navigation
  • 9490884 WebUI Tests: refactoring login method to be more readable
  • 6865e6e WebUI Tests: changing how the login screen is detected
  • 5fb9c4f WebUI Tests: fixing test_range test case
  • 8ce814d WebUI Tests: Changing how the initial load process is done
  • d8ffd80 WebUI Tests: fixing test_user.py::test_test_noprivate_posix
  • d1eb7bc WebUI Tests: changing the ActionsChains.move_to_element to a new approach

Login to comment on this ticket.

Metadata