Info of the compute service name in module cinder.compute.nova is not synchronized with the one in Keystone's config file

Bug #1414873 reported by Trung Trinh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Won't Fix
Undecided
Unassigned

Bug Description

Version: stable/juno

Description:
In the module cinder.compute.nova, the info of the compute service name is not synchronized with the one in Keystone's config file.

In fact, the compute service name can be pre-defined in Keystone's config file "/etc/keystone/default_catalog.templates" at the section "catalog.RegionOne.compute.name" but this pre-defined info is not taken into account by Cinder. In particular, the module "cinder.compute.nova" always uses its own default info which is defined in config option (nova_catalog_info and
nova_catalog_admin_info).

It can happen that Keystone's config file pre-defines a different name from the default name assumed by Cinder.

Proposal:
Synchronize the info of the compute service name between Keystone's config file and Cinder module

Tags: cinder
Changed in cinder:
assignee: nobody → Trung Trinh (trung-t-trinh)
status: New → In Progress
Revision history for this message
Sean McGinnis (sean-mcginnis) wrote :

Automatically unassigning due to inactivity.

Changed in cinder:
assignee: Trung Trinh (trung-t-trinh) → nobody
status: In Progress → Triaged
Changed in cinder:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.