MaxScale not correctly recognizing new topology when we failover to a new master
Turns out the issue was that mysqlfailover was causing a conflict with maxscale.  When the master would fail, mysqlfailover would automatically promote a new slave to master.  However, when we did this it would cause a conflict with Maxscale (since it usually does it on its own), so it would lose track of which servers were the master and which were the slaves.