Overriding hypervisor name for resource provider always requires a complete list of interfaces/bridges

Bug #1905276 reported by Takashi Kajinami
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Invalid
Wishlist
Unassigned

Bug Description

In some deployments, hostnames can be different between hosts and resource provider records. For example in deployment managed by TripleO we use short host name (without domain name) in host, while we use FQDN for resource provider records (this comes from the FQDN set to the host
option in nova.conf).

This causes an issue with the way how currently neutron looks up the root resource provider because placment API requires the exact hostname and doesn't automatically translate short name and FQDN.

To fix the issue we need to set the resource_provider_hypervisors option[1] now but it is very redundant to list up all devices or bridges in this option to override hostnames for the devices/bridges by the same value.

[1] https://review.opendev.org/#/c/696600/

summary: - Overriding defualt hypervisor name always requires a complete list of
- interfaces/bridges
+ Overriding hypervisor name for resource provider management always
+ requires a complete list of interfaces/bridges
summary: - Overriding hypervisor name for resource provider management always
- requires a complete list of interfaces/bridges
+ Overriding hypervisor name for resource provider always requires a
+ complete list of interfaces/bridges
Changed in neutron:
importance: Undecided → Low
status: New → Confirmed
importance: Low → Wishlist
Revision history for this message
Lajos Katona (lajos-katona) wrote :
Revision history for this message
Takashi Kajinami (kajinamit) wrote :

Closing this because our expectation here is that neutron and libvirt should detect the same hostname.
I've reported another bug to fix current incompatibility.

 https://bugs.launchpad.net/neutron/+bug/1926693

Changed in neutron:
status: Confirmed → Invalid
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.