Need a notification on using start.sh #44

Activity

1. data-angel

   closed this as completedin #45on Oct 12, 2026
2. data-angel commented on Oct 12, 2026

   

   data-angel

   on Oct 12, 2026

   Contributor

   More actions

   Thanks for the report, @HKMist. You were right: start.sh assumed the cable was on the first port.

   Fixed in #45. start.sh now finds the fabric port on each Spark by itself:

   • it looks for RoCE ports whose link is up and that have an IPv4 address;
   • it picks the pair on the same subnet, which is the cable between your two Sparks;
   • it prints the choice before starting. For your setup, expect something like:

   == fabric: rocep1s0f1 (enp1s0f1np1, <address>) here, rocep1s0f1 (enp1s0f1np1, <address>) on <worker>; set FABRIC_HCA in .env to choose another port
   

   To get it, run git pull and then ./start.sh. The image is unchanged, so nothing new is downloaded or built.

   If you had already set FABRIC_HCA=rocep1s0f1 in .env to work around it, that still works and still overrides the detection. If the detection picks the wrong port, please let us know here.