Skip to content

fix: replace symlinks with mv/cp in prepare-draft-release#3366

Merged
tekton-robot merged 1 commit intotektoncd:mainfrom
vdemeester:fix-draft-release-symlinks
Apr 22, 2026
Merged

fix: replace symlinks with mv/cp in prepare-draft-release#3366
tekton-robot merged 1 commit intotektoncd:mainfrom
vdemeester:fix-draft-release-symlinks

Conversation

@vdemeester
Copy link
Copy Markdown
Member

Changes

runc fails with mkdir /workspace/shared/repo: file exists when a step's workingDir points through a symlink. The prepare-draft-release task creates symlinks (repo → git, release → bucket/<version>) for the create-draft-release-oci task, but runc's container init tries to mkdir the workingDir path and fails when it encounters the symlink.

Replace ln -sfn with mv (for git checkout) and cp -r (for release artifacts) to give create-draft-release real directories instead of symlinks.

Observed in two consecutive release runs:

  • release-patch-lm7mdPodCreationFailed
  • release-patch-bh52zPodCreationFailed

A follow-up PR will update the plumbing task to accept configurable paths, removing the need for any renaming.

Submitter Checklist

  • Run make test lint before submitting a PR
  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices

Release Notes

NONE

@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Apr 22, 2026
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Apr 22, 2026
runc fails with 'mkdir /workspace/shared/repo: file exists' when
a step's workingDir points through a symlink. The prepare-draft-release
task was creating symlinks (repo → git, release → bucket/<version>)
to bridge the naming gap between the operator pipeline and the
create-draft-release-oci task.

Instead, use the source-subpath and release-subpath params added in
plumbing (65d3485eedbb) to pass the correct paths directly. This
removes the need for any symlinks, mv, or cp operations.

Also update the plumbing git resolver pin to 7abffd25eb2e.
@vdemeester vdemeester force-pushed the fix-draft-release-symlinks branch from 94dca5e to cfecbc9 Compare April 22, 2026 12:31
@anithapriyanatarajan
Copy link
Copy Markdown
Contributor

/kind cleanup

@tekton-robot tekton-robot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Apr 22, 2026
@anithapriyanatarajan
Copy link
Copy Markdown
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 22, 2026
@anithapriyanatarajan
Copy link
Copy Markdown
Contributor

/approve

@tekton-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anithapriyanatarajan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [anithapriyanatarajan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 22, 2026
@tekton-robot tekton-robot merged commit ac736e5 into tektoncd:main Apr 22, 2026
16 checks passed
@vdemeester vdemeester deleted the fix-draft-release-symlinks branch April 22, 2026 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants