You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a ticket for tracking issues related to ipxe/ipxe#1115
Once again Equinix Metal is blocked on updating ipxedust because the latest builds of ipxe don't work on a bunch of our currently deployed fleet. This time the affected machines have intel NICs.
Ideally this ticket will remain open until ipxe/ipxe#1115 is fixed properly.
One option for now is to ship the revert in ipxedust and keep applying the revert until a proper fix lands as we previously did for #115 (mercifully only once until a better workaround appeared). A corresponding PR will appear soon.
The text was updated successfully, but these errors were encountered:
Follow up for #142 that includes a workaround for #143
This once again points us at a commit that I pushed to my fork. Reviewers should verify that the commit looks legit and is correctly a child of the commit it is replacing.
- [x] tested on an affected NIC
This is a ticket for tracking issues related to ipxe/ipxe#1115
Once again Equinix Metal is blocked on updating ipxedust because the latest builds of ipxe don't work on a bunch of our currently deployed fleet. This time the affected machines have intel NICs.
I have tested nshalman/ipxe@0cc8177 (directly on top of ipxe/ipxe@182ee90 which is the commit in #142) as a revert of
nshalman/ipxe@cad1cc6 per the linked upstream ipxe issue.
Ideally this ticket will remain open until ipxe/ipxe#1115 is fixed properly.
One option for now is to ship the revert in ipxedust and keep applying the revert until a proper fix lands as we previously did for #115 (mercifully only once until a better workaround appeared). A corresponding PR will appear soon.
The text was updated successfully, but these errors were encountered: