Bug 2069624

Summary:	[RFE] Snapshot and Revert
Product:	Red Hat OpenStack	Reporter:	Juan Larriba <jlarriba>
Component:	tripleo-ansible	Assignee:	Juan Larriba <jlarriba>
Status:	CLOSED ERRATA	QA Contact:	myadla
Severity:	high	Docs Contact:
Priority:	high
Version:	17.1 (Wallaby)	CC:	astillma, ccamacho, fdiazbra, joabas, jpretori, kgilliga, mariel, mbracho, pgrist, skovili
Target Milestone:	beta	Keywords:	FutureFeature, Triaged
Target Release:	17.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tripleo-ansible-3.3.1-1.20221003151006.bc71476.el9ost python-tripleoclient-16.5.1-1.20221014070713.1d6a69d.el9ost	Doc Type:	Enhancement
Doc Text:	The Red Hat OpenStack Platform (RHOSP) snapshot and revert feature is based on the Logical Volume Manager (LVM) snapshot functionality and is intended to revert an unsuccessful upgrade or update. Snapshots preserve the original disk state of your RHOSP cluster before performing an upgrade or an update. You can then remove or revert the snapshots depending on the results. If an upgrade completed successfully and you do not need the snapshots anymore, remove them from your nodes. If an upgrade fails, you can revert the snapshots, assess any errors, and start the upgrade procedure again. A revert leaves the disks of all the nodes exactly as they were when the snapshot was taken.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-16 01:11:06 UTC	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:
Bug Depends On:	2066349
Bug Blocks:

Description Juan Larriba 2022-03-29 09:41:06 UTC

From an upgrades perspective, we only need a short-lived snapshot taken in the same machine to be able to revert to the previous state if everything goes wrong.

The most important requirement in this context is that the snapshot and the revert are very fast, but other requirements that belong to the Disaster Recovery domain such as storing the backup remotely, being able to consistently recover from a full hardware failure or the ability to program recurrent backups add a lot of time to the backup process without adding significative advantage to the upgrade process.

In this regard, we want to implement a new feature that creates quick local snapshots before an upgrade using the LVM snapshot feature.

Comment 5 Sree 2023-04-12 18:32:05 UTC

Verified by QA

Comment 11 Fernando Díaz 2023-05-29 08:25:33 UTC

Thanks for the clarification! I've added the doc in the related field.

Comment 14 Juan Larriba 2023-06-08 09:10:08 UTC

Im not working on this team anymore. Adding ccamacho.

Comment 21 errata-xmlrpc 2023-08-16 01:11:06 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:4577

Comment 22 Red Hat Bugzilla 2023-12-15 04:25:19 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days