pe 8.11.2024 klo 20.29 Martin-Éric Racine (martin-eric.rac...@iki.fi) kirjoitti:
>
> pe 8. marrask. 2024 klo 20.12 Luca Boccassi (bl...@debian.org) kirjoitti:
> >
> > Source: dhcpcd
> > Version: 1:10.1.0-1
> > Severity: serious
> > User: debian...@lists.debian.org
> > Usertags: flaky
> >
> > Dear maintainer(s),
> >
> > The dhcpcd autopkgtest on amd64 are flaky, and fail roughly half of
> > the runs. As per RT, flaky autopkgtest are RC. Example:
> >
> > 19s autopkgtest [04:11:44]: test timesyncd-ntp-servers-from-dhcp:
> > [-----------------------
> > 220s Preparing virtual interfaces...
> > 220s Actual changes:
> > 220s tx-checksum-ip-generic: off
> > 220s tx-tcp-segmentation: off [not requested]
> > 220s tx-tcp-ecn-segmentation: off [not requested]
> > 220s tx-tcp-mangleid-segmentation: off [not requested]
> > 220s tx-tcp6-segmentation: off [not requested]
> > 220s tx-udp-segmentation: off [not requested]
> > 220s tx-checksum-sctp: off
> > 220s Preparing dnsmasq configuration...
> > 225s Obtaining network configuration for veth1 via dhcp...
> > 255s timed out
> > 256s autopkgtest [04:12:21]: test timesyncd-ntp-servers-from-dhcp:
> > -----------------------]
> > ▾ test timesyncd-ntp-servers-from-dhcp: test results
> > 256s autopkgtest [04:12:21]: test timesyncd-ntp-servers-from-dhcp:  -
> > - - - - - - - - - results - - - - - - - - - -
> > 256s timesyncd-ntp-servers-from-dhcp FAIL non-zero exit status 1
>
> This seemingly is caused by dnsmasq. Acquiring an IP randomly fails
> with a timeout. Putting its maintainer in CC.

Simon,

As per above, dnsmasq routinely fails to respond to a DHCP request,
which breaks autopkgtest for other packages on a random basis.

While I have marked the test as flaky, as per Luca's suggestion, as a
temporary kuldge, I'd really like to get to the bottom of what causes
these random timeouts.

The test I'm currently using is as follows:

https://salsa.debian.org/debian/dhcpcd/-/blob/debian/sid/debian/tests/timesyncd-ntp-servers-from-dhcp?ref_type=heads

Given the above, can you think of any reason why DHCP would randomly
fail to respond within dhcpcd's default 30 seconds timeout?

Thanks!
Martin-Éric

Reply via email to