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

panic: mkdir /tmp/kubebuilder-envtest: read-only file system #1651

Closed
helen-frank opened this issue Sep 10, 2024 · 4 comments
Closed

panic: mkdir /tmp/kubebuilder-envtest: read-only file system #1651

helen-frank opened this issue Sep 10, 2024 · 4 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@helen-frank
Copy link
Contributor

Description

Observed Behavior:

Expected Behavior:
karpenter pod runing
Reproduction Steps (Please include YAML):

# make apply
...

# kubectl -n kube-system get pod | grep karpenter
karpenter-5fdbd7dd77-frzhg                 0/1     Error     1 (7s ago)   13s
# kubectl -n kube-system logs -f karpenter-5fdbd7dd77-frzhg
panic: mkdir /tmp/kubebuilder-envtest: read-only file system

goroutine 1 [running]:
sigs.k8s.io/controller-runtime/pkg/internal/testing/addr.init.0()
        sigs.k8s.io/[email protected]/pkg/internal/testing/addr/manager.go:57 +0x15c

Versions:

  • Chart Version:
  • Kubernetes Version (kubectl version): v1.31.0
  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@helen-frank helen-frank added the kind/bug Categorizes issue or PR as related to a bug. label Sep 10, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 10, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Karpenter contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@helen-frank
Copy link
Contributor Author

/assign

I'll try to fix that.

If anyone else knows of a solution to this problem, I'd appreciate it.

@helen-frank
Copy link
Contributor Author

I'm guessing it was caused by this change 75fcd2a

My pr #1623 hasn't run git fetch all; git rebase upstream/main, so the make apply test is fine.

@jonathan-innis
Copy link
Member

Fixed by #1660. Looks like we (I) unintentionally imported something that added envtest to our dependency graph...and broke everything :)

Fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants