-
Notifications
You must be signed in to change notification settings - Fork 18k
x/build/cmd/makemac: Mac VMs are failing to start due to "Invalid configuration" #23859
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
Comments
Original bug report I should've used was #23856. |
Change https://golang.org/cl/94601 mentions this issue: |
Updates golang/go#23859 Change-Id: Ic7833420b5538f59314afefefb431bfd14355ece Reviewed-on: https://go-review.googlesource.com/94601 Reviewed-by: Andrew Bonventre <[email protected]>
Change https://golang.org/cl/95735 mentions this issue: |
Updates golang/go#23859 Change-Id: I7e0fed5b17430669a726a8a7bbf8d3efc190034c Reviewed-on: https://go-review.googlesource.com/95735 Reviewed-by: Andrew Bonventre <[email protected]>
Logged in and poked around. It seems our vSphere/vCenter/vWhatever crapped itself and ran out of disk space for something and then went downhill fast into a weird state. The MacStadium folk are cleaning it up. |
MacStadium said they fixed something, but I still see 5 alerts. But upon poking around more, I found that 4 of our 10 physical nodes had lost their connections to the shared NFS datastore. I had to manually remount those: No clue why they became unmounted or why manual action was required to repair it. But it all seems to be working again, even with VMware still alerting about stuff: I'm following up with MacStadium about that. (https://portal.macstadium.com/tickets/47331) /cc @andybons |
And I see all 20 back up & connected. I'll re-enable trybots. |
Seems like this issue is fixed, so closing. |
Half of our Mac VMs aren't running.
On our Mac VMware cluster, on the Linux VM that runs x/build/cmd/makemac in a systemd unit:
Notice all the
govc: Invalid configuration for device '0'.
.Why did this start failing? This has been running unmodified for about 18 months.
Investigate.
/cc @andybons @mdempsky @aclements
The text was updated successfully, but these errors were encountered: