cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Marek Grac <mgrac@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fence-agents-4.0.1 stable release
Date: Mon, 01 Jul 2013 15:15:02 +0200	[thread overview]
Message-ID: <51D180D6.6060200@redhat.com> (raw)

Welcome to the fence-agents 4.0.1 release.

This release includes a few minor bug fixes:
* fence agent node assassin was temporary removed

* fix problem for actions for fence agents without plugs/ports
* fix validation for password,password_script or identity file
* fence_scsi now supports delay as other fence agents (be aware to use -H which is agent specific)
* support for new fencing method in fence_dummy - type=fail - all operation should fail
* improve work with invalid power states
* fix fence_apc after introducing support for firmware 5.x - problem occurs on devices with more than 25 devices
* command-prompt can be properly entered from user's input
* fence_dummy can benefit from random delay at its start

* manual page for fence_scsi was extended to provide info about 'unfence'
* notice was added that command prompt is expected to be python regular expression


The new source tarball can be downloaded here:

https://fedorahosted.org/releases/f/e/fence-agents/fence-agents-4.0.1.tar.xz

To report bugs or issues:

    https://bugzilla.redhat.com/

Would you like to meet the cluster team or members of its community?

    Join us on IRC (irc.freenode.net #linux-cluster) and share your
    experience  with other sysadministrators or power users.

Thanks/congratulations to all people that contributed to achieve this
great milestone.

m,



                 reply	other threads:[~2013-07-01 13:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51D180D6.6060200@redhat.com \
    --to=mgrac@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).