The first thing you need to do is find what the problem in the config is. You can run 'show configuration failure all' for clues. For example:
(master-a.dev.mobility.cns.vt.edu)[[00:1a:1e:00:ab:38]##show configuration failure all
All Configuration Failure
-------------------------
IP Address MAC Config ID Process Command Message
---------- --- --------- ------- ------- -------
198.82.xxx.xx 00:1a:1e:00:ab:38 37 Layer2/3 ipv6 address 2001:468:c80:2118::19/64 IPv6 Prefix conflicts with another Interface
198.82.xxx.xx 00:1a:1e:00:be:00 34
Total switches with config failures::2
As you can see, sometimes it is helpful, and sometimes not. Once you have resloved the config issues, do another 'write memory'. It sounds like you may have done this already, and as you have noticed, you're not quite done. Next log into the md, and tell it to do a full refresh of its config, using the `ccm-debug` command. The AOS 8.x-y way of connectng to the local md is by using the `mdconnect` command.
(master-a.dev.mobility.cns.vt.edu) [/] #cd cottonmouth
(master-a.dev.mobility.cns.vt.edu) [00:1a:1e:00:be:00] #mdconnect
Redirecting to Managed Device Shell
Last login: Tue Feb 13 13:40:23 2018 from 172.21.20.101
(yellowbelly) [MDC] *#ccm-debug full-config-sync
(yellowbelly) [MDC] *#exit
Exiting Managed Device Shell
(master-a.dev.mobility.cns.vt.edu) [00:1a:1e:00:be:00] #show configuration failure all
All Configuration Failure
-------------------------
IP Address MAC Config ID Process Command Message
---------- --- --------- ------- ------- -------
Total switches with config failures::0