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

kubevirt addon doesn't init kubevirt ns and it's content #19303

Open
peedy2495 opened this issue Jul 19, 2024 · 2 comments
Open

kubevirt addon doesn't init kubevirt ns and it's content #19303

peedy2495 opened this issue Jul 19, 2024 · 2 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@peedy2495
Copy link

What Happened?

After enabling the kubevirt addon the install.sh (ref: deploy/addons/kubevirt/pod.yaml.tmpl) can't be executed.
Reason: curl isn't available in the kubevirt-install-manager container.

Attach the log file

/kubevirt-scripts/install.sh: line 3: curl: command not found
Installing KubeVirt version:
/kubevirt-scripts/install.sh: line 6: curl: command not found
error: the path "/manifests/kubevirt-operator.yaml" does not exist
error: resource mapping not found for name: "kubevirt" namespace: "kubevirt" from "STDIN": no matches for kind "KubeVirt" in version "kubevirt.io/v1"
ensure CRDs are installed first

Operating System

Ubuntu

Driver

Docker

@peedy2495 peedy2495 changed the title kubevirt addon doesn't init kubevirt ns an tit's content kubevirt addon doesn't init kubevirt ns and it's content Jul 19, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 17, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants