Alias lab AMD server support #149
Conversation
|
intended to resolve issue 147 |
|
That is what I currently use for the lab and tested working.
~ Thanks,
Chris
…On Wed, Dec 2, 2020 at 8:56 AM Ben England ***@***.***> wrote:
intended to resolve issue 147
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AG3IDEHOISWZ4M3CLSLX2YTSSZBSLANCNFSM4UKQ2RXQ>
.
|
|
-t director now works on both 7525 nodes, after I did a racreset. Previously it only worked on 1 of the 2. However, the boot order displayed does not match the specified boot order (very close though). Why would this happen? Here is the log of the results. I think this PR can be merged now. |
|
I got this error below from jetpack while it was trying to set -t director. The badfish error was "Boot order modification is not supported by this host"! So if we can't change the boot order, that's not good, unless we do not need to change boot order, and in that case we shouldn't be requesting it. So which is it? However, a minute later I tried doing exactly what jetpack was doing directly with badfish and got the message that it was already in director mode. Ughh. So I'll try putting a 2-minute delay in the script to see if it was a timing-related thing caused by --racreset. @QuantumPosix @sadsfae @grafuls what do you think? EDITING for sanitiation reasons |
|
Thanks for submitting this, can you please submit it to the |
|
@bengland2 disregard, @QuantumPosix has batched up a PR for this here: |
Do not merge yet, needs some more testing, although badfish accepts this file as syntactically correct.
This change was suggested by Chris Enright to support the new AMD servers in the Alias lab. I came across this problem because these servers were assigned to me in cloud12, and the servers are
e20-{h25-7425,h27-7425,h29-7525,h31-7525}.example.com
@QuantumPosix does this look ok?