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.

Bug 1435122

Summary: IPA server installs fails with error message - No local ID range and no admins group found
Product: Red Hat Enterprise Linux 7 Reporter: Kaleem <ksiddiqu>
Component: 389-ds-baseAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 7.4CC: ksiddiqu, mbabinsk, mvarun, nkinder, pvoborni, rcritten, rmeggins, spoore, tbordaz, tscherf
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.6.1-9.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 21:16:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
console output with ds error log file none

Description Kaleem 2017-03-23 08:29:58 UTC
Created attachment 1265641 [details]
console output with ds error log file

Description of problem:
IPA server install with latest IPA build fails with following error message.

-----
ipa         : ERROR    default_range: No local ID range and no admins group found. Cannot create default ID range
ipa         : ERROR    Upgrade failed with no such entry
  [error] RuntimeError: no such entry
  [cleanup]: stopping directory server
  [cleanup]: restoring configuration
ipa.ipapython.install.cli.install_tool(CompatServerMasterInstall): ERROR    Update failed: no such entry
ipa.ipapython.install.cli.install_tool(CompatServerMasterInstall): ERROR    The ipa-server-install command failed. See /var/log/ipaserver-install.log for more information

Version-Release number of selected component (if applicable):
[root@dhcp207-182 ~]# rpm -q ipa-server 389-ds-base svrcore
ipa-server-4.5.0-2.el7.x86_64
389-ds-base-1.3.6.1-3.el7.x86_64
svrcore-4.1.3-2.el7.x86_64
[root@dhcp207-182 ~]# 

How reproducible:
Always

Steps to Reproduce:
1. Install IPA with latest IPA build

Actual results:
IPA install fails

Expected results:
IPA install should be successful


Additional info:
(1) selinux is in permissive mode
(2) Please find the attached ds error log file

Comment 9 Kaleem 2017-03-28 12:01:30 UTC
*** Bug 1436295 has been marked as a duplicate of this bug. ***

Comment 21 errata-xmlrpc 2017-08-01 21:16:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2086