from running a quick check, all our physical slaves are running with the new kernel
> for slave in $(cat ~/Documents/phx-slaves); do
> echo "$slave: "
> ssh "$slave" "uname -r"
> done
ovirt-srv17.phx.ovirt.org:
3.10.0-693.11.6.el7.x86_64
ovirt-srv25.phx.ovirt.org:
3.10.0-693.11.6.el7.x86_64
ovirt-srv21.phx.ovirt.org:
3.10.0-693.11.6.el7.x86_64
ovirt-srv22.phx.ovirt.org:
3.10.0-693.11.6.el7.x86_64
ovirt-srv23.phx.ovirt.org:
3.10.0-693.11.6.el7.x86_64
ovirt-srv26.phx.ovirt.org:
3.10.0-693.11.6.el7.x86_64
ovirt-srv05.phx.ovirt.org:
3.10.0-693.11.6.el7.x86_64
ovirt-srv20.phx.ovirt.org:
3.10.0-693.11.6.el7.x86_64
ovirt-srv19.phx.ovirt.org:
3.10.0-693.11.6.el7.x86_64
ovirt-srv04.phx.ovirt.org:
3.10.0-693.11.6.el7.x86_64
ovirt-srv18.phx.ovirt.org:
3.10.0-693.11.6.el7.x86_64

 

On Sun, Jan 21, 2018 at 10:45 AM, Daniel Belenky <dbelenky@redhat.com> wrote:
The kernel version on srv25 is 3.10.0-693.11.6.el7.x86_64 which seems to be the latest.
I have tested it on another slave yet.

On Sun, Jan 21, 2018 at 10:37 AM, Eyal Edri <eedri@redhat.com> wrote:
Can you check if the kernel is upgraded there and also if it works on other slaves?

On Jan 21, 2018 10:32, "Daniel Belenky" <dbelenky@redhat.com> wrote:
Which slave is the upgraded slave?
It seems that this issue still persists on srv25
Is there a Jira ticket we can follow?

On Sun, Jan 21, 2018 at 8:51 AM, Eyal Edri <eedri@redhat.com> wrote:
Gal,
Can you check if this happens on the upgraded slave? how soon can we release the fixed lago-ost-plugin with support for the new CPU type?

On Fri, Jan 19, 2018 at 6:05 PM, Dafna Ron <dron@redhat.com> wrote:
Hi,

Please note that this time the patch failed on unsupported cpu type:

Unsupported CPU model: Haswell-noTSX-IBRS. Supported models: IvyBridge,Westmere,Skylake,Penryn,Haswell,Broadwell,Nehalem,Skylake-Client,Broadwell-noTSX,Conroe,SandyBridge,Haswell-noTSX

Thanks, 
Dafna

---------- Forwarded message ----------
From: oVirt Jenkins <jenkins@ovirt.org>
Date: Fri, Jan 19, 2018 at 3:33 PM
Subject: [CQ]: 86552,1 (ovirt-log-collector) failed "ovirt-4.2" system tests
To: infra@ovirt.org


Change 86552,1 (ovirt-log-collector) is probably the reason behind recent
system test failures in the "ovirt-4.2" change queue and needs to be fixed.

This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.

For further details about the change see:
https://gerrit.ovirt.org/#/c/86552/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/261/
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra


_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra




--

Eyal edri


MANAGER

RHV DevOps

EMEA VIRTUALIZATION R&D


Red Hat EMEA

TRIED. TESTED. TRUSTED.
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)

_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra




--

DANIEL BELENKY

RHV DEVOPS




--

DANIEL BELENKY

RHV DEVOPS




--

DANIEL BELENKY

RHV DEVOPS