Your message dated Tue, 05 Jan 2021 01:12:38 +0200
with message-id <[email protected]>
and subject line Re: Bug#969028: ganeti: migration_caps break migration
has caused the Debian Bug report #969028,
regarding ganeti: migration_caps break migration
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
969028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969028
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ganeti
Version: 2.16.0-5
Severity: important
Dear Maintainer,
using Ganeti 2.16 and qemu 1:5.0-14~bpo10+1 I tried setting
migration_caps for the cluster. But no matter which value i use it
breaks migration.
Migration then "goes"
- Setup disks and prepare target node
- starting memore transfer
- "Migration failed, aborting"
- Closing disks
That is entirely independent on which value I put into the caps.
Unsetting migration_caps and retrying the migration - it fails again.
Looking more in detail it appears that its setting the caps on the
source side. But possibly forgets to set them on the target side so qemu
hates doing migration?!
And when it breaks, it forgets to unset the capabilities, so next
migrations break too. One has to manually connect to the monitor and
unset them, before migration works again.
--
bye, Joerg
--- End Message ---
--- Begin Message ---
Source: ganeti
Version: 3.0.0-1
Hi,
Joerg Jaspert <[email protected]> writes:
> Source: ganeti
> Version: 2.16.0-5
> Severity: important
>
> Dear Maintainer,
>
> using Ganeti 2.16 and qemu 1:5.0-14~bpo10+1 I tried setting
> migration_caps for the cluster. But no matter which value i use it
> breaks migration.
>
> Migration then "goes"
> - Setup disks and prepare target node
> - starting memore transfer
> - "Migration failed, aborting"
> - Closing disks
>
> That is entirely independent on which value I put into the caps.
>
> Unsetting migration_caps and retrying the migration - it fails again.
>
> Looking more in detail it appears that its setting the caps on the
> source side. But possibly forgets to set them on the target side so qemu
> hates doing migration?!
>
> And when it breaks, it forgets to unset the capabilities, so next
> migrations break too. One has to manually connect to the monitor and
> unset them, before migration works again.
>
> --
> bye, Joerg
This was fixed upstream in 3.0.0, see
https://github.com/ganeti/ganeti/pull/1525.
Regards,
Apollon
--- End Message ---
