Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
4.8.0
-
None
-
Security Level: Public (Anyone can view this level - this is the default.)
-
None
-
CentOS Linux 6, CentOS Linux 7, Ubuntu LTS 14.04
Description
When using a custom network offering in a redundant router setup, the password server does not bind to an IP or port and therefore that network is unable to serve passwords.
Upon verification on the routers (both on MASTER and BACKUP) the password service script is invoked with:
/bin/bash /opt/cloud/bin/passwd_server_ip None dummy
instead of
/bin/bash /opt/cloud/bin/passwd_server_ip <PRIVATE_IP> dummy
When manually killing and restarting the password script with the correct IP address it works without problems.
The issue seems to be related to getting the right configuration set up on the router(s) when using a custom network offering.