... | ... | @@ -610,20 +610,20 @@ Import procedure: |
|
|
gnt-instance failover -f $INSTANCE &&
|
|
|
gnt-instance start $INSTANCE
|
|
|
|
|
|
The above can sometimes fail if the allocator is upset about
|
|
|
something in the cluster, for example:
|
|
|
|
|
|
Can's find secondary node using iallocator hail: Request failed: No valid allocation solutions, failure reasons: FailMem: 2, FailN1: 2
|
|
|
|
|
|
This situation is covered by [ticket 33785](https://bugs.torproject.org/33785). To work around the
|
|
|
allocator, you can specify a secondary node directly:
|
|
|
|
|
|
gnt-instance modify -t drbd -n fsn-node-04.torproject.org $INSTANCE &&
|
|
|
gnt-instance failover -f $INSTANCE &&
|
|
|
gnt-instance start $INSTANCE
|
|
|
The above can sometimes fail if the allocator is upset about
|
|
|
something in the cluster, for example:
|
|
|
|
|
|
Can's find secondary node using iallocator hail: Request failed: No valid allocation solutions, failure reasons: FailMem: 2, FailN1: 2
|
|
|
|
|
|
This situation is covered by [ticket 33785](https://bugs.torproject.org/33785). To work around the
|
|
|
allocator, you can specify a secondary node directly:
|
|
|
|
|
|
gnt-instance modify -t drbd -n fsn-node-04.torproject.org $INSTANCE &&
|
|
|
gnt-instance failover -f $INSTANCE &&
|
|
|
gnt-instance start $INSTANCE
|
|
|
|
|
|
TODO: move into fabric, maybe in a `libvirt-import-live` or
|
|
|
`post-libvirt-import` job that would also do the renumbering below
|
|
|
TODO: move into fabric, maybe in a `libvirt-import-live` or
|
|
|
`post-libvirt-import` job that would also do the renumbering below
|
|
|
|
|
|
11. change IP address in the following locations:
|
|
|
|
... | ... | |