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.

Sign up for GitHub

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

Jump to bottom

[flake] Docker restart fails in BMO e2e #1783

Open
tuminoid opened this issue Jun 12, 2024 · 3 comments
Open

[flake] Docker restart fails in BMO e2e #1783

tuminoid opened this issue Jun 12, 2024 · 3 comments
Labels
kind/flake Categorizes issue or PR as related to a flaky test. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@tuminoid
Copy link
Member

Which jobs are flaking?

BMO e2e tests

Which tests are flaking?

Randomly any of e2e variants

Since when has it been flaking?

Since moving to GH actions.

Jenkins link

https://github.com/metal3-io/baremetal-operator/actions/runs/9477201984/job/26111334840

Reason for failure (if possible)

n 12 05:29:25 minikube systemd[1]: docker.service: Deactivated successfully.
Jun 12 05:29:25 minikube systemd[1]: Stopped Docker Application Container Engine.
Jun 12 05:29:25 minikube systemd[1]: Starting Docker Application Container Engine...
Jun 12 05:29:25 minikube dockerd[796]: time="2024-06-12T05:29:25.668001724Z" level=info msg="Starting up"
Jun 12 05:30:25 minikube dockerd[796]: failed to start daemon: failed to dial "/run/containerd/containerd.sock": failed to dial "/run/containerd/containerd.sock": context deadline exceeded
Jun 12 05:30:25 minikube systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jun 12 05:30:25 minikube systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 12 05:30:25 minikube systemd[1]: Failed to start Docker Application Container Engine.

Anything else we need to know?

No response

Label(s) to be applied

/kind flake
@metal3-io-bot metal3-io-bot added kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Jun 12, 2024
@tuminoid tuminoid changed the title Docker restart fails in BMO e2e [flake] Docker restart fails in BMO e2e Jun 12, 2024
@Rozzii
Copy link
Member

Rozzii commented Jun 12, 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 Jun 12, 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 Sep 10, 2024
@tuminoid
Copy link
Member Author

tuminoid commented Oct 4, 2024

/remove-lifecycle stale
/lifecycle frozen

This is very much still happening.

@metal3-io-bot metal3-io-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/flake Categorizes issue or PR as related to a flaky test. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tuminoid @Rozzii @metal3-io-bot