Unit "multipathd.socket" failed on OpenShift Node

Issue

• On an OpenShift Container Platform (OCP) node the following error message can be observed when logging in via SSH:

  $ ssh core@node-123.example.com
  Red Hat Enterprise Linux CoreOS 46.82.202105060947-0
  Part of OpenShift 4.6, RHCOS is a Kubernetes native operating system
  managed by the Machine Config Operator (`clusteroperator/machine-config`).
  
  WARNING: Direct SSH access to machines is not recommended; instead,
  make configuration changes via `machineconfig` objects:
  https://docs.openshift.com/container-platform/4.6/architecture/architecture-rhcos.html
  
  
  Last login: Thu Jun 24 13:02:43 2021 from 10.10.120.21
  [systemd]
  Failed Units: 1
  multipathd.socket
  [core@node-123 ~]$
  

• The systemd unit multipathd.socket shows as failed:

  * multipathd.socket - multipathd control socket
   Loaded: loaded (/usr/lib/systemd/system/multipathd.socket; enabled; vendor preset: disabled)
   Active: failed (Result: trigger-limit-hit) since Thu 2021-06-17 11:54:30 UTC; 1 weeks 0 days ago
   Listen: @/org/kernel/linux/storage/multipathd (Stream)
      CPU: 0
  
  Jun 17 11:54:30 node-123.example.com systemd[1]: multipathd.socket: Trigger limit hit, refusing further activation.
  Jun 17 11:54:30 node-123.example.com systemd[1]: multipathd.socket: Failed with result 'trigger-limit-hit'.
  Jun 17 11:54:30 node-123.example.com systemd[1]: multipathd.socket: Consumed 0 CPU time