Skip to content

[BUG] Volume detached automatically after upgrade Longhorn #5983

Closed
@yangchiu

Description

Describe the bug (🐛 if you encounter this issue)

Create a volume and attach it to a node, and upgrade Longhorn, after Longhorn upgraded, the attached volume is detached automatically. Need to confirm if it's the expected behavior.

To Reproduce

Steps to reproduce the behavior:

  1. Install Longhorn v1.4.0
  2. Create a volume from UI, and attach it to a node from UI
  3. Upgrade Longhorn to master-head
  4. The attached volume becomes detached

Expected behavior

A clear and concise description of what you expected to happen.

Log or Support bundle

If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.

Environment

  • Longhorn version:
  • Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
  • Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:
    • Number of management node in the cluster:
    • Number of worker node in the cluster:
  • Node config
    • OS type and version:
    • CPU per node:
    • Memory per node:
    • Disk type(e.g. SSD/NVMe):
    • Network bandwidth between the nodes:
  • Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
  • Number of Longhorn volumes in the cluster:

Additional context

Add any other context about the problem here.

Metadata

Labels

area/volume-attach-detachVolume attach & detach relatedcomponent/longhorn-managerLonghorn manager (control plane)kind/bugpriority/0Must be implement or fixed in this release (managed by PO)reproduce/always100% reproducibleseverity/1Function broken (a critical incident with very high impact (ex: data corruption, failed upgrade)

Type

No type

Projects

  • Status

    Closed

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions