Prechecks fails when using multinode deploy using a single node and haproxy disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Fix Released
|
High
|
Hiroki Ito | ||
Liberty |
Fix Released
|
High
|
Hiroki Ito | ||
Mitaka |
Fix Released
|
High
|
Hiroki Ito |
Bug Description
When using deploy with a single node, it is needed change the var kolla_internal_
And in this case, the prechecks process will fail, because this Ip address is in use.
Steps to reproduce
1 - Choose stable/mitaka branch and use the inventory as follow
=======
# These initial groups are the only groups required to be modified. The
# additional groups are for more control of the environment.
[control]
# These hostname must be resolvable from your deployment host
192.168.201.2
#192.168.201.3
#192.168.201.4
# The above can also be specified as follows:
#control[01:03] ansible_
# The network nodes are where your l3-agent and loadbalancers will run
# This can be the same as a host in the control group
[network]
192.168.201.2
#192.168.201.3
#192.168.201.4
[compute]
192.168.201.2
#192.168.201.3
#192.168.201.4
...
...
=======
2 - Change it in /etc/kolla/
kolla_internal_
enable_haproxy: "no"
3 - Run the prechecks: # ./tools/
The error logs generated
+++++++
TASK: [prechecks | Checking if kolla_internal_
failed: [192.168.201.2] => (item=192.
stdout: PING 192.168.201.2 (192.168.201.2) 56(84) bytes of data.
64 bytes from 192.168.201.2: icmp_seq=1 ttl=64 time=16.0 ms
64 bytes from 192.168.201.2: icmp_seq=2 ttl=64 time=0.188 ms
64 bytes from 192.168.201.2: icmp_seq=3 ttl=64 time=0.095 ms
--- 192.168.201.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.095/5.
failed: [192.168.201.2] => (item=192.
stdout: PING 192.168.201.2 (192.168.201.2) 56(84) bytes of data.
64 bytes from 192.168.201.2: icmp_seq=1 ttl=64 time=0.049 ms
64 bytes from 192.168.201.2: icmp_seq=2 ttl=64 time=0.104 ms
64 bytes from 192.168.201.2: icmp_seq=3 ttl=64 time=0.055 ms
--- 192.168.201.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.049/0.
FATAL: all hosts have already failed -- aborting
PLAY RECAP *******
to retry, use: --limit @/root/
192.168.201.2 : ok=52 changed=0 unreachable=0 failed=1
Changed in kolla: | |
importance: | Medium → High |
Changed in kolla: | |
milestone: | newton-1 → newton-2 |
Changed in kolla: | |
milestone: | newton-2 → newton-3 |
Changed in kolla: | |
assignee: | nobody → Hiroki Ito (hrito) |
haproxy disabled is not really a mode we want to promote. If we fix in master, I'd be ok with that (and release in stable/newton), but I am hesitant to bring this mode of operation into stable/mitaka unless the patch is super simple. Lets see an implementation before making a decision. 2.0.1 is always an option as well as long sa this isn't a feature.