Comment 2 for bug 1700150

Log entries like

Jun 23 18:31:48 localhost container-server: 172.16.3.8 - - [23/Jun/2017:18:31:48 +0000] "HEAD /d1/253/AUTH_8943125e619d485c87965261f5704d4e/incoming128-0" 204 - "HEAD http://10.0.0.5:13808/v1/AUTH_8943125e619d485c87965261f5704d4e/incoming128-0" "tx5cce2b4d87ca442697823-00594d5e14" "proxy-server 29899" 0.0020 "-" 30317 0

make me think this may be an SSL misconfiguration. There shouldn't be an http request going to 13808, which is the SSL port.

That being said, my guess would be that the rabbit failure is happening because Swift is trying to send an error notification about the bad request. Whether that's failing because of the SSL misconfiguration or because there's legitimately a problem I can't really say. I think we need more details about how this environment was deployed and what was going on to cause these bogus calls to Swift. I don't see similar errors in CI so it's not a general problem with Swift.