90009aac84
Currently, when there is a volume_migrate action and migration_type is `retype`, watcher assumes that the retype always triggers a migration and checks the result of the retype based on the fields related to the migration action (actually, it uses the same function to check the result when `migration_type` is `retype` or `migrate`. This creates problem in different scenarios: - Actions keep in ONGOING status forever for volumes which have never being migrated as the migration fields of the volume are empty. - Actions which were migrated anytime before, still have the old values so it may report the status of te retype actions wrongly. This patch is implementing an entirely new function to check the result of a retype action based on the final type and the status field of the volume. This should be valid for any kind of retype action, with or without migration. The criteria for successfull retype is that the type for the volume is the destination one in the action and the status is available or in-use. Closes-Bug: #2112100 Change-Id: I76e91ed99e7a814a43a6dd906b6bcc150d471624 Signed-off-by: jgilaber <jgilaber@redhat.com>
12 lines
413 B
YAML
12 lines
413 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Currently, when Watcher applies a `volume_migrate` action with value
|
|
`retype` for the `migratione_type`, it can wrongly report the result of
|
|
the action when the retype does not trigger a volume migration.
|
|
|
|
This patch fixes the logic to validate the resulting state of the action
|
|
and reports it correctly.
|
|
|
|
For more details: https://bugs.launchpad.net/watcher/+bug/2112100
|