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

Cirrus: Prevent resident pollution #3985

Merged
merged 1 commit into from
Sep 19, 2019

Conversation

cevich
Copy link
Member

@cevich cevich commented Sep 10, 2019

When constructing VM cache-images, the latest/greatest podman package is
installed to ensure all necessary dependencies are met. Prior to
testing source-built binaries, most of of the packaged files are removed.
However, if the io.podman service or socket is enabled/running, it
could cause the packaged podman and varlink binaries to be both resident
and cached. Since this condition would cause very difficult to diagnose
behaviors, add preventative measures to ensure these services are absent
prior to removing packaged podman files.

Signed-off-by: Chris Evich [email protected]

contrib/cirrus/lib.sh Outdated Show resolved Hide resolved
Copy link
Member

@edsantiago edsantiago left a comment

Choose a reason for hiding this comment

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

LGTM in principle. I may want to explore other options with podman-remote system tests, such as defining a random PODMAN_VARLINK_ADDRESS; but this too will be nice to have. Thanks.

contrib/cirrus/lib.sh Outdated Show resolved Hide resolved
contrib/cirrus/lib.sh Show resolved Hide resolved
contrib/cirrus/lib.sh Outdated Show resolved Hide resolved
contrib/cirrus/lib.sh Outdated Show resolved Hide resolved
@cevich cevich force-pushed the verify_no_podman branch 3 times, most recently from 302dcbb to 2ad0dc5 Compare September 10, 2019 19:46
@cevich
Copy link
Member Author

cevich commented Sep 10, 2019

Thanks for taking a look @edsantiago I appreciate it. Pretty sure I captured all your feedback in the latest push.

contrib/cirrus/lib.sh Outdated Show resolved Hide resolved
When constructing VM cache-images, the latest/greatest podman package is
installed to ensure all necessary dependencies are met.  Prior to
testing source-built binaries, most of of the packaged files are removed.
However, if the `io.podman` service or socket is enabled/running, it
could cause the packaged podman and varlink binaries to be both resident
and cached.  Since this condition would cause very difficult to diagnose
behaviors, add preventative measures to ensure these services are absent
prior to removing packaged podman files.

Signed-off-by: Chris Evich <[email protected]>
@cevich
Copy link
Member Author

cevich commented Sep 10, 2019

rebased w/ -q addition and force-pushed.

Copy link
Member

@edsantiago edsantiago left a comment

Choose a reason for hiding this comment

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

LGTM

@rhatdan
Copy link
Member

rhatdan commented Sep 11, 2019

/aprove

@rhatdan
Copy link
Member

rhatdan commented Sep 11, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 11, 2019
@rhatdan
Copy link
Member

rhatdan commented Sep 19, 2019

/approve

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cevich, edsantiago, rhatdan

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 19, 2019
@openshift-merge-robot openshift-merge-robot merged commit 408f278 into containers:master Sep 19, 2019
@cevich cevich deleted the verify_no_podman branch June 30, 2021 18:11
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
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. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants