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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] could not get correct branch name from longhorn/spdk #8432

Open
a110605 opened this issue Apr 24, 2024 · 0 comments
Open

[BUG] could not get correct branch name from longhorn/spdk #8432

a110605 opened this issue Apr 24, 2024 · 0 comments
Labels
kind/bug 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

Comments

@a110605
Copy link

a110605 commented Apr 24, 2024

Describe the bug

Longhorn branch could not be found when apply longhorn-spdk-setup yaml.

To Reproduce

Follow prerequisites docs, applying longhorn-spdk-setup yaml should git clone correct setup script from https://github.com/longhorn/spdk/tree/longhorn-1.6.

kubectl apply -f https://raw.githubusercontent.com/longhorn/longhorn/v1.6.1/deploy/prerequisite/longhorn-spdk-setup.yaml

But got

fatal: Remote branch longhorn not found in upstream origin. Failed to configure SPDK environment error code 1

image

Expected behavior

Should git clone script from spdk repo without any problem.

Support bundle for troubleshooting

Environment

  • Longhorn version: 1.6.1
  • Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Kubectl
  • Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: K3s
    • Number of control plane nodes in the cluster: 1
    • Number of worker nodes in the cluster: 1
  • Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): digital ocean
  • Number of Longhorn volumes in the cluster: 0

Additional context

@a110605 a110605 added kind/bug 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 Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug 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

1 participant