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

Auto-correct previous bad image installs of podman-net-usermode #21014

Closed
wants to merge 1 commit into from

Conversation

n1hility
Copy link
Member

@n1hility n1hility commented Dec 14, 2023

Additional improvement to resolution of #20982

v39.0.1-3 introduced an update to gvforwarder with defunct perms. Detect and correct this condition so that users do not need to reinit a fresh user-mode dist.

Auto-corrects previous installs of podman-net-usermode that were created from a defective image update (v39.0.1) 

@openshift-ci openshift-ci bot added release-note approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Dec 14, 2023
@n1hility
Copy link
Member Author

/cherry-pick v4.8

@openshift-cherrypick-robot
Copy link
Collaborator

@n1hility: once the present PR merges, I will cherry-pick it on top of v4.8 in a new PR and assign it to you.

In response to this:

/cherry-pick v4.8

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.

@n1hility n1hility changed the title Auto-correct previous bad image install of podman-net-usermode Auto-correct previous bad image instalsl of podman-net-usermode Dec 14, 2023
@n1hility n1hility changed the title Auto-correct previous bad image instalsl of podman-net-usermode Auto-correct previous bad image installs of podman-net-usermode Dec 14, 2023
@@ -29,6 +29,8 @@ fi
if [[ ! $ROUTE =~ default\ via ]]; then
exit 3
fi
# auto-correct previous installs of known bad image v39.0.3
test -x /usr/local/bin/vm || chmod 755 /usr/local/bin/vm
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any reason to do the test vs just always the chmod?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no real convincing reason, other than to save an exec since test is a builtin, but that won't really make any discernible difference, so I just changed it.

v39.0.1-3 introduced an update to gvforwarder with defunct perms.
Detect and correct this condition so that users do not need to
reinit a fresh user-mode dist.

[NO NEW TESTS NEEDED]

Signed-off-by: Jason T. Greene <[email protected]>
Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

openshift-ci bot commented Dec 15, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, n1hility

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

Copy link

A friendly reminder that this PR had no activity for 30 days.

@Luap99
Copy link
Member

Luap99 commented Jan 22, 2024

@n1hility Do we still need this?

@github-actions github-actions bot removed the stale-pr label Jan 23, 2024
@n1hility
Copy link
Member Author

no longer relevant

@n1hility n1hility closed this Mar 19, 2024
@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Jun 18, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Jun 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants