35f30a61b1
Steps to reproduce:
* Define a separate network for the external API network
* Don't define a cidr field for the new network (prevents IPs being
allocated to hosts on this network)
* Set the vip_address field for the network (and optionally fqdn)
* kayobe overcloud host configure
* kayobe overcloud service deploy
* kayobe overcloud host configure (again)
On the final command, keepalived will have created a VIP on the
interface, causing the command to fail with an error like the following:
Interface eth0 has an IPv4 address but none was requested
This change fixes the issue by passing the VIP address as an allowed
address to the MichaelRigart.interfaces role. This depends on
https://github.com/michaelrigart/ansible-role-interfaces/pull/71.
Change-Id: Ic86c0ca1b8209c968cb20a11bb3f40da71f296d0
Story: 2007736
Task: 39902
9 lines
336 B
YAML
9 lines
336 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes an issue when configuring the external API network interface on
|
|
controllers without an IP address which would cause ``kayobe overcloud host
|
|
configure`` to fail on a host with an active virtual IP address. See
|
|
`story 2007736 <https://storyboard.openstack.org/#!/story/2007736>`__ for
|
|
details.
|