Comment 8 for bug 1837927
Revision history for this message
| Orestes Leal Rodriguez (orestesleal) wrote | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi Guys,
I've fixed the issue, you all were correct, the problem was on the OpenStack side.
The problem was with the MTU (a device in the middle of those link don't allow >1500 MTU, we use jumbo frames.
But I have a question. Why xenial worked, did it transfer the metadata in chunks (therefore each part (json payload+protocol overhead) totals <1500 bytes)? because even with the MTU 9000 and the device discarding jumbo frames in the middle cloud-init on xenial worked (yes, with the EC2 datasource).
I would appreciate an insight of how that cloud init version works in this sense.