There are several reasons for removal of CTS:
1. It's not actively maintained
2. It's quite hard to setup
3. It has hard to fix bug in it's design (syslog messages are thrown by
rsyslog (configurable), journald (configurable) or when rsyslog is
used together with journald (non configurable)) so test
can fail just because of lost message.
4. It depends on pacemaker CTS, which is changed quite often
5. CTS itself is great tool for Pacemaker
(shutdown/startup of the node), but Corosync has a slightly
different needs
6. Bin Liu <bliu@suse.com> made a heroic effort to port it to Python 3
(huge thanks), but it's still not fully complete
All and all, if somebody is interested in maintaining CTS code, please
create repository similar to corosync flatiron cts and let us know.
Signed-off-by: Jan Friesse <jfriesse@redhat.com> Reviewed-by: Fabio M. Di Nitto <fdinitto@redhat.com> Reviewed-by: Christine Caulfield <ccaulfie@redhat.com>