* Update cinder from branch 'master'
to e28867ba8dc6dcd786323fa83b70827154d856b1
- Merge "Fujitsu driver: Improve volume deletion"
- Fujitsu driver: Improve volume deletion
To improve the volume deletion process, add a step to check associated
copy sessions. Additionally, it also improves the process of retrieving
storage-managed volume numbers.
There was a problem where the volume could not be deleted because the
copy session information acquired by SMI-S IF from ETERNUS DX Storage,
which was cached and did not reflect the information that had just
been executed.
This problem has been addressed through improvements in information
retrieval.
Change-Id: I21d5c1fa4f13e688a5f73535c8d6fdec613adc03
* Update cinder from branch 'master'
to 7e9626404c71b3ec7fa30a56b376cae3ee979547
- Merge "docs: Migrate docs from cinderclient to OSC (part 1)"
- docs: Migrate docs from cinderclient to OSC (part 1)
Fix a couple of outdated references along the way.
Change-Id: I9a7fb660bfd622ccdfb40bc6936493c87f6a1d25
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update cinder from branch 'master'
to d7994a9912bc0bf2e1fa1354451295ee9356257a
- Merge "[docs] Add recheck advice"
- [docs] Add recheck advice
Add some general info about gate tests and a link to the recheck
section of the project team guide.
Change-Id: Iedd11fa49489c9c855cf33ebc221fcbf218fa2a7
* Update cinder from branch 'master'
to 83c3e8e0e36a4117f77237f5b6ffc6e264b8fffe
- Merge "Update CI for Dalmatian"
- Update CI for Dalmatian
Updates:
- run py311 func job in gate (was py310)
- add py312 testenvs to tox.ini
- did not remove py38 testenvs from tox.ini
- removed py38 classifier from setup.cfg, but did not change
python_requires (currently it's >=3.8)
Python 3.12 unit tests will run non-voting in the gate as part of the
openstack-python3-jobs template. Python 3.10 coverage is being handled
by tempest running in Ubuntu 22.04.
Change-Id: I72ec22780d36ea3e56386ae2bd74bf5b9806731c
* Update cinder from branch 'master'
to b36142602e4a478e0e9349126ab2bee92f3f2d18
- Merge "Fix snapshot status is always backing-up"
- Fix snapshot status is always backing-up
This patch adds a snapshot clean operation in the
cleanup_incomplete_backup_operations process of c-bak.
Co-Authored-by: Christian Rohmann <christian.rohmann@inovex.de>
Closes-Bug: #1938488
Change-Id: Ifa3d572139fc37c94e3b50a02e61c9818a1b6501
* Update cinder from branch 'master'
to d46e2ebbd719b01aa3497853332fda1b724c281d
- Merge "Ceph: Catch more failure conditions on volume backup"
- Ceph: Catch more failure conditions on volume backup
This fixes issues for volume backups with the Ceph driver
where failures of the first process ("rbd export-diff") were
not caught. Instead, only the return code of the second
process ("rbd import-diff") was recognized.
This change also preserves the stderr that was lost previously
in order to ease debugging.
Closes-Bug: 2031897
Co-Authored-By: Pete Zaitcev <zaitcev@kotori.zaitcev.us>
Change-Id: I53b573bfff64e7460ef34f1355d3a9d52a8879f9
Signed-off-by: Jan Hartkopf <jhartkopf@inovex.de>
* Update cinder from branch 'master'
to f3a63ed6fa4cb2366381255f44e55f95f7d44ea2
- [docs] update gerrit group info
The cinder-core gerrit group is configured directly in project-config
to act as openstackclient/openstackSDK "service cores". Add info to
the cinder-groups document so that we know where to look if this needs
to be changed or adjusted in the future.
Change-Id: I6b626604f9ff573ab59fd4867fdee7a0178ed7f0
* Update cinder from branch 'master'
to b0f0b9015b9dfa228dff98eeee5116d8eca1c3cc
- Merge "hacking: Fix E501 errors"
- hacking: Fix E501 errors
https://github.com/PyCQA/pycodestyle/issues/622 was fixed
in pycodestyle 2.4.0, which triggers E501 for docstrings
that didn't previously.
This shows up if we pull in a hacking>=6.0.0.
Change-Id: Id3c8a66c26f01ca734e6bc33c14f5deedf8e15f3
* Update cinder from branch 'master'
to 08adeda490d759d7debbfe90963ac6bde308258c
- Merge "Remove six from Huawei drivers"
- Remove six from Huawei drivers
Change-Id: I2f0c483b26d70435e1deea021a79e4a892426826
* Update cinder from branch 'master'
to c0d824dd0e2d4aac6f8756176c64fa02970161e4
- Merge "Imported Translations from Zanata"
- Imported Translations from Zanata
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
Change-Id: I604c2ed35f14040b10fc27d1a8f7e379a54a7205
* Update cinder from branch 'master'
to 54856da91045299537fdb69edf43fb61aba79cc6
- Merge "PowerMax: Allow live migration without pool name"
- PowerMax: Allow live migration without pool name
This change is to update the live migration ability in environments
using PowerMax. In previous 2023.1 version, the live migration fails
without a pool name.
The update adds the ability of live migration without a pool name.
Change-Id: Iad767cd516c8527136508470629236f68e0c7cc2
Closes-Bug: #2034937
* Update cinder from branch 'master'
to 00e59c7d1d7ab8adb4f522247cfb58fe768ebf4d
- Merge "Dell PowerMax: Fix SnapVx unlink failure"
- Dell PowerMax: Fix SnapVx unlink failure
Dell PowerMax SnapVx unlink fails as the linked device
is not yet fully defined.
This patch fixed the issue by checking the new configuration
'snapvx_unlink_symforce' and the linked device 'defined' status
to determine the value of 'symforce' in the payload of
SnapVx unlink restcall.
Closes-Bug: #2045230
Change-Id: I614f6aef2d4da76c417b4a143ab80e4a5f716dcd
* Update cinder from branch 'master'
to 273175720fa9c7885eaf2e8df46af5007aaecd3a
- Merge "HPE 3par: Unable to create clone of replicated vol"
- HPE 3par: Unable to create clone of replicated vol
Two possibilities of clone volume:
1] same size, online copy
Existing behaviour: start clone & return from function.
Error occur because clone is not yet complete and
code tries to create vol on secondary array.
2] size is different, offline copy
Existing behaviour: (i) create new replicated vol.
(ii) during clone operation below error occur:
Volume is involved in remote copy
(iii) Since clone operation fails, delete new replicated vol (as cleanup).
To overcome both possibilities, code changes are done.
For clone of replicated vol, create offline copy only.
Steps:
(i) Create new vol without replication.
(ii) Perform clone operation; wait till completion (offline copy).
(iii) Create vol on secondary array.
Closes-Bug: #2021941
Change-Id: I1f025542a2509e36919ece01b29064377dbbe189
* Update cinder from branch 'master'
to d94ecc22c036d060c0a52bd5130281e244a769e5
- Update master for stable/2024.1
Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: I4311c34b40838da8ecc48802091908f08bf6f48f
* Update cinder from branch 'master'
to 1f87e459860e23afe3e54e6015bea9ef0046cf33
- Merge "Run protection tests during gate check"
- Run protection tests during gate check
This patch adds the cinder-tempest-plugin-protection-functional test to
the gate check. The test itself is defined in cinder-tempest-plugin.
This test enables Consistent and Secure Default RBAC (SRBAC) [1] on both
Keystone and Cinder to ensure that integration with Keystone and Cinder
functionality is working correctly when both services are enforcing
scope in RBAC.
Currently no other tests in the Cinder gate have this option enabled.
Moving forward, this job will help ensure that new changes to Cinder
will work in environments where SRBAC is enabled. This job will also
help as we continue to implement the next phases of the SRBAC community
goal.
[1] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rbac.html
Depends-On: https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/906153
Change-Id: I590eb954203ccd2fc564117addfcf5d2dac5bd74
* Update cinder from branch 'master'
to 08835cab080b57acba827adc6ae8a30fe2f525e6
- Merge "Dell EMC: PowerMax - Configurable SRDF snapshots"
- Dell EMC: PowerMax - Configurable SRDF snapshots
Add volume type extra spec boolean property
'powermax:disable_protected_snap'. Enabled when set to: `'<is> True'`,
`'True'`, `'true'`, or True, otherwise the property is disabled by
default.
When set to True, snapshot won't be replicated and won't
match the source volume type, it will be a regular device
no matter what.
If the property is not enabled in the volume type extra_specs, then
there is no change from the current behavior.
Implements blueprint powermax-protected-snap-config
Change-Id: Iafa44dcf0e8f46749b5ef37f0b8d341e8253a3bd
* Update cinder from branch 'master'
to baa7c33422dafa9bae1843528887b3d88deebeb1
- Merge "Dell EMC: Deprecate volume drivers for EOL products"
- Dell EMC: Deprecate volume drivers for EOL products
The following three volume drivers are no longer supported, because
the storage products are now EOL[1].
- Dell SC Series Storage Driver (iSCSI, FC)
- Dell VNX Storage Driver (FC, iSCSI)
- Dell XtremeIO Storage Driver (iSCSI, FC)
This change marks these drivers unsupported, so that we can remove
these drivers after 2024.1 release.
[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/7D7GUOI66BOD7Z3ZQWPWYYHH6VHAY4JJ/
Change-Id: I763278ec72adaf6f2ddd21edbfc687ca2f17f09a
* Update cinder from branch 'master'
to 8475859fcef91e2bb1dafb88b250cbfb75c79111
- Merge "reno: Update master for xena Unmaintained status"
- reno: Update master for xena Unmaintained status
The stable/xena branch has been deleted, so reno can't find its
release notes. Use the xena-eom tag to indicate the end of the
Cinder project's maintenance of the Xena series.
This strategy is what we used for the yoga transition, and was
discussed at a cinder weekly meeting:
https://meetings.opendev.org/irclogs/%23openstack-meeting-alt/%23openstack-meeting-alt.2024-02-07.log.html#t2024-02-07T14:06:09
Change-Id: Iafa97d17bd5684c4a43b08f4b1a8d2b580a2cfd1
* Update cinder from branch 'master'
to c6040dc3bc6592b8b930038eaf12601396266f58
- Merge "JovianDSS: Rework Open-E JovianDSS driver"
- JovianDSS: Rework Open-E JovianDSS driver
Provide major rework of Open-E JovianDSS driver that involves:
- improve performance of volume and snapshot creation and deletion
- remove revert to snapshot support
- improve storage net interface picking algorithm
Change-Id: Ifc2aa5d3622315ae5c70b2d8e809e1b1553684ea
Implements: blueprint open-e-joviandss-iscsi-rework
* Update cinder from branch 'master'
to c0ff458b051ba414ff8e08d92b6e4a613fef0735
- reno: Update master for Unmaintained branches
The stable/victoria and stable/wallaby branches have been deleted,
so reno can't find their release notes. Use the victoria-eom and
wallaby-eom tags to indicate the end of the
Cinder project's maintenance of these series.
Also fix our override for the reno closed_branch_tag_re to include
the -eom tags. Add the changed reno.yaml file to all relevant
irrelevant-files lists.
This strategy is what we used for the yoga transition, and was
discussed at a cinder weekly meeting:
https://meetings.opendev.org/irclogs/%23openstack-meeting-alt/%23openstack-meeting-alt.2024-02-07.log.html#t2024-02-07T14:06:09
Change-Id: I505b7cc12888d2373a0550b40bb945d75bb11067
* Update cinder from branch 'master'
to 0581e8cbd6b28724e75fc5b48c29c07e0d910fdb
- Merge "Remove six from HPE drivers"
- Remove six from HPE drivers
Change-Id: I34ab6eea48e7c05e9e3e7dcb11ef70b24f45ac56
* Update cinder from branch 'master'
to c7f2f613075e66b84d98a84fa4202f7cab0aa472
- Merge "[NetApp] LUN space allocation support"
- [NetApp] LUN space allocation support
Space allocation is an important NetApp driver specific feature.
This needs to be set when the cinder volume is created.
This is not related to thin/thick provisioning feature of cinder
volumes.It is independent of that. It enables ONTAP to reclaim
space automatically when host deletes data.This helps ONTAP
and host to see the actual space correctly when the host
deletes data.
It also helps to keep a LUN (cinder volume) online when the
LUN (cinder volume) in ontap runs out of space and containing
volume (in ONTAP) cannot automatically grow more space.
User can configure it by using volume type extra spec.
By default Space allocation value is disabled for ONTAP LUN
netapp:space_allocation: "<is> True" # to enable space allocation
netapp:space_allocation: "<is> False" # to disable space allocation
Blueprint: netapp-space-allocation-support
Change-Id: Ib7072f3093067ecd8ad84e396aaecec8f15c49ba
* Update cinder from branch 'master'
to 59a789dfe4026566b6ca75ab6c540ea1a63f6245
- Merge "Add Cinder active-active support for Dell PowerFlex driver"
- Add Cinder active-active support for Dell PowerFlex driver
Add Cinder active-active support for Dell PowerFlex driver.
Implements: blueprint dell-powerflex-aa
Change-Id: Ifde39110baff8f1365d6a68328a08353114ab763
* Update cinder from branch 'master'
to b5d08a53abad849dbaf09a16323e5f72f5913d7c
- Merge "Remove six from Nexenta drivers"
- Remove six from Nexenta drivers
Change-Id: I3290fd411da511f276d4f592820e9a88df958472
* Update cinder from branch 'master'
to a43cdaa85ca3ed00bf850e29dedb451a30316833
- Merge "[Pure Storage] Enable sync repl volume creation during failover"
- [Pure Storage] Enable sync repl volume creation during failover
Currently when cinder failover is invoked, due to the primary
storage backend being down, it is not possible, through the
driver, to create a new volume with sync replication
functionality. Non-replicated and async replicated volumes can
be created in this scenario - although not recommended due to
potential issues after failback.
A synchronously replicated volume could be safely created
during failover as the Pure Storage architecture can allow
this to happen. When the failed array is available again, any
new sync replication volumes created during the outage will be
automatically recovered by the backend's own internal systems.
This patch updates the driver to check, during volume creation,
if the backend is in failover mode and then allow sync volumes
to be correctly created, even though the primary array could be
inaccessible. Sync volume attachment will also be allowed to
continue should one of the backend replica pair arrays be down.
Creating different replication volume types have been tested
both failover and failback scenarios in Pure's labs and this
patch has proved to work as expected.
Additionally included is work from abandoned
change I7ed3ebd7fec389870edad0c1cc07ac553854dd8a, which
resolves replication issues in A/A deployments.
Also, fixes bug where a deleted replication pod can cause the
driver to fail on restart.
Closes-Bug: #2035404
Change-Id: I58f0f10b63431896e7532b16b561683cd242e9ee
* Update cinder from branch 'master'
to 20fe5b51f6aad2651b460dc43a48d743573ebd02
- Merge "Remove six from ProphetStor driver"
- Remove six from ProphetStor driver
Change-Id: Icd857fffc910139cf4d359447b5037847e93d4f5
* Update cinder from branch 'master'
to ba424aae9241551433f80c15555f815ba9c9d8ac
- Merge "Dell PowerFlex: Added timeout into rest API call."
- Dell PowerFlex: Added timeout into rest API call.
Added connect and read timeout into rest API call
of PowerFlex to avoid cinder hang issue.
Deafult value of connect and read timeout
is 30 seconds.
Closes-Bug: #2052995
Change-Id: I032d76627466f74121e3dc4fb2c8e175d830fa14
* Update cinder from branch 'master'
to b2a96e82fc0a78a0736467fc477d9c5cd4d0d4aa
- Merge "Dell PowerMax: Added timeout into rest API call."
- Dell PowerMax: Added timeout into rest API call.
Added connect and read timeout into rest API call
of PowerMax to avoid cinder hang issue.
Deafult value of connect and read timeout
is 30 seconds.
Closes-Bug: #2051830
Change-Id: I2d419b4257bae75c69577a34758910c4889e2507
* Update cinder from branch 'master'
to 2cb647584a78f069586ee0a70fb9d3b08e8550a9
- Merge "Fix error in cinder-manage quota sync cmd"
- Fix error in cinder-manage quota sync cmd
This fixes a regression introduced in [0] which changed a variable name
in some function definitions, but failed to change the matching variable
references.
Change some similar functions for consistency and to avoid overloading
imports with local variable names.
[0] https://review.opendev.org/c/openstack/cinder/+/842542
Related-Bug: 2047693
Change-Id: I153a73ad88762d5baa3f3c2c5c752e56280f7dc0
* Update cinder from branch 'master'
to 647fa0b10222c919dbeeeb19b761b5521fd01961
- Merge "Add the os-extend_volume_completion volume action"
- Add the os-extend_volume_completion volume action
Split off the finalization part of the volume manager's
extend_volume method and make it externally callable as the new
os-extend_volume_completion admin volume action.
This is the first part of a feature that will allow volume drivers
to rely on feedback from Nova when extending attached volumes,
allowing e.g. NFS-based drivers to support online extend.
See the linked blueprint for details.
Implements: bp extend-volume-completion-action
Change-Id: I4aaa5da1ad67a948102c498483de318bd245d86b
* Update cinder from branch 'master'
to 4eef9c0830b0a56e1fcdac39924a3420afc6f8bd
- Merge "Fix online data migration"
- Fix online data migration
The online migration remove_temporary_admin_metadata_data_migration
was recently merged and broke gate for the kolla project.
There are 2 issues with the current code:
1. The db api doesn't return the total and updated values
2. We are issuing a limit and update query together which is
not allowed generating the following error:
sqlalchemy.exc.InvalidRequestError: Can't call Query.update()
or Query.delete() when limit() has been called
This patch fixes the issue by creating a select subquery to get
all the ID values with the limit as max_count. We then create
a new query for update and pass the select subquery as a filter.
We don't require a releasenote since the bug and fix are in the
same release.
Closes-Bug: 2052805
Change-Id: Ida994f767eecb094c177db15dfc80a0c0fe56447
* Update cinder from branch 'master'
to a56d3976d66766519637ee344e43ad81675487e1
- Fix syntax in release note
An apostrophe was in place of a backtick, and as a result the
hyperlink to the LP bug didn't display as a hyperlink.
Change-Id: I42867de19c35255f275f47eb78062130f5756cab
* Update cinder from branch 'master'
to 47bf6af18c77adcc47161da396bd767e54578cab
- Merge "db: Set name for FK constraint"
- db: Set name for FK constraint
The name is present on the migrations. Set it on the models.
Change-Id: I9766dd02d3c97c419234b35cb4c45c21d6aab449
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update cinder from branch 'master'
to d3a80ad1347db2de9da1186f082202caa3356bff
- Merge "db: Remove erroneous primary key definitions"
- db: Remove erroneous primary key definitions
The migrations were not creating a composite primary key for the
'workers' table. Correct the model.
Strange that the migration auto-generation logic didn't pick this up.
Change-Id: Icf8a47248827de30bfa81279b63ffbc2b2a88331
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
* Update cinder from branch 'master'
to 0425c08f3d19ee0487c26bec499cf84e4538f519
- Merge "Hacking: Remove C306, C308 checks"
- Hacking: Remove C306, C308 checks
These block usage of methods that no longer
exist in oslo.utils 6.0.0+. Since they have
been removed, we don't need a hacking check
for this.
Change-Id: If0345c863b1750eaca3097f240fde9b976ac442e
* Update cinder from branch 'master'
to 105728c2ab072217dc16c3611e79b388aaab44a7
- Tests: Support jsonschema 4.21
This fixes unit test compatibility with
jsonschema 4.21 while maintaining compat
with jsonschema 3.2.
Change-Id: If9b8b4ccc805c8086c180e881b0ddd712289ad13
* Update cinder from branch 'master'
to 7245ec027b1902dc24c30cf3885a5dfec1866a6a
- Merge "Remove six from Infortrend driver"
- Remove six from Infortrend driver
Change-Id: I47b6e39eaa88e4ba5c47b7ccc973c8a7f43a178a
* Update cinder from branch 'master'
to a2bb77ab08fe0441bf072f9b55f76b05d3fe162d
- Merge "Remove six from VMWare drivers"
- Remove six from VMWare drivers
Change-Id: I26f1caebae29206442d75c8620a28517d42fc78f
* Update cinder from branch 'master'
to 0d82e610ab1bfdf3d071b6384b1163a84b11cd80
- Merge "Fix 'cinder-backup' service when Swift with TLS enabled"
- Fix 'cinder-backup' service when Swift with TLS enabled
The 'backup_swift_ca_cert_file' [1] setting is ignored by the Swift
backup driver so 'cinder-backup' service will appear "down" early on
startup when TLS backend used. This change fixes the issue.
1. https://docs.openstack.org/cinder/latest/configuration/block-storage/backup/swift-backup-driver.html
Closes-Bug: #2051985
Change-Id: Idec29ce596438a7969ea32d48bacfede84f5b0b6
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
* Update cinder from branch 'master'
to ad8c3cdfc880409b8dfe6b77de098a99e8b3094c
- Merge "Remove six from Veritas drivers"
- Remove six from Veritas drivers
Change-Id: I760653c3e08d6ba8b2c3b69720ca39697dedee83
* Update cinder from branch 'master'
to d3fa11028a0c152d6c4a8467057738608045bed2
- Merge "Remove six from SandStone driver"
- Remove six from SandStone driver
Trivial-Fix
Change-Id: I7d5e8d16f4b1babc191e9649c62a6638e7f2535e
* Update cinder from branch 'master'
to 31b90d75e1e33c662f510a93c18265933b226bb7
- Merge "Fix message confusion during backup restore"
- Fix message confusion during backup restore
This patch updates the message being logged after the flow manager
creates a volume from backup. When the flow manager called the driver
to try and do a backend assisted restore and the driver doesn't support
that, the log entry said it created the volume successfully. This was
incorrect as the volume wasn't finished. The raw volume was created,
but the data hadn't been copied into the volume yet. This is a
confusing message when trying to debug the process for failures in
production.
This patch updates the log message to only say successfull when the
driver assisted restore is implemented and worked.
Change-Id: I65d84f1e5566d7189ffd3315aeeef09c7cd73c68
* Update cinder from branch 'master'
to 015262b9540ff5a883ae4ba3a3062a646d885148
- Merge "Dell PowerFlex driver: update support matrix in doc"
- Dell PowerFlex driver: update support matrix in doc
Update the support matrix for Dell PowerFlex driver.
Change-Id: I3d0742f53a49cf8888329d0aeb034634c5fc4081
* Update cinder from branch 'master'
to 02b2d28305e800dccbc49c6bbb400592e91f4097
- Merge "Remove six from FusionStorage driver"
- Remove six from FusionStorage driver
Change-Id: Id231e4cab1d9994248375cb86f6fd06db9d777c5
* Update cinder from branch 'master'
to 4c4b51bb2fe6ecfa59ab5ae3e82f144da1c7f8f6
- Merge "Remove six from Inspur driver"
- Remove six from Inspur driver
Change-Id: I9e653ae7534bf4b9f7974ac6ff70e59aeb458b29
* Update cinder from branch 'master'
to fa19d4a8662b671c5c75e79b775d3b4417ab8695
- Merge "Remove six from test codes"
- Remove six from test codes
This removes six from some of the tests code. The other test codes will
be updated in per-driver changes.
Change-Id: Ib168d5831ce30793b22a33aec85b81103a4150a7
Zuul
OpenStack Release Bot