OCPBUGS-58178: Bump promtail version to 3.4.3 #66518
Conversation
openshift-ci-robot
added
jira/severity-critical
|
@vrutkovs: This pull request references Jira Issue OCPBUGS-58178, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vrutkovs 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 |
openshift-ci
bot
added
the
approved
|
/pj-rehearse 5 |
|
@vrutkovs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
A total of 28272 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@vrutkovs: job(s): 5 either don't exist or were not found to be affected, and cannot be rehearsed |
|
/pj-rehearse more |
|
@vrutkovs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-cgroupsv2 periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-serial |
|
@vrutkovs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
The passing AWS journals don't show any issues with promtail or any sigkills, hopefully that indicates this is helpful (Not sure if this issue is more prevalent on GCP, though, or if AWS is representative as well, since it's a bit racy) |
|
lets run a few GCP tests to be sure |
|
@vrutkovs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse ack |
|
@vrutkovs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@vrutkovs: This pull request references Jira Issue OCPBUGS-58178, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/pj-rehearse pull-ci-openshift-machine-config-operator-main-e2e-gcp-op pull-ci-openshift-machine-config-operator-release-4.20-e2e-gcp-op |
|
@vrutkovs: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@vrutkovs: job(s): either don't exist or were not found to be affected, and cannot be rehearsed |
|
@vrutkovs: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
Hmm, I see the same problem: on the latest failed e2e-gcp-op run. |
Lets see if bumping promtail helps with sigkills on GCP