© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
This error happens while polling for events from the overcloud stack by tripleoclient.
I can reproduce this error pretty easily locally by deploying with an ssl undercloud with 6GB ram and 2 vcpus. If I don't enable swap, something gets OOM killed. If I do enable swap, swap gets used (< 1GB) and then I hit this error.
The stack keeps deploying but the client has been killed, so the job fails. My investigation so far has only pointed out that it's the swap allocation that is delaying things enough to cause the client to fail in this way.
We do not see this error in the ha job even though it deploys more nodes. As of now, my only suspect is that it's the overhead of the initial SSL connections causing the error.