Could not associate the gluster volume with correct network as no gluster network found in the cluster.

Solution Verified - Updated -

Issue

  • The following messages are observed in the engine logs:
018-04-10 23:06:27,040+02 WARN  [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler10) [5f66d485] Could not associate brick '<gluster_server_IP>:/gluster_volume' of volume '<volume_ID>' with correct network as no gluster network found in cluster '<cluster_ID>'
2018-04-10 23:06:27,041+02 WARN  [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler10) [5f66d485] Could not associate brick '<gluster_server_IP>:/gluster_volume'' of volume '<volume_ID>' with correct network as no gluster network found in cluster '<cluster_ID>'

Environment

  • Red Hat Hyperconverged Infrastructure Version 1.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.