| Summary: | Fedora autobuilders have intermittent network error to git.yoctoproject.org in oe-selftest | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Richard Purdie <richard.purdie> |
| Component: | autobuilder | Assignee: | Michael Halstead <mhalstead> |
| Status: | VERIFIED FIXED | QA Contact: | Jose Perez C <jose.perez.carranza> |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | infras.ab.watcher, Infras.watcher, jose.perez.carranza, joshuagloe, leonardo.sandoval.gonzalez, mhalstead, pidge |
| Version: | 2.1 | ||
| Target Milestone: | 2.3 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Richard Purdie
2016-09-06 10:02:29 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1317691 seems potentially related. The export variable mentioned there doesn't help. (In reply to comment #1) > https://bugzilla.redhat.com/show_bug.cgi?id=1317691 seems potentially > related. The export variable mentioned there doesn't help. Just to confirm RP observation, the export mentioned at [1] did not help: $ export NSS_STRICT_NOFORK=DISABLED $ while true; do git -c core.fsyncobjectfiles=0 ls-remote https://git.yoctoproject.org/git/dbus-wait | grep -v 6cc6; done fatal: unable to access 'https://git.yoctoproject.org/git/dbus-wait/': A PKCS #11 module returned CKR_DEVICE_ERROR, indicating that a problem has occurred with the token or slot. This is on a F24 machine. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1317691#c2 (In reply to comment #1) > https://bugzilla.redhat.com/show_bug.cgi?id=1317691 seems potentially > related. The export variable mentioned there doesn't help. Richard, this seems to be a problem with the distro where building is done, in this case Fedora. There is a proposed fix [1], but in case this solves the problem (which does not seem to fix all scenarios [2], except the sample case) on host, how do we handle this case? we can patch the packages we control but of course we can not patch distros. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1317691#c13 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1317691#c16 The proposed patch (https://bugzilla.redhat.com/attachment.cgi?id=1144900&action=diff) did not solve the issue on the AB machine so moving the status to WaitForUpstream. As mentioned, the bug has already being filed on the redhat bugzilla tracker and has not been fixed. The simplified scenario in our case was reported in the main bug tracker page, giving another simple way to reproduce it. https://bugzilla.redhat.com/show_bug.cgi?id=1317691#c29 Last change from bugzilla's RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1317691 errata-xmlrpc <errata-xmlrpc@redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|VERIFIED |RELEASE_PENDING Michael, assigning this bug to you because Red Hat have provided a set of updates that fixes the issue on the fedora(s) builder(s) Please follow the recommendations from: https://bugzilla.redhat.com/show_bug.cgi?id=1317691#c34 Reading the advisories it appears that this issue should be solved with the newest set of Fedora packages. They have been installed so I think this is resolved. Verified on local autobuilders and failure was not observed Dec 08 14:31 dae00fbb913c... Dec 08 08:38 18e4688bd52e... Dec 07 18:03 e38775a1d82e... Dec 07 12:16 e38775a1d82e... Dec 07 10:04 adb34b8ddcd8... Dec 06 18:18 9e63f81c78e2... Dec 06 12:24 9e63f81c78e2... |