Mcollective TLS uses SSLv3 after reboot

[andrewklau]

After a reboot, mcollective tries to connect to activemq through SSLv3

As its not part of an available protocol it will error. Leaving hard to trace errors unless you explicitly check the connection. Removing the protocol restriction resumes the connection.

I'm not sure why this happens but thought I should report it in case someone else sees this. I'm still away for a few more days so can't investigate further.

[andrewklau]

Issue happened after updating openssl around early Jan, getting the latest version of ruby193-mcollective has resolved this issue.

[andrewklau]

Still happens after reboot, seems upgrading/downgrading solves the issue but after a reboot some settings are lost. Can't seem to isolate what's doing this..