Debian Codegraph @

releasenotes/notes/cinder-manage-online-migrations-exit-status-7c16edb7facc37bb.yaml

raw
1 ---
2 upgrade:
3 - |
4 The ``cinder-manage db online_data_migrations`` command now returns exit
5 status 2 in the case where some migrations failed (raised exceptions) and
6 no others were completed successfully from the last batch attempted. This
7 should be considered a fatal condition that requires intervention. Exit
8 status 1 will be returned in the case where the ``--max-count`` option was
9 used and some migrations failed but others succeeded (updated at least one
10 row), because more work may remain for the non-failing migrations, and
11 their completion may be a dependency for the failing ones. The command
12 should be reiterated while it returns exit status 1, and considered
13 completed successfully only when it returns exit status 0.