This issue was fixed (unintentionally) in MAAS 1.9, but I confirmed that it still exists on MAAS 1.8.3.
This issue was fixed (unintentionally) in MAAS 1.9, but I confirmed that it still exists on MAAS 1.8.3.