Nir Soffer <nsof...@redhat.com> writes: > On Tue, Nov 16, 2021 at 9:43 PM Milan Zamazal <mzama...@redhat.com> wrote: >> >> Hi, > >> >> putting recently experienced problems with OST runs failures aside, I >> wonder about what currently happens in gerrit on gating. For instance in >> https://gerrit.ovirt.org/c/vdsm/+/117523/6: >> >> - OST OST -1 >> Patch Set 6: OST-1 >> https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger1/4579 : >> Looking for build artifacts for OST. >> ci build >> >> * Why setting OST-1 when looking for a build? >> >> - Jenkins CI >> Patch Set 6: >> >> No Builds Executed >> >> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/30672/ : >> To avoid overloading the infrastructure, a whitelist for >> running gerrit triggered jobs has been set in place, if >> you feel like you should be in it, please contact infra at >> ovirt dot org. >> >> * OST not allowed to trigger builds? > > This is caused by the same DNS issue.
I see, thanks for identifying the cause. It happened to me again today in https://gerrit.ovirt.org/c/vdsm/+/117543. Did anybody see a response from infra on the DNS issue or does anybody know what can be done about it? It disrupts our CI significantly last days. > I see this in many builds: > > [2021-11-18T16:38:43.034Z] error: RPC failed; result=6, HTTP code = 0 > [2021-11-18T16:38:43.034Z] fatal: The remote end hung up unexpectedly > [2021-11-18T16:38:43.530Z] scripts/whitelist_filter.sh > [2021-11-18T16:38:43.530Z] Initialized empty Git repository in > /home/jenkins/agent/workspace/vdsm_standard-check-patch/jenkins-whitelist/.git/ > [2021-11-18T16:38:43.530Z] Fetching whitelist repo from > https://gerrit.ovirt.org/jenkins-whitelist... > [2021-11-18T16:39:05.682Z] fatal: unable to access > 'https://gerrit.ovirt.org/jenkins-whitelist/': Could not resolve host: > gerrit.ovirt.org; Unknown error > User nsof...@redhat.com is not whitelisted > > Looks like the script fail to get clone the whitelist repo, and then > instead of failing > try to check if the current user is in the non-existing whitelist file. > >> >> - OST OST +1 >> Patch Set 6: OST+1 >> >> https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger1/4583 : >> start OST for >> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/30681/ >> >> * Shouldn't OST set OST+1 after it runs rather than when it starts? >> >> Is there any explanation of these phenomenons? >> >> Thanks, >> Milan >> _______________________________________________ >> Devel mailing list -- devel@ovirt.org >> To unsubscribe send an email to devel-le...@ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/IMRYKBROJXKU3EQAQYNQBJ67CJSXKWWD/ _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZJZSN2AJOYLSCGEUJADTC2556YDTWEFS/
