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

[v4.0] Backport handling of incompatible machines #13560

Merged

Conversation

n1hility
Copy link
Member

@n1hility n1hility commented Mar 18, 2022

This backports the incompatible machine handling PR and 4 other dependent PRs (list below)

NOTE: That this treats all machines created by podman versions older than 4.0.2 + brew as incompatible and must be recreated (Not just 3.x). Since 4.0.0 and 4.0.1 were not released on MacOS, in practice this should not be observed. This is also technically the most correct since #13409 changes the uid of the machine uid to match the host user's uid, impacting compatibility of future 4.x releases that expect this to be the case (e.g. volume mounts using a 4.0.1 created machine won't match)

#13523 - Tolerate old machine (Fixes #13510)
#13562 - Fix type-o and cleanup doc punctuation (requested through review)
#13466 - machine rm -f (Fixes #13448)
#13465 - Improve install message (Fixes #13456)
#13409 - MacOS Improvements - introduces virtfs - shipped post 4.0.2 as a brew 4.0.2 patch

[NO NEW TESTS NEEDED]

baude and others added 3 commits March 18, 2022 15:06
* Enable support of virtfs in Podman and darwin.  At the time of this writing, it requires a special patch not yet included in upstream qemu.
* Prefer to use a specially built qemu to support virtfs.  The qemu is installed under libexec/podman.

[NO NEW TESTS NEEDED]
Signed-off-by: Brent Baude <[email protected]>
If you want to remove a running machine, you can now pass the --force/-f
to podman machine rm and the machine will be stopped and removed without
confirmations.

Fixes: containers#13448

[NO NEW TESTS NEEDED]

Signed-off-by: Brent Baude <[email protected]>
@n1hility n1hility force-pushed the backport-handle-incompatible branch from 0528938 to b1884f0 Compare March 18, 2022 20:54
@TomSweeneyRedHat
Copy link
Member

Can we cherry-pick this, once set, to the v4.0-rhel branch too?

Start in a reduced mode for recovery, warn, and provide instructions to recreate them

Signed-off-by: Jason T. Greene <[email protected]>
@n1hility n1hility force-pushed the backport-handle-incompatible branch from b1884f0 to 6878376 Compare March 18, 2022 22:37
@n1hility n1hility changed the title [v 4.0] Backport handling of incompatible machines [v4.0] Backport handling of incompatible machines Mar 18, 2022
@rhatdan
Copy link
Member

rhatdan commented Mar 19, 2022

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 19, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 19, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: n1hility, 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 Mar 19, 2022
@openshift-merge-robot openshift-merge-robot merged commit 19c8019 into containers:v4.0 Mar 19, 2022
@TomSweeneyRedHat
Copy link
Member

We shouldn't be merging anything into this v4.0 branch or the v4.0-rhel branch for the next week or two.....

@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 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 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