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

Error processing tar file with symlinks #140

Closed
soltysh opened this issue Sep 10, 2019 · 5 comments
Closed

Error processing tar file with symlinks #140

soltysh opened this issue Sep 10, 2019 · 5 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@soltysh
Copy link
Member

soltysh commented Sep 10, 2019

When I'm trying to build images from https://github.com/openshift/oc or https://github.com/openshift/cluster-kube-apiserver-operator I'm getting:

$ make images
imagebuilder --allow-pull -t registry.svc.ci.openshift.org/ocp/4.2:cluster-kube-apiserver-operator -f ./Dockerfile.rhel7 .
--> FROM registry.svc.ci.openshift.org/ocp/builder:golang-1.12 as builder
--> WORKDIR /go/src/github.com/openshift/cluster-kube-apiserver-operator
--> COPY . .
API error (500): Error processing tar file(exit status 1): invalid symlink "/go/src/github.com/openshift/cluster-kube-apiserver-operator/vendor/github.com/coreos/etcd/Documentation/README.md" -> "docs.md"
make: *** [Makefile:20: image-ocp-cluster-kube-apiserver-operator] Error 1

Removing that particular link give me a similar error about a different link. Looks like there's a problem with symlinks.

@tnozicka
Copy link

@mrunalp @rhatdan do you know who owns the failing part / who is the right person to ping?

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 18, 2020
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-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 Oct 20, 2020
@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci-robot
Copy link

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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/test-infra repository.

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

4 participants