From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] 3.1.8 rc fails to validate IP resources
Date: Sun, 04 Dec 2011 19:43:24 +0100 [thread overview]
Message-ID: <4EDBBF4C.1020906@redhat.com> (raw)
In-Reply-To: <4EDBB350.7070607@alteeve.com>
On 12/04/2011 06:52 PM, Digimer wrote:
> On 12/04/2011 03:12 AM, Fabio M. Di Nitto wrote:
>> On 12/03/2011 11:34 PM, Digimer wrote:
>>> Looks like the IP section was not added to cluster.rng.
>>>
>>
>> You need to install latest and greatest resource-agents :)
>>
>> Fabio
>
> Now *that's* just embarrassing! :P
>
Rule #1 applies here.. no matter how much love you put in the first
release, you can be sure that it won't be even build anywhere other than
your machine ;)
Relax, and keep going.. ;) you are doing good so far. :)
Fabio
prev parent reply other threads:[~2011-12-04 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 22:34 [Cluster-devel] 3.1.8 rc fails to validate IP resources Digimer
2011-12-04 8:12 ` Fabio M. Di Nitto
2011-12-04 17:52 ` Digimer
2011-12-04 18:43 ` Fabio M. Di Nitto [this message]
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=4EDBBF4C.1020906@redhat.com \
--to=fdinitto@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).