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
Instead of our custom tox-py311 job, use the openstack-wide job
that was added by change I725b94bee6601a and added to the testing
template by I3b22ff95ab7b83a.
Since the openstack-tox-py311 job uses a debian bookworm nodeset,
follow change I736ecb2a18d3 in adjusting cinder's bindep.txt.
Change-Id: I3b22ff95ab7b83ae6e0e12f0d2bf645cc87424d2
A previous patch incorrectly removed a call using a specific
version of API as part of the replication failover process.
The call being made to the backend fails as one of the
parameters is not supported in later API version.
This patch fixes the call to the backend to use the required
API version.
There are no tempest tests for replication failover, hence
why the original patch passed tests.
Closes-Bug: #2028380
Change-Id: Id4f5f16a04220cc880e17ffd69a8303c93a6e8ba
A bullet list shouldn't be indented in rST and doing so causes it to be
rendered inside a blockquote, which is not what we want.
In addition, indicating versions as vXXX is more prevalent than VXXX so
correct this.
Change-Id: I3ea8e0a8ae58d5b7da9aae85b41162b2458020d5
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Added support of FC to Tatlin Unified driver
Implements: blueprint yadro-tatlin-unified-fc
Co-Authored-By: Sergey Karpenkov <s.karpenkov@yadro.com>
Change-Id: Ia8192854a7095354f2616d53d2c5b71580384dcb
This patch adds the following tests:
1) List backup with details
2) Show backup
3) Update backup
Partially-Implements: blueprint generating-sample-files
Change-Id: I9bbfab93fb138932243d880e440c9524b5f08217
Unfortunately, the commit b75c29c7d8e0e6ac212b59f9ad8d140874e55251
did not update all the places where BackupAPI.restore_backup()
was called. One of them was in the flow manager.
Although this regression being undetected in is disappointing,
we are not changing how unit tests are performed in any
fundamental way for this patch. An outstanding patch using
MyPy is aready in review, which would capture this case.
Closes-bug: #2025277
Related-Change-Id: I54b81a568a01af44e3f74bcac55e823cdae9bfbf
Change-Id: Iabfebacfea44916f89584ffd019d848e53302eaf
Add the "maximum" marker for Zed and 2023.1 at mv 3.70, which was
introduced by change I459f06504e90.
Change-Id: I7a7e45a99e0c7ec59f4e2ef7e98c9710c4cd37a1
This patch adds the following tests:
1) Volume transfer for microversions 3.55 and above
Partially-Implements: blueprint generating-sample-files
Signed-off-by: Desire Barine <desirebarine16@gmail.com>
Change-Id: Ifdd99433563ab72d8d43a374af0377213834d46e
The current implementation of the `_full_restore` method in the Ceph
backup driver is causing restoration to fail when restoring to another
volume type. This is because the method generates an incorrect image
name in the Ceph pool, resulting in the error message:
```
rbd.ImageNotFound: [errno 2] error opening image
b'volume-a91c11af-1147-4ac7-a5ce-61676736e076.backup.base' at snapshot
None.
```
Originally, the format `volume-<vol-uuid>.backup-<backup-uuid>` was used
for every backup created on the Ceph pool. However, after the change introduced in commit Ia08c252d747148e624f8d9e8b0e43f94773421e0, the
base name format was altered to volume-<uuid>.backup.base when
creating backups from Cinder snapshots.
This patch modifies the current if statement in _full_restore() to check
for the presence of a snapshot_id attribute in the backup. If the
attribute exists, the old base name format is used; otherwise, the new
format is applied. The if block statement in _full_restore() should now
match the format generated by the _full_backup() method.
Additionally, src_snap is activated when the destination volume is RBD
or if the backup is incremental. Currently, the Ceph backup driver only
supports incremental RBD backups, so incremental backups from non-RBD
volumes are not permitted.
NOTE: This patch primarily mirrors the modifications in
Ia08c252d747148e624f8d9e8b0e43f94773421e0, addressing it as a partial
bug fix. There's a consequential patch that further strengthens the
backup restore operations, which should be considered to fully resolve the bug. These two should be squashed and backported together for
optimal implementation.
Partial-Bug: #1895035
Change-Id: Iff8e1e90ab3c7b519819577ec3aafff838e6934f
The replication needs to map the origin cluster aggregates to destination.
The origin is got from the provisioning options that contains the aggregate
as a list for FlexGroup pool and a string for FlexVol pool. This patch
fixes the create operation by adding that aggregate condition check.
Change-Id: Ia0af0777eeae18cfabefb5df4fdeb562382c2299
Closes-Bug: #1927784
In the code hpe_3par_iscsi.py, only the trunk ips
(192.168.68.203) are considered. If vlan ips (192.168.100.1)
are specified, they aren't considered while forming list of
iscsi ips.
Sample output of "showport" command from HPE 3par storage system:
CSSOS-SSA04 cli% showport -iscsivlans
N:S:P VLAN IPAddr Netmask
0:2:1 - 192.168.68.203 255.255.192.0
0:2:1 100 192.168.100.1 255.255.192.0
0:2:1 200 192.168.100.2 255.255.255.0
Kindly refer launchpad bug for details.
This patch adds support for using vlan iscsi ips.
Closes-Bug: #2015034
Change-Id: Idaea18411ae03c5a9696b2ab67e84087177fcc74
