On Wed, 2017-11-01 at 10:04 +0100, Ferenc Wágner wrote:
> Ken Gaillot writes:
>
> > When an operation completes, a history entry () is
> > added to
> > the pe-input file. If the agent supports reload, the entry will
> > include
> > op-force-restart and op-restart-digest fields. Now I see those ar
Ken Gaillot writes:
> When an operation completes, a history entry () is added to
> the pe-input file. If the agent supports reload, the entry will include
> op-force-restart and op-restart-digest fields. Now I see those are
> present in the vm-alder_last_0 entry, so agent support isn't the issue
On Tue, 2017-10-31 at 18:44 +0100, Ferenc Wágner wrote:
> Ken Gaillot writes:
>
> > The pe-input is indeed entirely sufficient.
> >
> > I forgot to check why the reload was not possible in this case. It
> > turns out it is this:
> >
> > trace: check_action_definition: Resource vm-alder
Ken Gaillot writes:
> The pe-input is indeed entirely sufficient.
>
> I forgot to check why the reload was not possible in this case. It
> turns out it is this:
>
> trace: check_action_definition: Resource vm-alder doesn't know
> how to reload
>
> Does the resource agent implement the "re
On Tue, 2017-10-31 at 09:33 +0100, Ferenc Wágner wrote:
> Ken Gaillot writes:
>
> > On Fri, 2017-10-20 at 15:52 +0200, Ferenc Wágner wrote:
> >
> > > Ken Gaillot writes:
> > >
> > > > On Fri, 2017-09-22 at 18:30 +0200, Ferenc Wágner wrote:
> > > >
> > > > > Ken Gaillot writes:
> > > > >
> >
Ken Gaillot writes:
> On Fri, 2017-10-20 at 15:52 +0200, Ferenc Wágner wrote:
>
>> Ken Gaillot writes:
>>
>>> On Fri, 2017-09-22 at 18:30 +0200, Ferenc Wágner wrote:
>>>
Ken Gaillot writes:
> Hmm, stop+reload is definitely a bug. Can you attach (or email it
> to me privately
On Fri, 2017-10-20 at 15:52 +0200, Ferenc Wágner wrote:
> Ken Gaillot writes:
>
> > On Fri, 2017-09-22 at 18:30 +0200, Ferenc Wágner wrote:
> > > Ken Gaillot writes:
> > >
> > > > Hmm, stop+reload is definitely a bug. Can you attach (or email
> > > > it to
> > > > me privately, or file a bz wit
Ken Gaillot writes:
> On Fri, 2017-09-22 at 18:30 +0200, Ferenc Wágner wrote:
>> Ken Gaillot writes:
>>
>>> Hmm, stop+reload is definitely a bug. Can you attach (or email it to
>>> me privately, or file a bz with it attached) the above pe-input file
>>> with any sensitive info removed?
>>
>> I
On Fri, 2017-09-22 at 18:30 +0200, Ferenc Wágner wrote:
> Ken Gaillot writes:
>
> > Hmm, stop+reload is definitely a bug. Can you attach (or email it
> > to me
> > privately, or file a bz with it attached) the above pe-input file
> > with
> > any sensitive info removed?
>
> I sent you the pe-inp
Ken Gaillot writes:
> Hmm, stop+reload is definitely a bug. Can you attach (or email it to me
> privately, or file a bz with it attached) the above pe-input file with
> any sensitive info removed?
I sent you the pe-input file privately. It indeed shows the issue:
$ /usr/sbin/crm_simulate -x pe
On Fri, 2017-09-22 at 16:23 +0200, Ferenc Wágner wrote:
> Hi,
>
> I'm running a custom resourcre agent under Pacemaker 1.1.16, which
> has
> several reloadable parameters:
>
> $ /usr/sbin/crm_resource --show-metadata=ocf:niif:TransientDomain |
> fgrep unique=
>
>
>
>
>
>
>
>
>
>
> I use
Hi,
I'm running a custom resourcre agent under Pacemaker 1.1.16, which has
several reloadable parameters:
$ /usr/sbin/crm_resource --show-metadata=ocf:niif:TransientDomain | fgrep
unique=
I used to routinely change the unique="0" parameters without having the
corresponding resources re
12 matches
Mail list logo