Bug 743076

Summary: All cluster nodes reboot when any change in the cluster resource/application is done from conga
Product: Red Hat Enterprise Linux 6 Reporter: sk <khandu20>
Component: clusterAssignee: Fabio Massimo Di Nitto <fdinitto>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Cluster QE <mspqa-list>
Severity: urgent Docs Contact:
Priority: medium    
Version: 6.1CC: ccaulfie, cluster-maint, lhh, rpeterso, syeghiay, teigland
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-06 14:47:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 756082    
Attachments:
Description Flags
It's the cluster.conf none

Description sk 2011-10-03 19:02:13 UTC
Created attachment 526111 [details]
It's the cluster.conf

Description of problem:
Immediately after adding a Resource/Application/ResourceToAnApplication in the RHEL cluster, all the nodes reboot.

Version-Release number of selected component (if applicable):
RHEL 6.0 and RHEL 6.1

How reproducible:
Always

Steps to Reproduce:
1.Add a script resource
2.Submit it
3.All the nodes of the cluster reboot.
  
Actual results:
All the nodes of the cluster reboot.

Expected results:
After submitting any change in the cluster, it should successfully reflect the changes and get propagated to all the cluster nodes.


Additional info:
Please find attached the cluster.conf file i am using.

Comment 2 Fabio Massimo Di Nitto 2011-10-03 20:50:46 UTC
Please attach also /var/log/cluster/ from all cluster nodes.

cluster.conf alone isn't enough to determine what's happening. I also assume you mean luci and not conga in the report.

Comment 3 Suzanne Logcher 2011-10-06 18:43:08 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
               
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 4 sk 2011-10-11 16:52:12 UTC
1. It's Luci and not conga.

2. It is a very critical issue as it affects our testing drastically so request you to please let me know the required hints to resolve it if not fix it.

3. What is the link to download RHEL 6.2 beta and by when will it be released.

Comment 5 Suzanne Logcher 2011-10-11 17:41:51 UTC
RHEL 6.2 Beta was announced on Oct 5.  Here is the announcement sent to the rhelv6 lists (rhelv6-announce, rhelv6-list, and rhelv6-beta-list).  Feel free to subscribe.

Dear Red Hat customers and partners:

Today, we are pleased to announce the availability of the beta
for Red Hat Enterprise Linux 6.2.  This beta includes a broad
set of updates to the existing feature set and also provides
rich new functionality particularly in the areas of performance
and scaling, identity management, high availability, advanced
storage, and networking as well as enablement for the latest
hardware and architectures.   

Already the established leader as both a virtual machine guest
and hypervisor host, Red Hat Enterprise Linux 6.2 introduces
new features and enhanced functionality that reinforces Red Hat
Enterprise Linux as the standard operating system platform for
the enterprise.

Key functionality in this beta include:

Performance and Scaling

o Kernel-level optimizations implemented in the process
  scheduler, networking, virtualization, and I/O subsystems
  will improve performance and scalability.
o Faster creation of ext4 file systems and improved response
  times in XFS for certain workloads. 
o Improved CPU controller, scalability and enhanced resource
  management features to set processor utilization ceilings.

Identity Management

o Centralized identity management for the flexible management
  of users, roles, policies, and authentication services.  
o New capabilities for the unification of Kerberos ticketing,
  DNS naming, user and group ids, and Linux systems policies
  into a single service.

High Availability 

o Support for Red Hat Enterprise Linux 6 guests on VMware(R)
  hosts and comprehensive support for the GFS2 shared storage
  file system have been added to the High Availability Add-on
  Product, creating a more tightly integrated environment.  
o Full support for the UDP-unicast protocol which reduces
  administration overhead, resulting in easier cluster
  deployment.     

Advanced Storage

o World Wide Name (WWN), or World Wide Identifier (WWID), for
  storage devices making it easier to identify them during
  installation for users utilizing Storage Area Networks (SAN)
  and other advanced network typologies. 
o Within production environments using Infiniband - where high
  throughput and low latency are key requirements - Red Hat
  Enterprise Linux can now be purposed as an iSCSI initiator
  and storage server.

Networking

o Transmit Packet Steering (XPS) capabilities which improve
  network packet transmission throughput by 30%.

We look to our community and partners for feedback to ensure
Red Hat Enterprise Linux 6.2 is yet another high-quality
release. The beta can be accessed at

  https://access.redhat.com/downloads/

The Release Notes can be accessed at

  https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/6.2_Release_Notes/index.html

The public blog can be accessed at

  http://www.redhat.com/about/news/blog/red-hat-announces-the-beta-release-of-red-hat-enterprise-linux-6-2

To learn more about Red Hat Enterprise Linux 6, visit 

  http://www.redhat.com/rhel/
 
For a technical deep-dive on Red Hat Enterprise Linux 6, visit 

  http://www.redhat.com/about/news/blog/red-hat-enterprise-linux-6-a-technical-look-at-red-hats-defining-new-operating-platform/


We are always thankful to our partners and our customers who
continue to work with us to develop and deliver the highest
quality platform available today.


The Enterprise Linux Team

Comment 6 Fabio Massimo Di Nitto 2011-10-12 04:02:17 UTC
I still need the logs from the nodes and the luci instance or sosreports.

As written in the original report, this bug is always reproducible, please reproduce and collect the information we need to fix it.

Also please contact GSS and open a ticket to associate with this BZ. Direct request to engineering are not prioritized the same way as if coming from Global Support Service.