Hi Mike Sorry for the last email. "Send" got clicked . So for GEODE-3926 only two commits made into release/1.6.0 -75ae58423bc66ca127fec7d2fc3ad71fbed61094 -99caa3038b544ee444d6f151b4c0b9aa77204741
However these commits didn't make into release 1.6.0 - b71b79fe813b408fc50a172644007e2d5f54a1e2 - 83c667b12c510f7a10aca57179b9e61f29cfddbb I think lack of these commits in the release/1.6.0 is causing failures in the rolling upgrade tests. I am currently testing the branch with these fixes. Will update soon. Regards Nabarun Nag On Thu, Apr 19, 2018 at 12:15 PM Nabarun Nag <n...@pivotal.io> wrote: > Hi Mike, > GEODE-3926 only two commits made into the release > > > On Thu, Apr 19, 2018 at 10:49 AM Xiaojian Zhou <gz...@pivotal.io> wrote: > >> I have cherry-picked GEODE-5056 into 9.5 and 1.6.0 >> >> On Thu, Apr 19, 2018 at 9:09 AM, Bruce Schuchardt <bschucha...@pivotal.io >> > >> wrote: >> >> > Thanks Mike - I've cherry-picked the fix onto the release/1.6.0 branch >> > >> > >> > >> > On 4/18/18 5:11 PM, Michael Stolz wrote: >> > >> >> Yes please. I'm holding the build til this gets in. Please notify me >> here >> >> when it's ready >> >> >> >> -- >> >> Mike Stolz >> >> Principal Engineer - Gemfire Product Manager >> >> Mobile: 631-835-4771 <(631)%20835-4771> >> >> >> >> On Apr 18, 2018 8:05 PM, "Bruce Schuchardt" <bschucha...@pivotal.io> >> >> wrote: >> >> >> >> A couple of people have reported running into GEODE-5085 < >> >>> https://issues.apache.org/jira/browse/GEODE-5085>, which prevents a >> >>> server from rejoining the cluster if it gets kicked out and a >> >>> SecurityManager has been configured. >> >>> >> >>> Is this something we could get into the 1.6 release? The fix is a >> single >> >>> commit and it's been through precheckin testing a few times now. >> >>> >> >>> >> >>> >> >>> >> > >> >
