the failure occurs while trying to connect to a worker VM to start a fake web server with netcat.
This time the connection happens over the private IP, so the l3 agent does not get into the picture. The port appears to be correctly wired in all analyzed failures. Therefore we need to look at potentiall sec group/dhcp issues.
79 of the 93 failures observed in the last 24 hours happen in the newly merged load balacing scenario: http:// logstash. openstack. org/#eyJmaWVsZH MiOltdLCJzZWFyY 2giOiJmaWxlbmFt ZTpcImNvbnNvbGU uaHRtbFwiIEFORC BtZXNzYWdlOlwid GVtcGVzdC5zY2Vu YXJpby50ZXN0X2x vYWRfYmFsYW5jZX JfYmFzaWMuVGVzd ExvYWRCYWxhbmNl ckJhc2ljLnRlc3R fbG9hZF9iYWxhbm Nlcl9iYXNpY1tjb 21wdXRlLGdhdGUs bmV0d29yayxzbW9 rZV0gLi4uIEZBSU xcIiIsInRpbWVmc mFtZSI6Ijg2NDAw IiwiZ3JhcGhtb2R lIjoiY291bnQiLC JvZmZzZXQiOjAsI nRpbWUiOnsidXNl cl9pbnRlcnZhbCI 6MH0sInN0YW1wIj oxMzkxNzcxNDg5M zc0fQ==
the failure occurs while trying to connect to a worker VM to start a fake web server with netcat.
This time the connection happens over the private IP, so the l3 agent does not get into the picture. The port appears to be correctly wired in all analyzed failures. Therefore we need to look at potentiall sec group/dhcp issues.