Canonical Juju

  1. Bug #1733944
  2. Comment #4

Comment 4 for bug 1733944

Revision history for this message
Ante Karamatić (ivoks) wrote :

So, problem is that MTU on physical machine was not matched with an MTU on LXD. Juju has view of both of these, the physical machine's MTU and MTU for LXD. In fact, it configures LXD itself.

I'm not sure how useful is for a tool to tell me it did something wrong. So, better behaviour would be to set MTU correctly or exit as soon as possible. It shouldn't deploy a machine with a broken MTU, particulary because it knows its broken.

Does that make sense?