Can I get pt-online-schema-change to abort if it can't connect to slave DBs?

Hi Carlos,

The issue was that the root user didn’t have the necessary permissions to connect to the slaves - they were discoverable, just not able to be connected to. That being said, I’m still looking for a way to run the command in a way that it would abort itself if the found slaves could not be connected to.

Thanks