Cause: cman iterates the interface list to try and find a match between active network interfaces and names in cluster.conf. If a name lookup fails then cman abandons the whole operation, rather than just that name lookup.
Consequence: If a name lookup fails for some reason (DNS error) then cman can fail to start. The error message it prints gives the impression that $HOSTNAME was not found in cluster.conf
Fix: The interface iterator code was fixed to use 'continue' rather than 'break' if a name lookup failed.
Result: This bug CAN still occur. If the name that cman is looking for is subject to a DNS failure then this message will be printed and cman will not start. fixing this is outside the scope of cman however.