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

Add tests to make sure mounts.conf does not warn on missing content #21272

Merged
merged 1 commit into from
Feb 2, 2024

Conversation

rhatdan
Copy link
Member

@rhatdan rhatdan commented Jan 16, 2024

Does this PR introduce a user-facing change?

Podman in podman will not longer warn on missing content in mounts.conf

@openshift-ci openshift-ci bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. release-note labels Jan 16, 2024
Copy link
Contributor

openshift-ci bot commented Jan 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 16, 2024
skip_if_remote "--default-mounts-file is not supported for remote clients"
MOUNTS_CONF=$PODMAN_TMPDIR/mounts.conf
run_podman run --rm --default-mounts-file=${MOUNTS_CONF} $IMAGE echo test1
assert "$output" = "test1" "No warning messages"
Copy link
Member

Choose a reason for hiding this comment

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

Request: unique test failure messages: "No warning messages with missing mounts.conf", "...with empty mounts.conf", "with bogus mounts.conf". That makes it so much nicer for the monkey looking at test failures.

@rhatdan rhatdan changed the title [WIP] Add tests to make sure mounts.conf does not warn on missing content Add tests to make sure mounts.conf does not warn on missing content Jan 17, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 17, 2024
randcontent=$(random_string 30)
mkdir -p $PODMAN_TMPDIR/mounts
echo $randcontent > $PODMAN_TMPDIR/mounts/$randfile
echo $PODMAN_TMPDIR/mounts:/run/secrets > $PODMAN_TMPDIR/mounts.conf
Copy link
Member

Choose a reason for hiding this comment

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

Could use ${MOUNTS_CONF} instead of $PODMAN_TMPDIR/mounts.conf for consistency. Same for the other reference above.

@rhatdan rhatdan force-pushed the VENDOR branch 2 times, most recently from 5315c33 to 7197204 Compare January 19, 2024 11:14
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 20, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 27, 2024
@rhatdan
Copy link
Member Author

rhatdan commented Feb 2, 2024

@TomSweeneyRedHat
Copy link
Member

LGTM
@edsantiago, want to take a quick peak?

@umohnani8
Copy link
Member

LGTM

@baude
Copy link
Member

baude commented Feb 2, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 2, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 11c37d5 into containers:main Feb 2, 2024
91 of 92 checks passed
@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 May 3, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators May 3, 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. 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. release-note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants