Files
watcher/releasenotes/notes/bug-2131663-b486d36f77d13a5d.yaml
Alfredo Moralejo 13d73e9b4e Make VM migrations timeout configurable and apply reasonable defaults
This change adds new 'migration_max_retries' and 'migrate_interval' configuration
parameters to the [nova] section to control timeout behavior for VM
migration operations.

Changes:
- Add a new [nova] section to the configuration file to store parameters
  related to the integration with nova.
- Add migration_max_retries config option (default: 180) to define the max
  retries to check the result of VM migrations before giving up.
- Add migration_interval config option (default: 5 seconds) to define the
  polling interval to check the VM status in migrate actions.
- Update live_migrate_instance() and watcher_non_live_migrate_instance()
  to use configured migration_max_retries when retry parameter is None.
- Add new parameter interval to the live_migrate_instance() and
  watcher_non_live_migrate_instance() methods.
- Add comprehensive unit tests for timeout and retry functionality
- Set migrate_max_retries to 120 and migration_interval to 1s in CI jobs.

Closes-Bug: #2131663

Assisted-By: claude-code (claude-sonnet-4.5)

Change-Id: Ifed3c058d821ce3b0741627dcc414fe054eb9dca
Signed-off-by: Alfredo Moralejo <amoralej@redhat.com>
2025-12-02 08:42:40 +01:00

12 lines
492 B
YAML

---
features:
- |
New parameters `migration_max_retries` and `migration_interval` have been
added to the `nova` section to define the maximum retries and polling
interval in VM migrations. Default values are 180 and 5 seconds.
fixes:
- |
Fixed the issue when migrate actions Failed when the migration took more that
120 seconds. After this patch, the default timeout is 900 seconds (15 minutes)
which should be a reasonable value for most OpenStack installations.