RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1622767 - mmkubernetes - deletion of pod causes logs to stop flowing
Summary: mmkubernetes - deletion of pod causes logs to stop flowing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rsyslog
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Jiří Vymazal
QA Contact: Dalibor Pospíšil
URL:
Whiteboard:
Depends On: 1622768
Blocks: 1648377 1649308
TreeView+ depends on / blocked
 
Reported: 2018-08-28 02:11 UTC by Rich Megginson
Modified: 2019-08-19 10:35 UTC (History)
6 users (show)

Fixed In Version: rsyslog-8.24.0-37.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1622768 (view as bug list)
Environment:
Last Closed: 2019-08-06 12:48:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rsyslog rsyslog issues 2949 0 None closed mmkubertnetes: action fails preparation cycle if kubernetes API destroys resource during bootup sequence 2020-01-27 13:22:29 UTC
Red Hat Product Errata RHSA-2019:2110 0 None None None 2019-08-06 12:48:36 UTC

Description Rich Megginson 2018-08-28 02:11:26 UTC 
Description of problem:
If a pod is deleted after it writes some logs but before rsyslog can query the Kubernetes API server for the pod metadata, mmkubernetes gets an error 404 from the Kubernetes API server and logs stop flowing.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 16 errata-xmlrpc 2019-08-06 12:48:13 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:2110
Note You need to log in before you can comment on or make changes to this bug.