Bug 476698
Summary: | conga doesn't run with selinux | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Brian Brock <bbrock> |
Component: | conga | Assignee: | Ryan McCabe <rmccabe> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | cfeist, cluster-maint, liko, rfujita, vvaldez |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-03-30 08:55:28 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brian Brock
2008-12-16 16:13:35 UTC
when trying to create a cluster named "t1": An error occurred when trying to contact any of the nodes in the t1 cluster. (In reply to comment #1) > when trying to create a cluster named "t1": > > An error occurred when trying to contact any of the nodes in the t1 cluster. The name does not seem to matter, all of my clusters report this error when creating a cluster, even with selinux disabled using RHEL 5.3 This never happened before using 5.2 and previous. If you wait a few minutes and hit refresh, everything works. Should I file a new bug on this? I just double-checked, and although the systems running ricci have selinux disabled, the system running luci has selinux enabled, and the luci server is typically not changed, where the ricci systems are always kickstarted. My apologies on the incorrect information, this is definitely what I am seeing. We don't have selinux support lined up for rhel5.4 inclusion, so I'm going to move this bug to target rhel5.5. Certainly when cluster suite support working with selinux, conga (ricci/luci) should as well. 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-2010-0289.html |