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.

Description of problem:

$ ipa domainlevel-get
-----------------------
Current domain level: 1
-----------------------

This is ok:
$ ipa domainlevel-set 0
ipa: ERROR: Domain Level cannot be lowered.

But this is not ok:
$ ipa domainlevel-set 1
ipa: ERROR: Domain Level cannot be raised to 1, server client.example.com does not support it.



Version-Release number of selected component (if applicable):
Current ipa-server from RHEL-7.5. Also tested with upstream.

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
IPA says the master does not support the desired domain level.

Expected results:
IPA should say that the domain level is already set to 1 and no modification needs to be performed.


Additional info:

Upstream ticket:
https://pagure.io/freeipa/issue/7511

Hi Thorsten,
when you reproduced the issue, which principal was authenticated?

I am able to to reproduce if I do
# kinit -kt /etc/krb5.keytab
# ipa domainlevel-set 1
ipa: ERROR: Domain Level cannot be raised to 1, server server.example.com does not support it.

But if I kinit as admin:
# kinit admin
Password for admin: 
# ipa domainlevel-set 1
ipa: ERROR: no modifications to be performed

I suspect the issue is linked to ipaMinDomainLevel and ipaMaxDomainLevel not readable by all the users.

Customer confirmed that he gets the expected output when the command is run with an admin TGT, hence closing as works for me.