Bug 1987054

Summary: [TestOnly] Verify accessible upgrades with manila
Product: Red Hat OpenStack Reporter: Goutham Pacha Ravi <gouthamr>
Component: python-manila-tests-tempestAssignee: lkuchlan <lkuchlan>
Status: NEW --- QA Contact: lkuchlan <lkuchlan>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)CC: vhariria, vimartin
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Goutham Pacha Ravi 2021-07-28 19:59:35 UTC 
Description of problem:

OpenStack consumers perform updates and upgrades all the time; we want to ensure that while performing a routine update or a major upgrade, or fast forward upgrade, resources provisioned on manila, and in-use do not suffer any disruptions while the manila control plane is being updated. 

A sample scenario would be:
*) Prior to update/upgrade/FFWD:
 1) a manila share is created
 2) access is accorded to a client user/VM/Container/Baremetal 
 3) the share is mounted by the client, and data is read/written
*) During the update/upgrade/FFWD:
 4) the client workload continues to work, even if the manila control plane is unavailable
*) After the update/upgrade/FFWD:
 5) the client workload continues to work. Since the management path is now available, operations such as access control, snapshotting, cloning (creating a new share from the snapshot) etc should be possible again. 


This TestOnly RFE is to capture the testing necessary to ensure this accessibility.