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 709330 - IPA Replica not started on reboot
Summary: IPA Replica not started on reboot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On: 705794
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-31 12:13 UTC by Ken Reilly
Modified: 2015-01-04 23:49 UTC (History)
9 users (show)

Fixed In Version: ipa-2.0.0-23.el6_1.1
Doc Type: Bug Fix
Doc Text:
Previously, the ipa service was not enabled via the chkconfig tool during the installation of a replica server. Subsequently, when the replica server was restarted, the ipa service was not started. With this update, replica servers are properly configured to start on boot.
Clone Of:
Environment:
Last Closed: 2011-06-15 00:22:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0865 0 normal SHIPPED_LIVE ipa bug fix update 2011-06-15 00:21:53 UTC

Description Ken Reilly 2011-05-31 12:13:47 UTC
This bug has been copied from bug #705794 and has been proposed
to be backported to 6.1 z-stream (EUS).

Comment 4 Tomas Capek 2011-06-06 09:54:47 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, the ipa service was not enabled via the chkconfig tool during the installation of a replica server. Subsequently, when the replica server was restarted, the ipa service was not started. With this update, replica servers are properly configured to start on boot.

Comment 5 Namita Soman 2011-06-09 16:09:51 UTC
Verified using ipa-server-2.0.0-23.el6_1.1.x86_64

rebooted replica machine
when it came back up, verified status:
# ipactl status
Directory Service: RUNNING
KDC Service: RUNNING
KPASSWD Service: RUNNING
DNS Service: RUNNING
HTTP Service: RUNNING
CA Service: RUNNING

Comment 6 errata-xmlrpc 2011-06-15 00:22:04 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0865.html


Note You need to log in before you can comment on or make changes to this bug.