Bug 1899160

Summary: cinder-backup service is configured to use specific controller's hostnames instead of "hostgroup" like cinder-volume
Product: Red Hat OpenStack Reporter: Alex Stupnikov <astupnik>
Component: openstack-cinderAssignee: Cinder Bugs List <cinder-bugs>
Status: CLOSED DUPLICATE QA Contact: Tzach Shefi <tshefi>
Severity: medium Docs Contact: Chuck Copello <ccopello>
Priority: unspecified    
Version: 13.0 (Queens)CC: abishop
Target Milestone: ---   
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: 2020-11-18 17:14:08 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:

Description Alex Stupnikov 2020-11-18 16:08:27 UTC 
Description of problem:

Cinder-volume and cinder-backup are both controlled by Pacemaker and both services are always running on single controller node (there is single instance of each service). For cinder-volume backends we generally set "backend_host=hostgroup" and we get consistent picture of "openstack volume service list": despite migrations there is a single instance of cinder-volume service per backend, which is up.

Situation is different for cinder-backup: due to the way cinder works or the way TripleO provisions it (I haven't isolated the root cause), a dedicated cinder-backup service is created for every controller node. As a result, there is cinder-backup service in down state when cinder-backup service is migrated from one controller node to another.

I am reporting this bug to ask engineering to check if this cosmetic issue could be resolved, or there is no way to change current behavior.
Comment 1 Alan Bishop 2020-11-18 17:14:08 UTC 
Sorry, at least for now "that's the way it works."

cinder-volume supports the notion of a backend_host, but the cinder-backup service doesn't have backends (only drivers).

But see bug #1666804, which is intended to address this situation, and bug #1665191 for more background.

*** This bug has been marked as a duplicate of bug 1665191 ***