yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #51175
[Bug 1583145] [NEW] live-migration monitoring is not working properly
Public bug reported:
Live-migration monitoring is based on the memory migration only. Which
means that if a live-migration is taking a long time to migrate a disk,
only the live_migration_progress_timeout parameter will be taken into
account and will supersede the live_migration_completion_timeout
parameter. In other words, because live_migration_progress_timeout is
logically smaller than live_migration_completion_timeout, the later will
never be used except in a case where the disk migration is fast and the
memory migration is slow.
Steps to reproduce:
- live-migrate an instance with lots a data on its ephemeral disk
- observe that the live-migration is aborted because of live_migration_progress_timeout only.
** Affects: nova
Importance: Undecided
Status: New
** Summary changed:
- live-migration monitoring is working properly
+ live-migration monitoring is not working properly
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1583145
Title:
live-migration monitoring is not working properly
Status in OpenStack Compute (nova):
New
Bug description:
Live-migration monitoring is based on the memory migration only. Which
means that if a live-migration is taking a long time to migrate a
disk, only the live_migration_progress_timeout parameter will be taken
into account and will supersede the live_migration_completion_timeout
parameter. In other words, because live_migration_progress_timeout is
logically smaller than live_migration_completion_timeout, the later
will never be used except in a case where the disk migration is fast
and the memory migration is slow.
Steps to reproduce:
- live-migrate an instance with lots a data on its ephemeral disk
- observe that the live-migration is aborted because of live_migration_progress_timeout only.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1583145/+subscriptions
Follow ups