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

e2e: Fix logging during test failure #454

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

RamLavi
Copy link
Member

@RamLavi RamLavi commented Jan 15, 2025

What this PR does / why we need it:
logs are not printed correctly as shown on #452
This PR is fixing that

Special notes for your reviewer:

Release note:

NONE

Currently during test fail, the kubemacpool manager pod logs are
not printed because the container name is not specified.
- Changing method of extracting the logs using req.Stream.
- Changing to print all container logs.
- Fix minor print formatting.

Signed-off-by: Ram Lavi <[email protected]>
In cases where the e2e is run a bigger context (like CNAO tier1 [0]) -
The failed tests logger should only catch kubemacpool related tests.

Signed-off-by: Ram Lavi <[email protected]>
@kubevirt-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from ramlavi. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@RamLavi
Copy link
Member Author

RamLavi commented Jan 15, 2025

@oshoval will help us debug the flake we saw on CNAO. PTAL when you have the time

@RamLavi
Copy link
Member Author

RamLavi commented Jan 15, 2025

/cherry-pick release-0.45

@kubevirt-bot
Copy link
Collaborator

@RamLavi: once the present PR merges, I will cherry-pick it on top of release-0.45 in a new PR and assign it to you.

In response to this:

/cherry-pick release-0.45

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants