This article provides information on how to resolve the issue where MIST generates an incomplete configuration, resulting in a configuration commit failure.

To isolate the issue, review the error details in the API response at the following endpoint (check the error section at the bottom):

https://api.mist.com/api/v1/sites/<site-id>/devices/00000000-0000-0000-1000-<device-mac>/config_cmd

For example, if there is an invalid subnet specified in the network interface configuration, MIST may fail to generate the configuration entirely. This results in all related configuration elements being skipped.

network[NEW_LAN_NETWORK].subnet invalid, dhcpd[NEW_LAN_NETWORK]

To fix this issue, verify if there is any typo in the subnet configuration for the specific network. If a variable is being used, ensure that the variable itself does not contain any errors in its subnet definition.

For example, a common mistake is defining all 4 octets in a subnet variable and then appending an additional octet when referencing it elsewhere. This results in a 5-octet IP address, which is invalid and causes the configuration to fail.