Instead of counting the string "interface" the test needs to scan the corosync.conf file for the directices node { ... }. There must be exact 2 such node-directives for the current se case and each of the entries needs exact two ring-addresses to be configured.
The perl-snipset outputs a "2" per found node-directive (if exactly 2 rings are found). So the correct result following the best practice is "22" (both name-directives have exact two ring-address definitions).
Instead of counting the string "interface" the test needs to scan the corosync.conf file for the directices node { ... }. There must be exact 2 such node-directives for the current se case and each of the entries needs exact two ring-addresses to be configured. The perl-snipset outputs a "2" per found node-directive (if exactly 2 rings are found). So the correct result following the best practice is "22" (both name-directives have exact two ring-address definitions).