** Description changed:

  Summary
  -------
  The Infinidat snapshot-promotion change makes InfiniSDK >= 250.0.0
  mandatory during driver setup. This rejects previously supported SDK
  versions, including 220.0.0, even though the existing generic data-copy
  implementation remains available.
  
  This report covers only the backward-compatibility regression and its fix,
  not the addition of snapshot promotion itself.
  
  Affected code
  -------------
  The regression is introduced by snapshot-promotion commit:
  4202c9c20e12572ab7ff7f7c38bbae5ffe63e045
  Change-Id: I361102149d9c39060347d01bfa276b7073fd15fb
  
  It applies to trees containing that change without the compatibility fix;
  this report does not assert that an unmodified Ubuntu noble/2024.1 package
  already contains the regression. Noble/2024.1 is the intended backport
  target.
  
  Steps to reproduce
  ------------------
  1. Use a Cinder tree containing the snapshot-promotion change above.
  2. Configure an Infinidat backend and install a previously supported
-    InfiniSDK version below 250.0.0, for example 220.0.0.
+    InfiniSDK version below 250.0.0, for example 220.0.0.
  3. Start cinder-volume and allow the Infinidat driver to run do_setup().
  
  Actual result
  -------------
  Driver setup raises VolumeDriverException because the installed SDK is
  older than 250.0.0, preventing initialization of the backend.
  
  Expected result
  ---------------
  The backend initializes with previously supported SDK versions. Snapshot
  promotion is enabled only when both InfiniSDK >= 250.0.0 and the storage
  system support it. Otherwise, volume cloning and volume creation from
  snapshots continue to use generic data copy, with a startup warning
  explaining why promotion is unavailable.
  
  Older SDKs must not be asked to call has_promote_snapshot(), which they
  may not provide.
  
  Proposed fix
  ------------
  e0823c0de3134bb437df6c3db06ff2b92ffec685
  Change-Id: I727f0d38c3641e5aace38e8084060467a4738cbf
  Title: Infinidat: preserve compatibility with older InfiniSDK
  
  Use 250.0.0 as the minimum for snapshot promotion only, cache the combined
  SDK/storage capability at setup, and use it for both clone paths. Restore
  the dependency minimum to 103.0.1 and update the driver documentation and
  release note.
  
  Validation plan
  ---------------
  Run the Infinidat unit tests, including the SDK/storage capability matrix
  and both data-copy fallback paths added by the proposed fix. Check that
  older SDKs initialize without accessing the newer capability method, that
  the appropriate startup warnings are emitted, and that promotion remains
  enabled only with a sufficiently recent SDK and capable storage.
  
  On a configured backend, repeat initialization and both clone operations
  with an older SDK, then with SDK >= 250.0.0 and capable storage. Verify that
  the resulting volumes are usable and their data matches the source.
  
  This is an upstream bug report, not an approved Ubuntu SRU.
+ 
+ 
+ ------------
+ 
+ [Impact]
+ 
+ The Infinidat snapshot-promotion feature backport (LP: #2174690,
+ upstream gerrit 940236) makes InfiniSDK >= 250.0.0 a hard requirement at
+ cinder-volume driver initialization. Deployments using InfiniSDK
+ versions that were previously supported (e.g. 220.0.0, with the
+ packaging dependency minimum at 103.0.1) would fail Infinidat backend
+ setup entirely and lose the backend, even if they never use snapshot
+ promotion.
+ 
+ [Test Plan]
+ 
+  * Use a Cinder deployment with an Infinidat backend on an array and an 
InfiniSDK version older than 250.0.0 that was previously supported (e.g. 
220.0.0; the packaging dependency minimum is 103.0.1). Record the installed 
Cinder and InfiniSDK versions and the array's InfuzeOS version. Create a source 
volume of a volume type mapped to that backend, attach it, write a recognizable 
data pattern, verify it can be read, and take a snapshot.
+  * Install the proposed package and restart cinder-volume. Confirm the 
backend initializes with the older SDK (no InfiniSDK-version startup failure) 
and that the driver logs why snapshot promotion is not used.
+  * Create (a) a volume from the source volume and (b) a volume from its 
snapshot. Confirm both succeed via the driver's generic data-copy path (backend 
operation traces or Cinder logs), that both resulting volumes are available and 
contain the source pattern, and that deleting the source or its snapshot does 
not make them unusable.
+ ( Since the SRU MR is submitted with both LP#2174690 and LP#2171540), the 
verification will not be about reproducing the breakage but about ensuring there
+ is no breakage)
+ 
+ [Where problems could occur]
+ 
+ - Driver startup: the combined SDK-version/storage-capability check is cached 
at setup; if it mis-detects, an older SDK could be asked for the newer 
capability method, or promotion could be attempted on incapable storage, 
leaving an incomplete clone or a backend that fails to initialize. Covered by 
the unit matrix above.
+ - Fallback correctness: both create-from-snapshot and clone-from-volume must 
keep working via generic data copy on older SDKs; a broken fallback would turn 
this into a functional regression rather than the intended 
no-change-for-old-SDKs behavior.
+ - Warning noise at startup on every older-SDK deployment (informational only).
+ - Blast radius is the Infinidat driver only; for non-Infinidat deployments 
the only reachable surface is module import at cinder-volume startup, verified 
above.
+ 
+ [Other information]
+ * Both LP#2174690 and LP#2171540 (this bug) are submitted in a single SRU 
since
+ this bug is a regression of LP#2174690
+ * In the absence of hardware, we can run only tempest test cases and ensure 
nothing is broken

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2171540

Title:
  Infinidat: snapshot promotion rejects previously supported InfiniSDK
  versions

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/2171540/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to