It's possibly you have the GPU Preview turned on if you have the latest version of CC 2015. Either choose View > CPU Preview or turn off GPU Preferences in InDesign preferences. I saw that in CC 2015 latest version but the bug goes away in CC 2017.
Just to address the problem you're having using CC 2017. I had a similar problem with it when I first installed and found that it did not work well with the preference file that was left over from CC 2015. Deleting that pref file made it possible to work well with CC 2017. As Steve said above CC 2017 takes care of the bug that you're having a problem with in CC 2015.
To delete your old preferences:
With InDesign closed launch a Finder Window in column view and click on your home folder. With the Option Key pressed choose Library from the Finder Go Menu. Within the Library folder find the following two files and delete them: “Adobe InDesign” and “com.adobe.InDesign.plist”. When InDesign is next launched it will create new preference files and the program will be restored to its defaults.
After you’ve reset up the program (make sure that no document window is open) to your liking, it is a really good idea to create copies of your personalized “mint” preference files (make sure that you quit the program before copying them—that finalizes your customization) and use them in the future to replace any corrupt versions you may need to delete.
You should also delete your old Cache files. To do so within the Library folder find the “Caches” folder. Within the Caches folder find and delete the entire file “Adobe InDesign”. I find that deleting the cache file completely leads to a lasting change.
Now that you're completely reset, try CC 2017 and see if it fixes your original problem.
That worked perfectly.
I am still hesitant to go back to 2017 and I know for a fact it was nothing to do with preferences as I got a brand new iMac and installed only 2017 on it, when I started having the issues I installed 2015 and haven't had a problem until the Master Page Issue.
I will give it a try though and see if the bug has been ironed out.