[ClusterLabs] Ocassionally IPaddr2 resource fails to start

Jan Pokorný jpokorny at redhat.com
Mon Oct 7 12:21:36 EDT 2019


On 07/10/19 09:24 -0500, Ken Gaillot wrote:
> If this always happens when the VM is being snapshotted, you can put
> the cluster in maintenance mode (or even unmanage just the IP
> resource) while the snapshotting is happening. I don't know of any
> reason why snapshotting would affect only an IP, though.

it might be interesting if you could share the details to grow the
shared knowledge and experience in case there are some instances of
these problems reported in the future.

In particular, it'd be interesting to hear:

- hypervisor

- VM OS + if plain oblivious to running virtualized,
  or "the optimal arrangement" (e.g., specialized drivers, virtio,
  "guest additions", etc.)

(I think IPaddr2 is iproute2-only, hence in turn, VM OS must be Linux)

Of course, there might be more specific things to look at if anyone
here is an expert with particular hypervisor technology and the way
the networking works with it (no, not me at all).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20191007/d8a94692/attachment.sig>

More information about the Users mailing list