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

Include CNI networks in inspect output when not running #7983

Merged

Conversation

mheon
Copy link
Member

@mheon mheon commented Oct 9, 2020

We were only including the CNI Network fields in the output of podman inspect when the container was not running. It's simple enough to fix (populate with empty structs, since we can't fill anything without a CNI response to get IP address assigned, etc).

This is necessary for Docker compatibility.

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mheon

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 Oct 9, 2020
@mheon
Copy link
Member Author

mheon commented Oct 9, 2020

@baude PTAL

@jwhonce
Copy link
Member

jwhonce commented Oct 9, 2020

LGTM once tests are happy

@TomSweeneyRedHat
Copy link
Member

changes LGTM, but tests look to be having some real issues.

We were only including the CNI Network fields in the output of
`podman inspect` when the container was not running. It's simple
enough to fix (populate with empty structs, since we can't fill
anything without a CNI response to get IP address assigned, etc).

This is necessary for Docker compatibility.

Signed-off-by: Matthew Heon <matthew.heon@pm.me>
@mheon mheon force-pushed the inspect_network_not_running branch from 41b4bc3 to 77033c4 Compare October 10, 2020 00:20
@mheon
Copy link
Member Author

mheon commented Oct 12, 2020

Restarting tests, looks like it was mostly flakes in uploading artifacts?

@baude
Copy link
Member

baude commented Oct 12, 2020

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 12, 2020
@baude
Copy link
Member

baude commented Oct 12, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 12, 2020
@mheon
Copy link
Member Author

mheon commented Oct 12, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 12, 2020
@openshift-merge-robot openshift-merge-robot merged commit e8f48a1 into containers:master Oct 12, 2020
@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 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 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.

6 participants