- Devel - oVirt List Archives

OST fails with LagoDeployError: ... failed with status 1 on lago-basic-suite-master-host-0
by Nir Soffer 04 Feb '19

04 Feb '19

I had 2 OST failure today with the same infrastructure failure, before running any test: + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' otopi-debug-plugins cronie Error: Package: 7:device-mapper-event-1.02.149-10.el7_6.3.x86_64 (alocalsync) Requires: device-mapper = 7:1.02.149-10.el7_6.3 Installed: 7:device-mapper-1.02.149-10.el7_6.2.x86_64 (installed) device-mapper = 7:1.02.149-10.el7_6.2 ret=1 + echo 'install failed with status 1' + exit 1 - STDERR Links to failed builds: - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… - https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_man… The last successful build was at Feb 1: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4004/ The trend show that all builds failed since Feb 3 9:02 am. https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend This issue is blocking 4.3 work on 4k support. Nir

2 3

Re: [rhev-devel] u/s errors during update
by Roni Eliezer 03 Feb '19

03 Feb '19

Adding devel(a)ovirt.org Thx Roni On Sun, Feb 3, 2019 at 2:31 PM Eyal Edri <eedri(a)redhat.com> wrote: > you might want to ask on devel(a)ovirt.org and not rhev-devel which is > downstream and might be less monitored. > > On Sun, Feb 3, 2019 at 11:10 AM Roni Eliezer <reliezer(a)redhat.com> wrote: > >> Hi >> I got the following errors (see below) when I try to upgrade 4.3 u/s >> Any idea? >> >> --> Finished Dependency Resolution >> Error: Package: 1:openvswitch-2.10.1-1.el7.x86_64 >> (@centos-ovirt43-testing) >> Requires: librte_efd.so.1()(64bit) >> Removing: dpdk-17.11-15.el7.x86_64 (@rhel-extras) >> librte_efd.so.1()(64bit) >> Updated By: dpdk-18.11-2.el7_6.x86_64 (rhel-extras) >> Not found >> Available: dpdk-17.11-7.el7.x86_64 (rhel-extras) >> librte_efd.so.1()(64bit) >> Available: dpdk-17.11-11.el7.x86_64 (rhel-extras) >> librte_efd.so.1()(64bit) >> Available: dpdk-17.11-13.el7.x86_64 (rhel-extras) >> librte_efd.so.1()(64bit) >> Available: dpdk-2.0.0-8.el7.x86_64 (rhel-extras) >> Not found >> Available: dpdk-2.2.0-2.el7.x86_64 (rhel-extras) >> Not found >> Available: dpdk-2.2.0-3.el7.x86_64 (rhel-extras) >> Not found >> Available: dpdk-16.11.2-4.el7.x86_64 (rhel-extras) >> Not found >> Error: Package: 1:openvswitch-ovn-common-2.10.1-1.el7.x86_64 >> (@centos-ovirt43-testing) >> Requires: librte_pmd_softnic.so.1()(64bit) >> Removing: dpdk-17.11-15.el7.x86_64 (@rhel-extras) >> librte_pmd_softnic.so.1()(64bit) >> Updated By: dpdk-18.11-2.el7_6.x86_64 (rhel-extras) >> Not found >> Available: dpdk-17.11-7.el7.x86_64 (rhel-extras) >> librte_pmd_softnic.so.1()(64bit) >> Available: dpdk-17.11-11.el7.x86_64 (rhel-extras) >> librte_pmd_softnic.so.1()(64bit) >> Available: dpdk-17.11-13.el7.x86_64 (rhel-extras) >> librte_pmd_softnic.so.1()(64bit) >> Available: dpdk-2.0.0-8.el7.x86_64 (rhel-extras) >> Not found >> Available: dpdk-2.2.0-2.el7.x86_64 (rhel-extras) >> Not found >> Available: dpdk-2.2.0-3.el7.x86_64 (rhel-extras) >> Not found >> Available: dpdk-16.11.2-4.el7.x86_64 (rhel-extras) >> Not found >> >> > > -- > > Eyal edri > > > MANAGER > > RHV/CNV 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) >

1 0

oVirt on Fedora 28 status update
by Nir Soffer 01 Feb '19

01 Feb '19

