Hi, check-merged has failed for my merged Vdsm patch yesterday: http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1811/ The error was: 14:36:12 @ Start specified VMs: Success (in 0:00:06) 14:36:12 + prepare_and_copy_yum_conf 14:36:12 ++ mktemp XXXXXX 14:36:12 + local tempfile=yd2rya 14:36:12 + cat /etc/yum/yum.conf 14:36:12 + grep -v reposdir 14:36:12 + /home/jenkins/workspace/vdsm_master_check-merged-el7-x86_64/vdsm/automation/exclude_from_conf 'vdsm*' 14:36:12 + lago copy-to-vm vdsm_functional_tests_host-el7 yd2rya /etc/yum/yum.conf 14:36:13 current session does not belong to lago group. 20:31:02 Build timed out (after 360 minutes). Marking the build as failed. So it's a false alert, could the failure be prevented? Thanks, Milan
On 26 May 2017 at 10:49, Milan Zamazal <mzamazal@redhat.com> wrote:
Hi, check-merged has failed for my merged Vdsm patch yesterday: http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1811/
The error was:
14:36:12 + lago copy-to-vm vdsm_functional_tests_host-el7 yd2rya /etc/yum/yum.conf
The following is not an error message is a warning that always shows up because the user in mock is not a member of the 'lago' group (its harmless though, b/c it is 'root' so doesn't need to be a member).
14:36:13 current session does not belong to lago group.
Note the huge time gap between these two lines:
20:31:02 Build timed out (after 360 minutes). Marking the build as failed.
So it's a false alert, could the failure be prevented?
It not a false alert, something is happening and is causing the system the be stuck for over 6 hours. Need to look for what is happening in the other logs. Note that with Lago stuff can be happening on the VMs without any messages going the the STDOUT, so the Jenkins job output screen is not the best place to look for reasons for failures on Lago. BTW, this has nothing to do with OST other then also using Lago. Adding Yaniv who is more familiar with the vdsm check-merged job. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
Another "Build timed out": http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1870/
adding infra-support to open a ticket. On Thu, Jun 1, 2017 at 10:28 AM, Milan Zamazal <mzamazal@redhat.com> wrote:
Another "Build timed out":
http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1870/ _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
On 1 June 2017 at 10:28, Milan Zamazal <mzamazal@redhat.com> wrote:
Another "Build timed out":
http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1870/
14:54:23 Removing the used loop devices... 20:54:23 Build timed out (after 360 minutes). Marking the build as failed. Any idea what might be holding the loop devices? -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
Another "Build timed out": http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1967/consol...
I clicked on 'keep forever' so it won't go away if we want to debug. On Wed, Jun 14, 2017 at 9:57 AM, Milan Zamazal <mzamazal@redhat.com> wrote:
Another "Build timed out":
http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7- x86_64/1967/console _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
participants (3)
-
Barak Korren -
Eyal Edri -
Milan Zamazal