> > > > Hi Andrew-san, > > > > > You're saying that some resources aren't being promoted to master > > > > > anymore? > > > > > > > > Partially yes. In 2.1.1 I could not write cib.xml to run Stateful as > > > > Master. But I encountered the situation that same cib.xml file makes > > > > Master on 2.0.8. So, I think crmd (or PE?) feature changed. > > > > Especially, attached cib.xml file with posted mail displays such a a > > > > phenomena. > > > > > > Looks like you are correct. > > > Fixed in: > > > http://hg.beekhof.net/lha/crm-dev/rev/716b5a3a457e > > > > Hi, Andrew-san. > > > > Thank you for your working and I confirmed that Stateful script runs > > as Master by above fix. But I feel incongruity for the point that when > > described Master node is stopped, stanby Slave node does not become to > > Master. And I attached the log file on the situation. > > This is actually the correct behavior. > There is no rsc_location constraint allowing us to promote sf:* on > sel4 nor has a master preference been set by the RA with > crm_master.... so no promotion should occur.
OK. I understood and have a last question. In 2.0.8 sel4 becomes Master for Stateful, so is it incorrect behaviour and fixed in the term between 2.0.8 and 2.1.1? MATSUDA, Daiki _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
