Fix podman network rm (-f) workflow #9622
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/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.