Bug 1620235

Summary:	The local_ip for the OVS Agent on the Compute Nodes is being configured with the Control Plane IP versus the IP for the Tenant Network in Spine/Leaf deployment
Product:	Red Hat OpenStack	Reporter:	Darin Sorrentino <dsorrent>
Component:	python-tripleoclient	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Gurenko Alex <agurenko>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	13.0 (Queens)	CC:	amuller, bfournie, bhaley, dsneddon, dsorrent, hbrock, jpichon, jslagle, mburns
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-29 19:05:44 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 Darin Sorrentino 2018-08-22 18:50:24 UTC

Description of problem:

When deploying spine/leaf, each leaf is configured with it's own Tenant network with different L3.  When checking the OVS Agent config, the local_ip is being set to the provisioning IP of the Compute Node.

So we need to fix this and restart the agent each time we deploy.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Dan Sneddon 2018-08-27 20:35:26 UTC

(In reply to Darin Sorrentino from comment #0)
> Description of problem:
> 
> When deploying spine/leaf, each leaf is configured with it's own Tenant
> network with different L3.  When checking the OVS Agent config, the local_ip
> is being set to the provisioning IP of the Compute Node.

Sorry about this, we have a documentation gap. There is a BZ to improve the documentation for this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1599910

If you are deploying routed spine/leaf, where the compute node is on a different tenant network than the controllers, then you need to add extra data with hiera overrides for the role. The "neutron::agents::ml2::ovs::local_ip" value in particular. For instance, if you have one compute role using tenant1 and internal_api1, and another using tenant2 and internal_api2, then you would define the following:

parameter_defaults:
  ...
  Compute1ExtraConfig:
    "nova::vncproxy::host": "%{hiera('internal_api1')}"
    "neutron::agents::ml2::ovs::local_ip": "%{hiera('tenant1')}"
    "cold_migration_ssh_inbound_addr": "%{hiera('internal_api1')}",
    "live_migration_ssh_inbound_addr": "%{hiera('internal_api1')}",
    "nova::compute::libvirt::vncserver_listen": "%{hiera('internal_api1')}",
    "nova::compute::vncserver_proxyclient_address": "%{hiera('internal_api1')}",
    "nova::migration::libvirt::live_migration_inbound_addr": "%{hiera('internal_api1')}",
    "nova::my_ip": "%{hiera('internal_api1')}",
    "tripleo::profile::base::database::mysql::client::mysql_client_bind_address": "%{hiera('internal_api1')}"
  Compute2ExtraConfig:
    "nova::vncproxy::host": "%{hiera('internal_api2')}"
    "neutron::agents::ml2::ovs::local_ip": "%{hiera('tenant2')}"
    "cold_migration_ssh_inbound_addr": "%{hiera('internal_api2')}",
    "live_migration_ssh_inbound_addr": "%{hiera('internal_api2')}",
    "nova::compute::libvirt::vncserver_listen": "%{hiera('internal_api2')}",
    "nova::compute::vncserver_proxyclient_address": "%{hiera('internal_api2')}",
    "nova::migration::libvirt::live_migration_inbound_addr": "%{hiera('internal_api2')}",
    "nova::my_ip": "%{hiera('internal_api2')}",
    "tripleo::profile::base::database::mysql::client::mysql_client_bind_address": "%{hiera('internal_api2')}"

Comment 5 Bob Fournier 2018-08-29 19:05:44 UTC

Marking this as a dup of doc bug.

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