On 07/25/2011 06:04 PM, Steven Dake wrote:
On 07/25/2011 08:45 AM, carlopmart wrote:
On 07/25/2011 05:42 PM, Steven Dake wrote:
are caused by this issue.
So, as a temporary work-around for this time, woule be (at your own
risks) to downgrade to 2.6.32-71.29.1.el6 kernel :
yum install kernel-2.6.32-71.29.1.el6.x86_64
Regards,
Hi Steven and Nicolas,
Is this bug resolved in RHEL6.1 with all updates applied?? Do I
need to
use some specific kernel version 2.6.32-131.2.1 or 2.6.32-131.6.1?
Thanks.
the corosync portion is going through QE. The kernel portion remains
open.
Regards
-steve
Thanks Steve, then, Can I use last corosync version provided with
RHEL6.1 and last RHEL6.0's kernel version without problems??
I recommend not mixing without a support signoff.
Then, how can I install rhcs under rhel6.x and prevent this bug??
get a support signoff. Also the corosync updates have not finished
through our validation process. Only hot fixes (from support) are available
Regards
-steve
Sorry to re-open this thread ... But exists any news about this problem??
--
CL Martinez
carlopmart {at} gmail {d0t} com
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
