Description

When poking around with /30 subnet (which resulted in previous ticket), and ending up with a /29 range instead, I forgot to add it to the network record itself. When creating VM, I selected this empty network and was able to start VM provision, which hanged in "placing" state for some time and then failed with no log records about it in Chunter logs.

Cerberus (or Sniffle) should probably check if there's at least one IP range (shich has free IPs available) in a network before marking the "Networking" screen as correctly filled and throw a warning if it's not.