Last time we discussed this here, we had only sanlock issue: https://bugzilla.redhat.com/1593853 The bug was fixed upstream about 2 month ago, but the Fedora package was not available. The package is not available yet in Fedora, but we have a build here: https://koji.fedoraproject.org/koji/buildinfo?buildID=1182539 You can install sanlock from this build using: dnf upgrade https://kojipkgs.fedoraproject.org//packages/sanlock/3.6.0/4.fc28/x86_64/py… \ https://kojipkgs.fedoraproject.org//packages/sanlock/3.6.0/4.fc28/x86_64/sa… \ https://kojipkgs.fedoraproject.org//packages/sanlock/3.6.0/4.fc28/x86_64/sa… Hopefully the package will pushed soon to updates-testing repo. With this you can use enable selinux as god intended. But if you update your host to kernel 4.20.4-100, multipath is broken. All multipath devices are not available, and your hosts will probably become non-operational since they report the iSCSI/FC storage domains in problem. The issue was reported here: https://lkml.org/lkml/2018/11/5/398 And we have this Fedora 29 bug: https://bugzilla.redhat.com/1669235 Ben explains it is: The kernel is switching over to use block multiqueue instead of the old request queue. Part of doing this is removing support for the old request queue from device-mapper. Another part is to remove support for the old request queue from the scsi layer. For some reason, the first part got into this fedora kernel, but the second part didn't. It seems to me that since the fedora kernel has removed support for non-blk-mq based devices, I should have been compiled with CONFIG_SCSI_MQ_DEFAULT=y To fix this issue you need to add the scsi_mod.use_blk_mq=Y option to the kernel command line: grubby --args=scsi_mod.use_blk_mq=Y --update-kernel /boot/vmlinuz-4.20.4-100.fc28.x86_64 After reboot, your multipath devices will appear again. Cheers, Nir

2 3

[Ovirt] [CQ weekly status] [01-02-2019]
by Dafna Ron 01 Feb '19

01 Feb '19

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#2) We have no current failures. Last failed job was for ovirt-ansible-hosted-engine-setup due to build-artiacts job on Jan 25. the issue is worked on by Simon Tiraboschi *CQ-Master:* GREEN (#1) There are no current issues in master CQ During the week we had 3 regressions for ovirt-engine 1. Domain version 5 feature was merged but its was not yet supported on vdsm side: https://gerrit.ovirt.org/#/c/96178/ - storage: Added V5 domain format definition. Date failure in CQ: 24-01-2019 test failing: 002_bootstrap.add_master_storage_domain Fix: https://gerrit.ovirt.org/#/c/97262/ - storage: Make default domain verion V4 for 4.3 2. CQ was still failing on create domain v5 after the fix was merged to fix regression #1 https://gerrit.ovirt.org/#/c/96178/ - storage: Added V5 domain format definition. Date failure in CQ: 26-01-2019 test failing: 002_bootstrap.add_secondary_storage_domains Fix: https://gerrit.ovirt.org/#/c/97408/ - storage: V5 is not a latest domain version yet ** first patch fixed the domain create for manual create but via the API the version was available which is why we were still failing on CQ. 3. Added callbacks for MBS disks causing regular disks to use callbacks unnecessarily https://gerrit.ovirt.org/#/c/96815/ - core: set VmDevices properly when creating and attaching We saw this regression once #1 and #2 regressions were fixed. Date first failure detected: 30-01-2019 Fix: https://gerrit.ovirt.org/#/c/97428/ - core: partial revert of 4d439006 Ovirt-engine passed on 31-01-2019 Current running jobs for 4.2 [1] and master [2] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.0.4)
by Tal Nisan 31 Jan '19

31 Jan '19

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.0.3)
by Tal Nisan 30 Jan '19

30 Jan '19

1 0

Planned infra outage - Saturday February 2
by Evgheni Dereveanchin 29 Jan '19

29 Jan '19

Hi everyone, There's a maintenance window planned for this Saturday, February 2 2019 to upgrade network equipment in the PHX datacenter. The change will be implemented during afternoon hours and several oVirt infra services may be unreachable for short periods of time, specifically: * package repositories * Jenkins CI * glance image repo If you have problems accessing project resources during this period or see CI failures please re-try in a couple of hours. The project website and Gerrit code review are not affected by this outage and will continue to function normally. -- Regards, Evgheni Dereveanchin

1 0

imageio failing to build on s390x
by Sandro Bonazzola 29 Jan '19

29 Jan '19

Hi, trying to enable imageio building on s390x (https://gerrit.ovirt.org/96738) for satisfying vdsm deps and got a failure: https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/994//artif… Can you please have a look if I'm missing something to get the build running? Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

4 3

ovirt-engine has been tagged (ovirt-engine-4.2.8.3)
by Tal Nisan 28 Jan '19

28 Jan '19

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.0.2)
by Tal Nisan 28 Jan '19

28 Jan '19

1 0