-
Notifications
You must be signed in to change notification settings - Fork 475
create ctr symlink after installation #1916
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
create ctr symlink after installation #1916
Conversation
Signed-off-by: Carlos Salas <carlos.salas@suse.com>
damdo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
drew-viles
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ok-to-test
/lgtm
|
/test pull-azure-vhds |
cpanato
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm
|
@damdo I think you have a hold on this, are we ready to remove it? |
|
/unhold Thanks @salasberryfin |
|
/assign @drew-viles @mboersma For approval Thanks! |
drew-viles
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, damdo, drew-viles The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Change description
This is an attempt at fixing an error that occurs when the
urltask is called before a symbolic link to/usr/local/bin/ctris created. This task tries to execute/usr/bin/ctrbefore it is available in the path and it fails to build the image.The issue was identified in the job
periodic-cluster-api-provider-gcp-make-conformance-main-ci-artifacts(Prow job history), which is one of the recently reported jobs in the Kubernetes organization that have been failing for a long time.When building the image for
cluster-api-provider-gcpwithkubernetes_source_type == "http"andkubernetes_cni_source_type == "http", the job outputs the following error:"/bin/sh: 1: /usr/bin/ctr: not found"A full log can be found here.
The proposed fix places the creation of the symlink right after
containerdis installed. If this is not considered the correct approach, we can look for other alternatives to avoid calling tasks that invoke/usr/bin/ctrbefore it is available.cc @justinsb @damdo @cpanato
Related issues
Additional context
This originated from @justinsb's investigation kubernetes-sigs/cluster-api-provider-gcp#1529 (comment)