-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
System planned downtime: Equinix aarch64 systems #2808
Comments
NOTE: I have provisioned (but not yet configured) two machines which could be used if we want to have backups during this time if they can be set up before this happens. Both of these are 8 core, 16GB, and 80GB disk (the disk may be the limiting factor for how many images we can host on them in parallel)
|
Setup here https://ci.adoptopenjdk.net/computer/build-osuosl-ubuntu2204-aarch64-1/ Dockerstatic machines (cant get them to connect yet) |
build-osuosl-ubuntu2204-aarch64-1 fails to build a jdk11 aarch64 binary https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-aarch64-temurin/142/console
related #2257 |
I cant get the dockerstatic machines to connect to jenkins. The correct public key is on the container, iptables looks fine (cant see any reason the packets would get dropped when comparing it to a working dockerhost machine). On dockerhost-osuosl-ubuntu2204-aarch64-1
From my workstation
Same goes for dockerstatic containers on the build-osuosl machine |
The build-osuosl machine can run tests thankfully https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/6116/console |
I've configured them so that they connect to jenkins, as opposed to jenkins connecting to the machines. Should work until I can resolve the connectivity issues |
Equinix systems are now back online again (Same IPs so no extra work needed on our part) |
I'm going to close this but it sounds like we'll need some remedial work on the OSUOSL systems which can be covered elsewhere. |
Equinix are migrating systems in their data centers starting on the 14th of November. This will take up to four days to complete. We have been asked to shut the machines down by end of day on the 13th.
No backups will be performed, but the expectation is that the machines will come back as-is, although potentially with a different IP address.
FYI @Haroon-Khel
The text was updated successfully, but these errors were encountered: