Bug was confirmed. :-)
http://developerbugs.linux-foundation.org/show_bug.cgi?id=2317
Hopefully fix will follow soon.
Regards,
M.
Martin Gombač wrote:
Shoud i file a bug for the problem (restarting resources) described
below?
Regards,
M.
Dejan Muhamedagic wrote:
Hi,
On Mon, Jan 18, 2010 at
Hi,
On Wed, Jan 20, 2010 at 10:29:54AM +0100, Martin Gombač wrote:
> Shoud i file a bug for the problem (restarting resources) described below?
> Regards,
> M.
>
> Dejan Muhamedagic wrote:
> >Hi,
> >
> >On Mon, Jan 18, 2010 at 10:00:39PM +0100, Martin Gombač wrote:
> >>Hi,
> >>
> >>i have one m/s
Shoud i file a bug for the problem (restarting resources) described below?
Regards,
M.
Dejan Muhamedagic wrote:
Hi,
On Mon, Jan 18, 2010 at 10:00:39PM +0100, Martin Gombač wrote:
Hi,
i have one m/s drbd resource and one Xen instance on top. Both m/s
are primary.
When i restart node that's
Hi,
On Mon, Jan 18, 2010 at 10:00:39PM +0100, Martin Gombač wrote:
> Hi,
>
> i have one m/s drbd resource and one Xen instance on top. Both m/s
> are primary.
> When i restart node that's _not_ hosting the Xen instance (ibm1),
> pacemaker restarts running Xen instance on the other node (ibm2).
>
Hi,
i have one m/s drbd resource and one Xen instance on top. Both m/s are
primary.
When i restart node that's _not_ hosting the Xen instance (ibm1),
pacemaker restarts running Xen instance on the other node (ibm2). There
is no need to do that. I thought it got fixed
(http://developerbugs.lin
