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

Fix podman network rm (-f) workflow #9622

Merged
merged 1 commit into from
Mar 5, 2021

Conversation

jmguzik
Copy link
Contributor

@jmguzik jmguzik commented Mar 4, 2021

/kind bug

Fix for issue #9632
/closes #9632

In NetworkRm fields from c.Config().Networks are checked to see associated networks. c.Config().Networks is not referring to the runtime and store initial configuration which can be obsolete. It forces to use -f flag if the container is created with network which is later disconnected.

A fix proposes the usage of the runtime data from c.Networks() with special handling of 2 errors which may occur: deleted containers and no associated networks.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 4, 2021
@jmguzik jmguzik force-pushed the network-rm-fix branch 3 times, most recently from 58f61f2 to 98e76e2 Compare March 5, 2021 10:40
@jmguzik jmguzik marked this pull request as ready for review March 5, 2021 14:14
@jmguzik jmguzik marked this pull request as draft March 5, 2021 14:17
@jmguzik jmguzik marked this pull request as ready for review March 5, 2021 14:17
@jmguzik jmguzik marked this pull request as draft March 5, 2021 14:22
@jmguzik jmguzik marked this pull request as ready for review March 5, 2021 14:22
@mheon
Copy link
Member

mheon commented Mar 5, 2021

LGTM
@containers/podman-maintainers PTAL

@jmguzik jmguzik changed the title [WIP] Fix podman network rm (-f) workflow Fix podman network rm (-f) workflow Mar 5, 2021
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 5, 2021
@rhatdan
Copy link
Member

rhatdan commented Mar 5, 2021

/lgtm
/approve

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 5, 2021
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmguzik, 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 Mar 5, 2021
@openshift-merge-robot openshift-merge-robot merged commit 0bac30d into containers:master Mar 5, 2021
@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 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 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.

Podman network rm seems to be broken in some situations
5 participants