Subnet field was and is (in 6.2) required field for Managed and/or Provision interfaces. It defines whether to use DHCP or Static configuration for Managed interface and defines other required services for Provision interface like Puppet Master/CA, TFTP, Reverse DNS and Discovery. These are essential associations which are made through Subnet, for this reason this is mandatory field and we unlikely change that.

For unmanaged (non-provision) interfaces it should be technically possible not to require Subnet field, but we don't support that. I was under impression that version 6.2 supports that, but that was not the case. But if I understand customer requirements correctly, in both cases they would like to have the field optional for Provision interfaces.

While it might be tempting to do a workaround by creating a "fake" Subnet(s), I'd not recommend that. If subnet address and netmask does not match, Satellite will be unable to find the subnet for particular IP address (e.g. discovery finds Capsule for communication).

This is a tracking ticket to make subnet an optional field.