Comment 5 for bug 1630679

I looked into this again today and I think both Blake and I are wrong. What appears to be happening when you set the URL in the UI is the validation fails so the URL isn't changed. The error isn't surfaced and nothing changes the URL in the UI. As such it appears MAAS is working with a local path when its really using the old URL.

That being said I'm curious if using a local path ever did work. The BootSource model was introduced in MAAS 1.6, since then it has always used a URLField. The URLField is a django provided field which only allows URLs. As such it seems users were never able to set the URL to a filepath unless Django changed the validator.

So should we allow users to set the BootSource to a local file path? Does that make sense when MAAS is in HA mode?