Errors with collecting logs for Machine with tests adopted from CAPI

[mboukhalfa]

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

[Rozzii]

/triage accepted

[metal3-io-bot]

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

[Rozzii]

/remove-lifecycle stale

[metal3-io-bot]

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

[Rozzii]

/remove-lifecycle stale
@adilGhaffarDev mentioned that he will check it.

[adilGhaffarDev]

@adilGhaffarDev mentioned that he will check it.

The issue persists. I would not say it's a bug. Failures are in log collection in e2e tests, and failures are not related to actual CAPM3 functionality.

[adilGhaffarDev]

/help