-
Notifications
You must be signed in to change notification settings - Fork 141
Collect kubelet logs before synchronization #3555
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
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
9e947d6 to
cf627a8
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/259992f6577b4fdeb978a4b3188ba530 ❌ openstack-k8s-operators-content-provider RETRY_LIMIT Host unreachable in 2h 27m 55s |
cf627a8 to
6eeb20f
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/cf5af774a6834a5d8d5d983c282e459d ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 48m 30s |
6eeb20f to
0b60901
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/773c8a7a6e3a4bcaa807a50f182f8bc8 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 44m 44s |
|
recheck |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/b83678c1d7b14f46b5ffab9b06cd4d31 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 08m 58s |
|
recheck |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/33900cdf75284ccb87cbb52c57229219 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 05m 42s |
The task that was responsible for collecting kubelet logs was done after the synchronization, so in some jobs we did not get kubelet service logs. Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
0b60901 to
426df59
Compare
| work_dir: "{{ ansible_user_dir }}/zuul-output/logs" | ||
| ansible.builtin.include_role: | ||
| name: fetch-output | ||
| ignore_errors: true # noqa: ignore-errors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(non-blocking) question: do we want to ignore here errors? I'm OK with this, but should we ignore errors in L 156?
| args: | ||
| chdir: "{{ ansible_user_dir }}/zuul-output/logs/" | ||
|
|
||
| - name: Compress logs bigger than 2MB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(non-blocking) thought: I thinks now this is a great candidate to pull out this two tasks somewhere to be imported.
If you agree I can work in the task.
The task that was responsible for collecting kubelet logs was done after the synchronization, so in some jobs we did not get kubelet service logs.