diff --git a/releasenotes/notes/import-locking-behavior-901c691f3839fe0a.yaml b/releasenotes/notes/import-locking-behavior-901c691f3839fe0a.yaml index de23b5d4dd..0c7f808c89 100644 --- a/releasenotes/notes/import-locking-behavior-901c691f3839fe0a.yaml +++ b/releasenotes/notes/import-locking-behavior-901c691f3839fe0a.yaml @@ -1,14 +1,13 @@ --- fixes: - | - A change was added to the import API which provides time-based - locking of an image to exclude other import operations from - starting until the lock-holding task completes (see Bug - 1884596_). The lock is based on the task that we start to do the - work, and the UUID of that task is stored in the - ``os_glance_import_task`` image property, which indicates who owns - the lock. If the task holding the lock fails to make progress for - 60 minutes, another import operation will be allowed to steal the - lock and start another import operation. + Bug 1884596_: A change was added to the import API which provides + time-based locking of an image to exclude other import operations + from starting until the lock-holding task completes. The lock is + based on the task that we start to do the work, and the UUID of + that task is stored in the ``os_glance_import_task`` image property, + which indicates who owns the lock. If the task holding the lock fails + to make progress for 60 minutes, another import operation will be + allowed to steal the lock and start another import operation. .. _1884596: https://bugs.launchpad.net/glance/+bug/1884596 diff --git a/releasenotes/notes/victoria-m3-releasenotes-9209cea98a29abc4.yaml b/releasenotes/notes/victoria-m3-releasenotes-9209cea98a29abc4.yaml new file mode 100644 index 0000000000..49981623c6 --- /dev/null +++ b/releasenotes/notes/victoria-m3-releasenotes-9209cea98a29abc4.yaml @@ -0,0 +1,30 @@ +--- +features: + - | + Added support to calculate virtual size of image based on disk format + - | + Added support for sparse image upload for filesystem and rbd driver + - | + Improved performance of rbd store chunk upload + - | + Added support to configure multiple cinder stores + +upgrade: + - | + After upgrading, deployments using the cinder backend should + update their config to specify a volume type. Existing images on + those backends will be updated at runtime (lazily, when they are + first read) to a location URL that includes the store and volume + type information. + +fixes: + - | + Bug 1891190_: test_reload() functional test causes hang and jobs TIMED_OUT + - | + Bug 1891352_: Failed import of one store will remain in progress forever if all_stores_must_succeed=True + - | + Bug 1887099_: Invalid metadefs for watchdog + + .. _1891190: https://code.launchpad.net/bugs/1891190 + .. _1891352: https://code.launchpad.net/bugs/1891352 + .. _1887099: https://code.launchpad.net/bugs/1887099