Description of problem:
After switching to RHEL 7.4 we see keepalived is unable to read IP address from config file to configure HA interface(though config file is properly configured).
Steps to reproduce:
1. Clone neutron
2. Install Keepalived v1.3.5 and run below functional test
neutron.tests.functional.sanity.test_sanity.SanityTestCaseRoot.test_keepalived_ipv6_support
This test will fail and you can see the errors in syslog.
Syslog failures:
Aug 22 19:52:01 vagrant6 Keepalived[14752]: Starting Keepalived v1.3.5 (03/19,2017), git commit v1.3.5-6-g6fa32f2
Aug 22 19:52:01 vagrant6 Keepalived[14752]: Unable to resolve default script username 'keepalived_script' - ignoring
Aug 22 19:52:01 vagrant6 Keepalived[14752]: Opening file '/tmp/tmpxxwEQH/tmpeVAVKR/router1/keepalived.conf'.
Aug 22 19:52:01 vagrant6 Keepalived[14753]: Starting VRRP child process, pid=14754
Aug 22 19:52:01 vagrant6 Keepalived_vrrp[14754]: Registering Kernel netlink reflector
Aug 22 19:52:01 vagrant6 Keepalived_vrrp[14754]: Registering Kernel netlink command channel
Aug 22 19:52:01 vagrant6 Keepalived_vrrp[14754]: Registering gratuitous ARP shared channel
Aug 22 19:52:01 vagrant6 Keepalived_vrrp[14754]: Opening file '/tmp/tmpxxwEQH/tmpeVAVKR/router1/keepalived.conf'.
Aug 22 19:52:01 vagrant6 Keepalived_vrrp[14754]: (VR_1): Cannot find an IP address to use for interface ha-c896a1c
Aug 22 19:52:02 vagrant6 Keepalived_vrrp[14754]: Stopped
Aug 22 19:52:02 vagrant6 Keepalived[14753]: Keepalived_vrrp exited with permanent error CONFIG. Terminating
Aug 22 19:52:02 vagrant6 Keepalived[14753]: Stopping
Aug 22 19:52:07 vagrant6 Keepalived[14753]: Stopped Keepalived v1.3.5 (03/19,2017), git commit v1.3.5-6-g6fa32f2
Version-Release number of selected component (if applicable):
How reproducible: 100%
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:3105