Public bug reported:
The metadata server listens on 169.254.269.254 but not on any ipv6
address. Thus v6-only machines must be configured with a config-drive.
(There is no v6 address assigned to metadata, but it could easily listen
on the v4-in-v6 address ::169.254.169.254 in the same way.)
**
Seems to me that the issue is not that the MTU isn't being honoured, but
that the MTU should be checked *before* TSO assembly and not *after*.
Assembly should happen outside the VM if the VM has enabled it on the
interface internally, and clearly the incoming segments (not packets, at
this point) m
I was testing with devstack, and the latest Folsom of the moment. If
it's not turning up in either case at the moment then apparently it's
gone away - I'll reopen with more detail if I see it again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is su
