accidentally, 2 instances of mcollective were running instead of one due to error in fuel-main somewhere. That error was fixed, but the bug which it introduced could be encountered only if 2 instances of fuel-agent will be started simultaneously with the extremely precise timing.
i can't suggest any 100% working steps for reproducing. I doubt if it could be reproduced with our regular deployment flow.
however, committed fix comes with nice unit test coverage, so, i think it's absolutely safe to mark it as 'fix released' according to the committed code without performing of full verification/reproducing cycle against the fix.
bug was caught under very specific circumstances.
accidentally, 2 instances of mcollective were running instead of one due to error in fuel-main somewhere. That error was fixed, but the bug which it introduced could be encountered only if 2 instances of fuel-agent will be started simultaneously with the extremely precise timing.
i can't suggest any 100% working steps for reproducing. I doubt if it could be reproduced with our regular deployment flow.
however, committed fix comes with nice unit test coverage, so, i think it's absolutely safe to mark it as 'fix released' according to the committed code without performing of full verification/ reproducing cycle against the fix.