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 893187

Summary:	Installing IPA with a single realm component sometimes fails
Product:	Red Hat Enterprise Linux 6	Reporter:	Rob Crittenden <rcritten>
Component:	ipa	Assignee:	Rob Crittenden <rcritten>
Status:	CLOSED ERRATA	QA Contact:	Namita Soman <nsoman>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.4	CC:	jgalipea, mkosek, mvarun, tlavigne
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ipa-3.0.0-21.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 09:31:53 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:
Bug Depends On:
Bug Blocks:	895654

Description Rob Crittenden 2013-01-08 20:40:10 UTC

Description of problem:

Installing IPA  with a single component for the realm sometimes fails.

It fails because dc=<component> has updates applied before cn=schema so there are objectclass violations.

The one realm I've confirmed it fails with is TESTRELM. I've tried others, alphabetically before and after and it installs fine, so I'm not sure what is different about this.

Normally update entries are sorted by DN such that parents are applied before children (we sort by length). And cn=schema should be a special case so it is always applied first.

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

ipa-server-3.0.0-20.el6.x86_64

Steps to Reproduce:
1. ipa-server-install --realm=TESTRELM

Actual results:

Seen in ipa-server-install output near end:

Applying LDAP updates
ipa.ipaserver.install.ldapupdate.LDAPUpdate: ERROR    Update failed: Object class violation: unknown object class "nisDomainObject"

Comment 2 Martin Kosek 2013-01-11 08:51:01 UTC

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/3342

Comment 3 Rob Crittenden 2013-01-11 16:33:04 UTC

Fixed upstream.

master: 1d2d1e1af1660d022adca447f900403d171cba00

ipa-3-1: 41b2febff00999dc6b477f18e2ad89cd49e39532

ipa-3-0: ad2a2002457ec74a9372f4de1b6fcee37494daef

Changed the DN sort routine to always sort cn=schema first.

Comment 7 Varun Mylaraiah 2013-01-29 16:09:34 UTC

verified using ipa-server-3.0.0-24.el6.x86_64

[root@mvarun yum.repos.d]# hostname
mvarun64.testrelm.com

[root@mvarun yum.repos.d]# ipa-server-install --realm=TESTRELM

Server host name [mvarun64.testrelm.com]: 

The domain name has been determined based on the host name.
.
.
.
Please confirm the domain name [testrelm.com]: 
.
.
.
Directory Manager password: 
Password (confirm): 
.
.
IPA admin password: 
Password (confirm): 

The IPA Master Server will be configured with:
Hostname:      mvarun64.testrelm.com
IP address:    10.70.1.181
Domain name:   testrelm.com
Realm name:    TESTRELM

Continue to configure the system with these values? [no]: yes

The following operations may take some minutes to complete.
Please wait until the prompt is returned.

Configuring NTP daemon (ntpd)
  [1/4]: stopping ntpd
  .
  .
Done configuring NTP daemon (ntpd).
Configuring directory server for the CA (pkids): Estimated time 30 minutes 30 seconds
  [1/3]: creating directory server user
  [2/3]: creating directory server instance
  [3/3]: restarting directory server
Done configuring directory server for the CA (pkids).
Configuring certificate server (pki-cad): Estimated time 33 minutes 30 seconds
  [1/21]: creating certificate server user
  .
  .
  [21/21]: Configure HTTP to proxy connections
Done configuring certificate server (pki-cad).
Configuring directory server (dirsrv): Estimated time 31 minutes
  [1/38]: creating directory server user
  .
  .
  [38/38]: configuring directory to start on boot
Done configuring directory server (dirsrv).
Configuring Kerberos KDC (krb5kdc): Estimated time 30 minutes 30 seconds
  [1/10]: adding sasl mappings to the directory
  .
  .
  [10/10]: configuring KDC to start on boot
Done configuring Kerberos KDC (krb5kdc).
Configuring kadmin
  [1/2]: starting kadmin 
  [2/2]: configuring kadmin to start on boot
Done configuring kadmin.
Configuring ipa_memcached
  [1/2]: starting ipa_memcached 
  [2/2]: configuring ipa_memcached to start on boot
Done configuring ipa_memcached.
Configuring the web interface (httpd): Estimated time 31 minutes
  [1/13]: setting mod_nss port to 443
  .
  .
  [13/13]: configuring httpd to start on boot
Done configuring the web interface (httpd).
Applying LDAP updates
Restarting the directory server
Restarting the KDC
Sample zone file for bind has been created in /tmp/sample.zone.dOYuEz.db
Restarting the web server
==============================================================================
Setup complete
.
.
.

Comment 9 errata-xmlrpc 2013-02-21 09:31:53 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.

http://rhn.redhat.com/errata/RHSA-2013-0528.html