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

x/build: one linux/arm builder (scaleway-prod-15) missing #35572

Closed
cagedmantis opened this issue Nov 13, 2019 · 2 comments
Closed

x/build: one linux/arm builder (scaleway-prod-15) missing #35572

cagedmantis opened this issue Nov 13, 2019 · 2 comments
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Unreleased

Comments

@cagedmantis
Copy link
Contributor

From https://farmer.golang.org/#health:

scaleway-prod-15 missing, never seen (at least 37h51m8s)
1 machines missing, 2% of capacity

Only 1 machine out of 50 is missing. At first I thought it was an issue similar to #32801 where destroying the machine would force the x/build/cmd/scaleway deamon to recreate a functioning vm. The deamon did recreate the machine. The new machine is exhibiting the same behavior.

The rundockerbuildlet daemon is running properly. The metadata is correctly populated. The buildlet appears to be running but it has not negotiated a connection with farmer.golang.org.

I will continue the investigation.
@cagedmantis cagedmantis self-assigned this Nov 13, 2019
@gopherbot gopherbot added this to the Unreleased milestone Nov 13, 2019
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Nov 13, 2019
@cagedmantis cagedmantis added the NeedsFix The path to resolution is known, but the work has not been done. label Nov 21, 2019
@cagedmantis
Copy link
Contributor Author

This issue was caused because of a mismatch between the master key used by the coordinator and scaleway. Both key's now match. We are looking into how to prevent this from happening in the future.

@cagedmantis
Copy link
Contributor Author

This master keys have been fixed and the documentation reflects it.

@golang golang locked and limited conversation to collaborators Nov 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
2 participants
@cagedmantis @gopherbot