Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] v2 volume always displays engine upgrade available on UI #7489

Closed
yangchiu opened this issue Dec 29, 2023 · 2 comments
Closed

[BUG] v2 volume always displays engine upgrade available on UI #7489

yangchiu opened this issue Dec 29, 2023 · 2 comments
Assignees
Labels
kind/bug priority/0 Must be fixed in this release (managed by PO) reproduce/always 100% reproducible require/backport Require backport. Only used when the specific versions to backport have not been definied. require/qa-review-coverage Require QA to review coverage
Milestone

Comments

@yangchiu
Copy link
Member

Describe the bug (馃悰 if you encounter this issue)

Install Longhorn master-head (longhorn-manager be08850), and create a v2 volume, always displays engine upgrade available on UI:

vol-1

But it's actually unable to be upgraded:

vol-2

To Reproduce

create a v2 volume on Longhorn master-head

Expected behavior

Support bundle for troubleshooting

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:
    • Kernel version:
    • CPU per node:
    • Memory per node:
    • Disk type(e.g. SSD/NVMe/HDD):
    • Network bandwidth between the nodes:
  • Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
  • Number of Longhorn volumes in the cluster:
  • Impacted Longhorn resources:
    • Volume names:

Additional context

@yangchiu yangchiu added kind/bug reproduce/always 100% reproducible priority/1 Highly recommended to fix in this release (managed by PO) require/qa-review-coverage Require QA to review coverage require/backport Require backport. Only used when the specific versions to backport have not been definied. labels Dec 29, 2023
@yangchiu yangchiu added this to the v1.6.0 milestone Dec 29, 2023
@derekbit
Copy link
Member

The task is #7445
cc @scures

@derekbit derekbit added priority/0 Must be fixed in this release (managed by PO) and removed priority/1 Highly recommended to fix in this release (managed by PO) labels Dec 29, 2023
@innobead
Copy link
Member

innobead commented Jan 4, 2024

Duplicated of #7445

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug priority/0 Must be fixed in this release (managed by PO) reproduce/always 100% reproducible require/backport Require backport. Only used when the specific versions to backport have not been definied. require/qa-review-coverage Require QA to review coverage
Projects
None yet
Development

No branches or pull requests

4 participants