From: Marek Grac <mgrac@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fence-agents-4.0.7 stable release
Date: Mon, 17 Feb 2014 16:33:22 +0100 [thread overview]
Message-ID: <53022BC2.1050804@redhat.com> (raw)
Welcome to the fence-agents 4.0.6 release.
This release includes quite a lot of bugfixes:
* support for firmware v1.40 for WTI (MPC series)
* nss_wrapper used for fence_ilo was replaced by gnutls-cli
* --delay was not respected in fence_vmware_soap
* fabric fence agents have 'off' as default action
* fence_scsi now generates correct key on corosync clusters
* regression was found in fence_ipmilan where -P and -L were
interchanged on command line
(there was no problem with long options and input from STDIN)
* fence_vmware_soap now fails with proper error message when user does
not have enough privileges
The new source tarball can be downloaded here:
https://fedorahosted.org/releases/f/e/fence-agents/fence-agents-4.0.7.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:[~2014-02-17 15:33 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=53022BC2.1050804@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.