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

podman play kube apply correct log driver #10044

Merged
merged 1 commit into from
Apr 15, 2021

Conversation

Luap99
Copy link
Member

@Luap99 Luap99 commented Apr 15, 2021

The --log-driver flag was silently ignored by podman play kube. This
regression got introduced during the play kube rework.
Unfortunately the test for this was skipped for no good reason.

Fixes #10015

The --log-driver flag was silently ignored by podman play kube. This
regression got introduced during the play kube rework.
Unfortunately the test for this was skipped for no good reason.

Fixes containers#10015

Signed-off-by: Paul Holzinger <[email protected]>
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99

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 Apr 15, 2021
@Luap99
Copy link
Member Author

Luap99 commented Apr 15, 2021

@edsantiago
Copy link
Member

@Luap99 thanks for the heads-up. This is pretty unfortunate: if I interpret it correctly the container is up, and thinks it is bound to the port, so the failure is in the networking glue. @baude is probably the best person to poke into this but his availability today is limited. Maybe tomorrow...

@edsantiago
Copy link
Member

edsantiago commented Apr 15, 2021

Wow - failed again

@edsantiago
Copy link
Member

Two flakes. Restarted. Opened #10046 to deal with them.

@edsantiago
Copy link
Member

LGTM

1 similar comment
@mheon
Copy link
Member

mheon commented Apr 15, 2021

LGTM

@mheon
Copy link
Member

mheon commented Apr 15, 2021

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2021
@openshift-merge-robot openshift-merge-robot merged commit 81ce39f into containers:master Apr 15, 2021
@Luap99 Luap99 deleted the fix-10015 branch April 15, 2021 19:03
@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.

Log type not passed to containers by 'play kube --log-driver=journald'
5 participants