[bug] ibm-power: job containers run at MTU 1500 on a 1450 network

Aperta
#954 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

@atishay-kasliwal ci sta già lavorando.

Dal 10/11/2026.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, linux

Direzione di ricerca

Start by finding where the setup reads network_mtu and where it passes --docker-network-mode podman, since the payload says the shared podman network ignores the runner key. Reproduce on a host whose default route is 1450 and compare podman0 against ip link show inside a job container. Done means the job network reports 1450 in both checks, and the provisioning output prints the detected value. Coordinate with #944 first, because both changes must share one source of the MTU.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug provider/IBMCLOUD
Problem

Job containers on an IBM Power (PowerVS) runner run with a 1500 MTU while the private network carries 1450. Small requests work and large transfers stall: an image pull or a package install hangs for minutes and the job trace shows no error line, because DNS and ping succeed.

The runner registers with no network_mtu, so the key is absent and the executor falls back to 1500. On our fleet the key reads 1450 and the packets are still 1500, because the runner is registered with --docker-network-mode podman (see #944). With a shared network the executor never creates a network for the job, so [runners.docker] network_mtu has no effect. The actual value comes from the podman bridge:

Item Value
underlay MTU 1450
podman0 MTU 1500
network_mtu in config.toml 1450

This issue replaces the earlier request to set network_mtu with the runner key. That key is inert under network_mode = podman.

Proposal
  • Detect the MTU of the default-route interface during setup.
  • Apply it to the network the jobs use:
    • the netavark mtu option on the default podman network, or
    • the bridge interface, if the network is created by the image.
  • When the setup creates the network explicitly, pass the value at creation time. A network created earlier at 1500 keeps 1500 until it is recreated, and recreating it needs no running container.
  • Keep network_mtu in step as well, so a setup without --docker-network-mode podman is correct too.
  • Print the detected value and the resulting bridge MTU in the provisioning output.

Related: #944 pins job containers to the shared podman network and adds a doc step that compares the two MTUs. That step is how this gap was found. The two changes should agree on one source of truth for the value.

Acceptance
  • On a host whose default route runs at 1450, the job network carries 1450 and ip link show inside a job container reports 1450.
  • A large transfer inside a job completes without a stall.
  • The provisioning output names the detected value.
Lingua principale
Go
Stelle
25
Fork
41
Merge medio
5g 3h
PR unite (30g)
16

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di redhat-developer/mapt

Tutte le issue di redhat-developer/mapt

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.