The corosync service fails to start with "Error: corosync[xxxx]: parse error in config: Can't open logfile '/var/log/cluster/corosync.log' for reason: No such file or directory"

Issue

• Corosync fails to start with Error: unable to start corosync

  Starting Cluster...
  Job for corosync.service failed because the control process exited with error code. See "systemctl status corosync.service" and "journalctl -xe" for details.
  Error: unable to start corosync
  

• The following messages are seen in journalctl -xe and /var/log/messages:

  Jun 16 07:19:23 node1 corosync[1654]: parse error in config: Can't open logfile '/var/log/cluster/corosync.log' for reason: No such file or directory (2).
  Jun 16 07:19:23 node1 corosync: Starting Corosync Cluster Engine (corosync): [FAILED]
  Jun 16 07:19:23 node1 systemd: corosync.service: control process exited, code=exited status=1
  Jun 16 07:19:23 node1 systemd: Failed to start Corosync Cluster Engine.