This patch addresses the scenario where an
incremental backup can be created having a
parent backup that was taken in a different
project. This scenario ultimately leads to
a silent error when creating/deleting the
incremental backup and quotas going out of
sync.
The proposed fix is to narrow the backup search
down to the same project. To achieve this, a
method's signature had to be updated to achieve
the desired optimized behavior of passing the
volume's project_id parameter.
Closes-bug: #1869746
Closes-bug: #1873518
Change-Id: Icb621ff5966133f59d9d43ca2dd9f8e1919b1149
(cherry picked from commit 8ebeafcbba)
This change addresses documentation updates required
for the Ussuri release.
Change-Id: I6602fbac143eb59c654010dd0e96af5ec066a112
Signed-off-by: Helen Walsh <helen.walsh@emc.com>
(cherry picked from commit e444ecf810)
Due to a characteristic on ONTAP devices, the volume extend
operation has a max resize size limited by underlying LUN's
geometry, so the support for extend online volumes was
disabled.
This patch fixes it by allowing a volume (attached or not)
to be extended up to 16TB, which is the max LUN size
supported by ONTAP.
NFS online_extend_support is still disabled due to a bug [0]
found on the generic implementation for NFS driver, which
ONTAP NFS driver relies on.
Closes-Bug: #1874134
[0] https://bugs.launchpad.net/cinder/+bug/1870367
Change-Id: I2812d71b23f27fe8be4e9a757094867f71b1afa2
(cherry picked from commit 510613e135)
After live migrating a volume into the 3PAR driver the volume would be
unusable. And we would no longer be able to do any operation with it.
Migrated in-use volumes cannot be renamed when migrated and therefore
need to use the "_name_id" field of the Volume object (volumes table in
the DB) to store the original volume's ID so the driver can locate the
volume.
The problem is that, even though the 3PAR driver sets the "_name_id"
field, it doesn't use it for any operation, so once the volume has been
migrated and the ID of the volume no longer matches the one that was
used to create the volume (value now in "_name_id") it will no longer be
able to locate the volume.
This patch adds the logic necessary to locate volumes using the
"_name_id" field.
Closes-Bug: #1697422
Change-Id: I27b9d4be419e1b52db02d4525b292ceeb5d5f867
(cherry picked from commit fc51678298)
VxFlex OS password is not stored in block_device_mapping table. Instead of this
passwords are stored in separate file and are retrieved during each attach/detach
operation.
Closes-Bug: #1823200
Change-Id: I99de0b618d4ead78f921fde296cee4c7484387dd
snapshot.id doesn't have `tmp-snap` in it as id
is not passed as a option while creating snapshot
object. This should be change to
`snapshot.display_name` at same location
Closes-Bug: #1875570
Change-Id: I66da0212a61d778fe9795d382b3af5b225a8aa54
(cherry picked from commit e52ab1a3ad)
Currently, if the iSCSI CIDR filter filters out some portals in
a synchronous replication setup, it only filters out the portals
but leaves the IQNs and LUNs, which can result in a mismatched
set of connection lists. This addresses the issue by filtering
earlier in the process, and only adding ones that pass the filter
in the first place.
Closes-Bug: #1877445
Change-Id: Idd4e21ff4efb63ad9ddf9d9bd5386bba103059ef
(cherry picked from commit 151db19b47)
Specialize the grenade-multinode job and test the variations
on upgrade where a few services are available on the subnode only
(c-bak only, c-bak+c-vol, c-bak+c-sch+c-vol).
Also, use grenade instead of grenade-py3. The former is now used
(after Iea355514ec7cc2a52ed5e88c356bcb1cdeadd639) in
integrated-gate-storage instead of the latter, which means
that we need to change it in order to apply the value of
irrelevant-files.
Depends-On: https://review.opendev.org/548936
Change-Id: I3eac1afcbb69e25e9b2a916910caf3291aa7c1fe
(cherry picked from commit 6c1e52cefc)
After migrating a volume, if the original and new volumes are on
the same 3PAR backend, then the volume names are swapped. However,
if the original volume is not in the same 3PAR backend, the new
volume is renamed to the original volume's name.
Closes-Bug: 1858119
Change-Id: I1f9d4143d1ad2637a2173090b290f6f96b64c492
(cherry picked from commit d8062063a3)
Adding missing force flag during live migration of instance
with more than one replication device in its masking view.
The removal of replication enabled devices from storage groups
is blocked in certain cases and an additional force option
is required in the REST payload.
Closes-Bug: 1875432
Change-Id: Ieae62e12df3be5018f716225abb65cdaa78379d1
(cherry picked from commit 50fc5e3988)
During U4P failover, if the initial operation that triggered the
failover hits an exception it can leave the failover lock in place.
Any operations waiting for lock to clear will continue to loop in place.
Added additional lock releases in exception catches and also a maximum
time that the holding operations should wait.
Change-Id: I43319854df9597df791a83cb4c598db0db3caec7
Closes-bug: 1875640
(cherry picked from commit 4351ace84f)
Concurrent live migrations can sometimes fail when one thread
deletes a storage group that another thread may need. Also
allowing for legacy short host name format in Live Migrations.
Change-Id: Iaacca9d6bce14995efa0347f84f918c175ac12cb
Closes-Bug: #1875478
(cherry picked from commit 03f5dce332)
This adds a warning message to the driver documentation page to make
sure it is visible that this config option should not be used due to
security concerns. We can't backport the deprecation of the config
option, but we can backport this doc warning to help prevent this option
from being used.
Related-bug: #1849624
Change-Id: Ief2c868d6a9baf6793cd9070a4451835a90752aa
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Cinder can successfully retype an attached volume from SolidFire
to different backends, but the other way around was failing. This patch
fixes this issue, allowing retype operation for attached volumes from
other backends to SolidFire.
Change-Id: I75b828198a2af707d59120f29704a81ba9f2b553
Closes-bug: #1859652
(cherry picked from commit ca475a3dad)
When the driver is trying to perform a flexclone from glance is
making a bad reference to a non-existent methond utils.resolve_hostname
the correct method is volume_utils.resolve_hostname
Change-Id: I5cd729bdd1fb97b07610b1971232c786bad7917d
Closes-Bug: #1875959
(cherry picked from commit 2da53ac02b)
Monkey patch the original current_thread to use the up-to-date _active
global variable. This solution is based on that documented at:
https://github.com/eventlet/eventlet/issues/592
Change-Id: Ida548b4bec00530418fd3d7ab254e971af77d3fe
Closes-Bug: #1863021
(cherry picked from commit 9f0aae5b58)
Updates the version description to be more accurate and the
release note to contain the bug ticket reference.
Partial-bug: #1703405
Change-Id: Ie1e2d635434f14adbc0b67c1ec2583842e1b4f6d
(cherry picked from commit 406e0778ec)
This addresses some minor issues in
I01039b7651a354761d034a9118b55b96cf32445e
Change-Id: I98dbc1f843a99405f12b6b9d1d189e27f5cdce6c
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
(cherry picked from commit 8819a1d6b4)
This patch adds the exisiting glance image colocation feature for
virtuozzo driver (which was restored recently).
Change-Id: I5278d97c98f44ca2f4dddf185cf108f72735d7b0
Closes-Bug: #1873463
(cherry picked from commit 89b86b650f)
This patch fixes pylint issues in both solidfire and test_solidfire
modules. New SolidFire patches shall succeed pylint checks.
Change-Id: I6695dbd0e0ae22cc4a820b3b6c179a13ace8a51a
(cherry picked from commit c91ef97096)
When detaching a volume from an instance, NetApp ONTAP driver terminates
the iSCSI connection, even if there're other connections to the LUN from
the same initiator. This terminates connections to the LUN from other
instances running on the same host.
This patch fixes this bug by leaving the connection untouched if there
are other connections from the same initiator. Now the connection is
terminated only if it's the last one from the same initiator.
Change-Id: I0b8b5930c9e8f3c049b82e92c5fb7b05d6ae9291
Closes-Bug: #1839384
(cherry picked from commit e27d83f4d0)
Change Ib27f9cd869078ff36e0230a18a18ba2d37d26820 indicates that
the MacroSAN driver is supported in Ussuri, so remove it from the
list of drivers marked 'unsupported' in Ussuri.
Change-Id: Icd8fbc8d7ed116720a042ce2a39d07bea9c14f57
This reverts commit 2a5cc4feff.
The 3rd Party CI is running. Therefore, the driver is being
marked supported in 'U' release.
Partially-implements: bp macrosan-driver-supported
Change-Id: Ib27f9cd869078ff36e0230a18a18ba2d37d26820
(cherry picked from commit 5075423026)
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.
Until the requirements repository has as stable/ussuri branch, tests will
continue to use the upper-constraints list on master.
Change-Id: I3df446698d65e5fe7800e3d9eaf5e8c1f3794101
Since XIV/A9000 are not supported yet, so remove XIV/A9000 part from
doc. also replace the picture with a new one without XIV/A9000 in it.
Change-Id: I928c7944981fbf166e907c9ae4038a08ccaa5c6e
Update typo and new storage name in release notes
Change DS8k to DS8000, Storize to Spectrum Virtualize
Family.
Change-Id: I3dcff5eaac34d1db12f80be42fde247cb58d7e75
Rodrigo Barbieri
OpenStack Release Bot