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

Errors with collecting logs for Machine with tests adopted from CAPI #1609

Open
mboukhalfa opened this issue Apr 22, 2024 · 3 comments
Open
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@mboukhalfa
Copy link
Member

What steps did you take and what happened:
Clusterctl upgrade test reused from CAPI persistently show the errors:

Failed to get logs for Machine clusterctl-upgrade-w6i26f-4d75h, Cluster clusterctl-upgrade-8o9j0d/clusterctl-upgrade-w6i26f: error finding the serial log: stat /var/log/libvirt/qemu/clusterctl_upgrade_8o9j0d/node_1-serial0.log: no such file or directory
05:56:59  Failed to get logs for Machine clusterctl-upgrade-w6i26f-xm89z-rfgwr, Cluster clusterctl-upgrade-8o9j0d/clusterctl-upgrade-w6i26f: error finding the serial log: stat /var/log/libvirt/qemu/clusterctl_upgrade_8o9j0d/node_0-serial0.log: no such file or directory
05:56:59  Failed to get infrastructure logs for Cluster clusterctl-upgrade-8o9j0d/clusterctl-upgrade-w6i26f: CollectInfrastructureLogs not implemented 

This msg seen also when trying to reuse other tests like md-remediation

What did you expect to happen:
Show that machine logs got successfully collected !

Anything else you would like to add:

Upon inspection of the collected tarball, I found the machine log files under the qemu folder. However, I am unsure if they were collected correctly despite the error message in the logs.

/kind bug

@metal3-io-bot metal3-io-bot added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Apr 22, 2024
@mboukhalfa mboukhalfa changed the title Error msg with collecting logs for Machine when reusing CAPI tests Errors with collecting logs for Machine with tests adopted from CAPI Apr 22, 2024
@Rozzii
Copy link
Member

Rozzii commented Apr 24, 2024

/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Apr 24, 2024
@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 23, 2024
@Rozzii
Copy link
Member

Rozzii commented Jul 24, 2024

/remove-lifecycle stale

@metal3-io-bot metal3-io-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Status: Backlog
Development

No branches or pull requests

3 participants