Bug 2229750

Summary:	Cross-AZ backup creation is broken
Product:	Red Hat OpenStack	Reporter:	Alan Bishop <abishop>
Component:	openstack-cinder	Assignee:	Brian Rosmaita <brian.rosmaita>
Status:	CLOSED ERRATA	QA Contact:	Yosi Ben Shimon <ybenshim>
Severity:	medium	Docs Contact:	Ian Frangs <ifrangs>
Priority:	medium
Version:	17.0 (Wallaby)	CC:	brian.rosmaita, eharney, ifrangs, jelynch, lsvaty, mariel, pgrist
Target Milestone:	z1	Keywords:	Regression, Triaged
Target Release:	17.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-cinder-18.2.2-1.20230518161044.el9ost	Doc Type:	Bug Fix
Doc Text:	Before this update, when specifying an availability zone (AZ) when creating a Block Storage volume backup, the AZ was ignored, which could cause the backup to fail. With this update, the Block Storage backup service resolves this issue.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-20 00:29:52 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:
Bug Blocks:	1905097

Description Alan Bishop 2023-08-07 14:26:48 UTC

Description of problem:

The cinder-backup service is no longer able to back up a volume in a different AZ. 

How reproducible:

Always

Steps to Reproduce:
1. Prepare a deployment with a cinder-volume service in one AZ, and the backup service in a different AZ.
2. Create a volume
3. Create a cross-AZ backup of that volume

Actual results:

The backup fails, with an error message in the cinder-scheduler log:

2023-08-07 12:52:34.964 2 ERROR cinder.scheduler.manager [req-08d6c888-8ee0-4d95-92ab-735bb723b790 256db7de35ee451b946003930aef5c99 262b573d07f2425ba7eb3718825e5893 - - -] Service not found for creating backup.: cinder.exception.ServiceNotFound: Service cinder-backup could not be found.

Expected results:

The backup succeeds.

Additional info:

The issue was reported upstream a while ago, and there's a patch proposed to fix it. The patch needs to be updated (it's in merge-conflict).

Comment 1 Brian Rosmaita 2023-08-08 14:00:18 UTC

Regression was introduced in upstream ussuri by change Ie2afb57c4861c4, so this should not need to go to train.

Comment 20 errata-xmlrpc 2023-09-20 00:29:52 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.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/RHBA-2023:5138