Skip to content

Issue with latest builds of iPXE on Mellanox ConnectX #115

@nshalman

Description

@nshalman

Current status

This is a ticket for tracking issues related to ipxe/ipxe#1091

There is a simple undef workaround that we can ship in our configuration until the upstream bug is fully resolved:
ipxe/ipxe#1091 (comment)

#undef NET_PROTO_EAPOL

We should ship that workaround until the upstream issue is resolved.

Original report

This is a ticket for tracking issues related to ipxe/ipxe#1091
For additional reference, netbootxyz/netboot.xyz#1359

Basically Equinix Metal is blocked on updating ipxedust because the latest builds of ipxe don't work on a bunch of our currently deployed fleet.

I have tested nshalman/ipxe@fbc3b4a as a revert of ipxe/ipxe@8b14652

Ideally this ticket will remain open until ipxe/ipxe#1091 is fixed properly.
One option for now is to ship the revert in ipxedust and keep applying the revert until a proper fix lands.
Otherwise I can maintain a fork for Equinix in the meantime.

But I do imagine other consumers of ipxedust with similar hardware will run into a similar issue in the meantime...

I intend to open a PR that would ship the revert, but I completely understand if the tinkerbell project chooses not to merge it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions