Feature Request Overview
Develop a backup & restore procedure for the relevant OVN and OVS data so that it is possible to roll-back to a known working state if an in-place update fails during the OVN part of the update.

Business justification

During the course of an in-place update or upgrade of RHOSO, it is possible that something may go wrong during the parts where OVN or OVS get updated/upgraded.

It is fairly often that there are schema updates done for OVN during these updates/upgrades and it is also possible that there may be an OVS schema upgrade that happens.

When schema changes happen, a simple roll-back of the container & configuration is not enough to revert the environment to a known working state - there needs to be some sort of backup & restore process.

Part of any change management process is the ability to roll-back from a failed change. Having this available empowers the customer to revert to a working state and figure out what went wrong without impact to the business.

Functional requirements /Acceptance Criteria

• A procedure for backing up the relevant data
• A procedure for using the backup to revert to a working state

Describe the customer impact

IMPORTANT: Do not include customer names.

• Provide links to the account project
• Provide links to any related support tickets (open or closed)

For details on connecting Jira issues to an account, see Connecting Jira Issues to Accounts.

(Optional) Point of contact

• Provide any additional points of contact for this feature request, such as an account executive, SA, or TAM: 
•  

(Optional) Additional links

Click More > Link to add any links to issues, such as an outcome, that are related to this feature request.