Commit errors on USG

[Rui Marinho]

Hi,

Wireguard randomly stops responding to delete interfaces wireguard requests and it becomes a bit of a nightmare to get things back to a working state. I found out about the route-allowed-ips false workaround has been the only way I can actually delete wireguard-related configs. But the success rate isn't very high - it depends on some other factors which I have been unable to understand yet.

I am still getting provisioning loops with the following error when I add in the firewalls (either via command or via a config json). Not consistently, which makes things harder to debug.

{
  "COMMIT": {
    "error": "\ufffe[ interfaces wireguard wg0 firewall in name LAN_IN ]\nNothing to do\n\n\uffff1\n\ufffe[ interfaces wireguard wg0 firewall local name LAN_LOCAL ]\nNothing to do\n\n\uffff1\n\ufffe[ interfaces wireguard wg0 firewall out name LAN_OUT ]\nNothing to do\n\n\uffff1\nCommit failed\n",
    "failure": "1",
    "success": "1"
  },
  "DELETE": {
    "failure": "0",
    "success": "1"
  },
  "SESSION_ID": "e2d744b8434b60721035d6a4de",
  "SET": {
    "failure": "0",
    "success": "1"
  }
}```

On a separate scenario, I get a little nervous when I see `config.boot` populated with wireguard sections even post-reboot after deleting all wireguard interfaces through the cli. What could be causing this persistence if I am not provisioning it in a config json?