Join GitHub today
multi-master failover stack trace when minion fails over to other master #30643
In 2015.8.4 the same behavior as reported in the above issues is the same:
The only new behavior i am reporting is during step 3 when the minion fails over to the second master there is now a stack trace error in 2015.8.4 as follows:
referenced this issue
Feb 26, 2016
@DmitryKuzmenko I am a little confused how to apply those PR's to the 2015.8 branch to test since they were added to develop. Do I just wait until they are added to 2015.8 to test? I tested on the head of the 2015.8 branch just a second ago, and tried pulling in those files as well, but still did not see any changes in multi-master, but I'm sure I'm applying these PRs incorrectly.
@DmitryKuzmenko Thanks for merging those forward I appreciate it. I have tested and this particular issue has been fixed on 2015.8 so I will go ahead and close this particular issue.
I did test this on the head of 2016.3 and it is not working, but I'm assuming this still needs to be merged forward to 2016, so I will test again later this week.