Skip to main content
NetApp Knowledge Base

A Trident volume created in Docker Swarm cluster is not visible to all the nodes

  1. Last updated
  2. Save as PDF
Views:
18
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • Docker Swarm cluster running Docker 24.0.2-1
  • NetApp Astra Trident 23.07.1
  • iSCSI protocol

Issue

  • When creating a new Docker volume, it is not visible to all the workers/managers.
  • The multipathing information is inconsistent
  • High I/O wait in the  Swarm worker nodes and faulty error message in the output of multipath -ll

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.

 

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Reference
    Confidence
    Validated
    Flag
    False
    Governance
    Experience
    KCS Enabled
    Yes
    Visibility
    Public
    Product Categories
    Trident Kubernetes
    Specialty
    SNAPx
  2. Tags
    1. 2009966288
    2. Docker Swarm
    3. Trident