Comment 6 for bug 1818682
Revision history for this message
| Marcus Klein (kleini76) wrote Re: HAproxy for metadata refuses connection from VM cloud-init | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
There are already some VMs running in that network connected to the according L3 router. I see haproxy happily running. After launching a new VM, haproxy has a different PID. The same happens, when a VM is destroyed.
root@network2:~# while (true); do ps afx | grep 48d5 | grep haproxy | wc -l; sleep 0.5; done
1
1
0
0
0
0
0
0
0
1
1
That means, that at least there is no haproxy listening for 3.5 seconds. Nova tells me, that launching a VM takes sometimes only 5 seconds. So it might happen, that the VM already runs cloud-init while haproxy is not running within the L3 router network namespace. eeks!
Are there any possible solutions for that?