To work around this, we copied the config from a known good router with a similar config. We pasted that into a CLI template with the corrected, device-specific values (site ID, site IP, addresses, etc.) and were able to apply the CLI template successfully. We then detached the CLI template and then applied the feature template successfully with no further issue with this bug.
