January 2019 - Devel - oVirt List Archives

[VDSM] Started getting virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired
by Edward Haas 11 Jan '24

11 Jan '24

Hi, I have a VM which acts as an oVirt host with VDSM installed. I use it for testing without connecting it to Engine. Recently VDSM fails to come up and I see this error: Sep 26 17:58:18 localhost libvirtd: 2018-09-26 14:58:18.978+0000: 12176: error : virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired Any hint on how to generate or fetch a new certificate without the help of Engine? Thanks, Edy.

3 5

Error Java SDK Issue??
by Geschwentner, Patrick 02 Apr '21

02 Apr '21

Dear Ladies and Gentlemen! I am currently working with the java-sdk and I encountered a problem. If I would like to retrieve the disk details, I get the following error: Disk currDisk = ovirtConnection.followLink(diskAttachment.disk()); The Error is occurring in this line: [cid:image001.png@01D44537.AF127FD0] The getResponst looks quiet ok. (I inspected: [cid:image002.png@01D44537.AF127FD0] and it looks ok). Error: wrong number of arguments The code is quiet similar to what you published on github (https://github.com/oVirt/ovirt-engine-sdk-java/blob/master/sdk/src/test/jav… ). Can you confirm the defect? Best regards Patrick

6 11

Vdsm: Intention to make ovirt-4.3 branch
by Milan Zamazal 20 Feb '19

20 Feb '19

Hi, I'm going to make ovirt-4.3 Vdsm branch next week. If there are any very important reasons not to make it, please let me know. Thanks, Milan

4 8

[VDSM] Flaky protocol detector test
by Nir Soffer 17 Feb '19

17 Feb '19

Recently this test cause too many random failures. I guess this is the known issue with handling SUBSCRIBE in protocol detector. I posted https://gerrit.ovirt.org/c/97099/ To mark it as broken until we have time to dig deeper ====================================================================== FAIL: test_detect_slow_client_concurrency(True) (protocoldetector_test.AcceptorTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", line 142, in wrapper return f(self, *args) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/protocoldetector_test.py", line 167, in test_detect_slow_client_concurrency self.check_concurrently(self.check_slow_client, use_ssl) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/protocoldetector_test.py", line 266, in check_concurrently self.assertTrue(all(done)) AssertionError: False is not true -------------------- >> begin captured logging << -------------------- 2019-01-19 20:47:16,021 DEBUG (MainThread) [vds.MultiProtocolAcceptor] Creating socket (host='127.0.0.1', port=0, family=2, socketype=1, proto=6) (protocoldetector:225) 2019-01-19 20:47:16,022 INFO (MainThread) [vds.MultiProtocolAcceptor] Listening at 127.0.0.1:46009 (protocoldetector:183) 2019-01-19 20:47:16,023 DEBUG (MainThread) [vds.MultiProtocolAcceptor] Adding detector <protocoldetector_test.Echo object at 0x7f1bb77f8dd0> (protocoldetector:210) 2019-01-19 20:47:16,024 DEBUG (MainThread) [vds.MultiProtocolAcceptor] Adding detector <protocoldetector_test.Uppercase object at 0x7f1bb77f8c90> (protocoldetector:210) 2019-01-19 20:47:16,031 INFO (Thread-61) [ProtocolDetector.AcceptorImpl] Accepted connection from 127.0.0.1:51950 (protocoldetector:61) 2019-01-19 20:47:16,047 INFO (Thread-61) [ProtocolDetector.AcceptorImpl] Accepted connection from 127.0.0.1:51952 (protocoldetector:61) 2019-01-19 20:47:16,048 INFO (Thread-61) [ProtocolDetector.AcceptorImpl] Accepted connection from 127.0.0.1:51954 (protocoldetector:61) 2019-01-19 20:47:16,065 INFO (Thread-61) [ProtocolDetector.AcceptorImpl] Accepted connection from 127.0.0.1:51956 (protocoldetector:61) 2019-01-19 20:47:16,068 INFO (Thread-61) [ProtocolDetector.AcceptorImpl] Accepted connection from 127.0.0.1:51958 (protocoldetector:61) 2019-01-19 20:47:16,069 DEBUG (Thread-61) [ProtocolDetector.Detector] Using required_size=9 (protocoldetector:89) 2019-01-19 20:47:16,097 DEBUG (Thread-61) [ProtocolDetector.Detector] Using required_size=9 (protocoldetector:89) 2019-01-19 20:47:16,099 DEBUG (Thread-61) [ProtocolDetector.Detector] Using required_size=9 (protocoldetector:89) 2019-01-19 20:47:16,107 DEBUG (Thread-61) [ProtocolDetector.Detector] Using required_size=9 (protocoldetector:89) 2019-01-19 20:47:16,109 DEBUG (Thread-61) [ProtocolDetector.Detector] Using required_size=9 (protocoldetector:89) 2019-01-19 20:47:16,574 INFO (Thread-61) [ProtocolDetector.Detector] Detected protocol echo from 127.0.0.1:51950 (protocoldetector:125) 2019-01-19 20:47:17,570 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed out while waiting for data (protocoldetector:94) 2019-01-19 20:47:17,571 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed out while waiting for data (protocoldetector:94) 2019-01-19 20:47:17,576 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed out while waiting for data (protocoldetector:94) 2019-01-19 20:47:17,578 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed out while waiting for data (protocoldetector:94) --------------------- >> end captured logging << ---------------------

2 7

propose Ravi Nori as a frontend maintainer for ovirt-engine infra
by Greg Sheremeta 05 Feb '19

05 Feb '19

Hi all, I'd like to propose Ravi Nori as a frontend maintainer for ovirt-engine infra team. While the infra team typically hasn't had a frontend maintainer, Ravi has strong knowledge of all of the frontend infra pieces, including everything related to SSO, welcome page, and GWT in admin portal. Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

5 5

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-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

oVirt 4.3.0 Go / No GO
by Sandro Bonazzola 28 Jan '19

28 Jan '19

1636867 <https://bugzilla.redhat.com/show_bug.cgi?id=1636867> Miguel Duarte Barroso Network ovirt-engine BLL.Network ASSIGNED medium [OVN] - Can't create ovn network with Hebrew characters - "UnicodeEncodeError: 'ascii' codec can't encode characters" <https://bugzilla.redhat.com/show_bug.cgi?id=1636867> 1520546 <https://bugzilla.redhat.com/show_bug.cgi?id=1520546> Benny Zlotnik Storage ovirt-engine BLL.Storage NEW high LSM with continuous I/O to the VM failed and auto generated snapshot remains <https://bugzilla.redhat.com/show_bug.cgi?id=1520546> 1647491 <https://bugzilla.redhat.com/show_bug.cgi?id=1647491> Benny Zlotnik Storage ovirt-engine BLL.Storage NEW urgent All VMs on the same host crash when a snapshot fail on one of them <https://bugzilla.redhat.com/show_bug.cgi?id=1647491> 1665020 <https://bugzilla.redhat.com/show_bug.cgi?id=1665020> Daniel Erez Storage ovirt-engine BLL.Storage NEW medium In case of a vdsm failure to perform prepareImage as part of transfer disk image (download image), TransferDiskImageCommand fails with NullPointerException <https://bugzilla.redhat.com/show_bug.cgi?id=1665020> 1646161 <https://bugzilla.redhat.com/show_bug.cgi?id=1646161> shani Storage ovirt-engine BLL.Storage NEW urgent IndexOutOfBoundsException: Index: 0, Size: 0 during import of VM <https://bugzilla.redhat.com/show_bug.cgi?id=1646161> 1664588 <https://bugzilla.redhat.com/show_bug.cgi?id=1664588> Tal Nisan Storage ovirt-engine BLL.Storage NEW high [CinderLib] - Adding managed storage via UI/REST fails <https://bugzilla.redhat.com/show_bug.cgi?id=1664588> 1658976 <https://bugzilla.redhat.com/show_bug.cgi?id=1658976> shani Storage ovirt-engine BLL.Storage POST high [Backup restore API] restore VM (created from template with thin copy) from OVF data fails - ImportVmFromConfigurationCommand fails with Error during ValidateFailure.: java.lang.NullPointerException <https://bugzilla.redhat.com/show_bug.cgi?id=1658976> 1597019 <https://bugzilla.redhat.com/show_bug.cgi?id=1597019> Benny Zlotnik Storage vdsm Core NEW high LSM's diskReplicateFinish failed on libvirtError: internal error: unable to execute QEMU command 'block-job-complete': Block job 'drive-ua....' not found <https://bugzilla.redhat.com/show_bug.cgi?id=1597019> 1552344 <https://bugzilla.redhat.com/show_bug.cgi?id=1552344> Denis Chaplygin Storage vdsm Core NEW high [Backup restore API][libgfapi] Start VM, with snapshot disk attached, resides on Gluster domain, fails with libvirtError <https://bugzilla.redhat.com/show_bug.cgi?id=1552344> 1563114 <https://bugzilla.redhat.com/show_bug.cgi?id=1563114> Tal Nisan Storage ovirt-engine Frontend.WebAdmin POST medium VM snapshots subtab doesn't show if a snapshot contains memory <https://bugzilla.redhat.com/show_bug.cgi?id=1563114> 1668713 <https://bugzilla.redhat.com/show_bug.cgi?id=1668713> Ido Rosenzwig Integration ovirt-hosted-engine-setup General POST high Attempting to create Hosted Engine in Cockpit fails with qemu-kvm: -chardev pty,id=charserial0: Failed to create PTY: Operation not permitted <https://bugzilla.redhat.com/show_bug.cgi?id=1668713> 1663949 <https://bugzilla.redhat.com/show_bug.cgi?id=1663949> Tomasz Barański Virt ovirt-engine Host-Deploy POST high Can't check for update on host after upgrade of engine <https://bugzilla.redhat.com/show_bug.cgi?id=1663949> 1647018 <https://bugzilla.redhat.com/show_bug.cgi?id=1647018> Ori Liel Infra ovirt-engine RestAPI POST urgent disk_attachment href contains "null" instead of "diskattachments" in REST API requests <https://bugzilla.redhat.com/show_bug.cgi?id=1647018> 1615974 <https://bugzilla.redhat.com/show_bug.cgi?id=1615974> Shirly Radco Metrics ovirt-engine-metrics RFEs POST high [RFE][Tracker] - Replace fluentd for shipping metrics and log, switch to rsyslog. <https://bugzilla.redhat.com/show_bug.cgi?id=1615974> IDAssigneeoVirt TeamProductComponentStatusSeveritySummary Hi, above you can find the list of current open proposed blockers with target ovirt-4.3.0. oVirt 4.3.0 is planned to be released tomorrow, January 29th 2019. Assignee: please go over above list and: - if the bug is not a blocker please re-target to another release - if the bug is a real blocker please give an ETA. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

10 11

[Ovirt] [CQ weekly status] [25-01-2019]
by Dafna Ron 25 Jan '19

25 Jan '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 (#1) We have no current failures. Last failed job was for ovirt-ansible-hosted-engine due to a failed build-artiacts job on Jan 24. the issue has been resolved today by Simon Tiraboschi *CQ-Master:* RED (#1) 1. tests are still failing on ovirt-engine master due to create of domain in version 5. this was reported to the list this week and a patch has been merged to engine: https://gerrit.ovirt.org/97262 The change is currently in sected off changes and should pass CQ in the next 24 hours. you can view the status of the patch in the last "get next" job in CQ: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… 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

[ANN] oVirt 4.3.0 Third Release Candidate is now available for testing
by Sandro Bonazzola 24 Jan '19

24 Jan '19

The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 4.3.0, as of January 24th, 2018 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the first release candidate of the 4.3.0 version. This release brings more than 130 enhancements and more than 450 bug fixes on top of oVirt 4.2 series. What's new in oVirt 4.3.0? * Q35 chipset, support booting using UEFI and Secure Boot * Skylake-server and AMD EPYC support * New smbus driver in windows guest tools * Improved support for v2v * OVA export / import of Templates * Full support for live migration of High Performance VMs * Microsoft Failover clustering support (SCSI Persistent Reservation) for Direct LUN disks * Hundreds of bug fixes on top of oVirt 4.2 series * New VM portal details page (see a preview here: https://imgur.com/a/ExINpci) * New Cluster upgrade UI * OVN security groups * IPv6 (static host addresses) * Support of Neutron from RDO OpenStack 13 as external network provider * Support of using Skydive from RDO OpenStack 14 as Tech Preview * Support for 3.6 and 4.0 data centers, clusters and hosts were removed * Now using PostgreSQL 10 * New metrics support using rsyslog instead of fluentd This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for both CentOS 7 and Fedora 28 (tech preview). - oVirt Node NG is already available for CentOS 7 - oVirt Node NG for Fedora 28 (tech preview) is being delayed due to build issues with the build system. Additional Resources: * Read more about the oVirt 4.3.0 release highlights: http://www.ovirt.org/release/4.3.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.3.0/ [4] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

[URGENT] 4.3.0 RC3 blocked
by Sandro Bonazzola 24 Jan '19

24 Jan '19

Hi, I was doing integration testing on the current 4.3.0-pre repository which is planned to be released today as RC3 and i can't start a newly created VM: *Bug 1669102* <https://bugzilla.redhat.com/show_bug.cgi?id=1669102> - can't start VM qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config, ability to start up with partial NU MA mappings is obsoleted and will be removed in future can you please have a look? I've the system available for further investigations. 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>

2 3

ovirt-engine has been tagged (ovirt-engine-4.3.0.1)
by Piotr Kliczewski 24 Jan '19

24 Jan '19

1 0

Disable VNC Password in oVirt host
by Akshita Jain 23 Jan '19

23 Jan '19

Hi, I'm doing R&D project using oVirt 4.2. In my project i want to access the VNC Console on multiple screens from our separately hosted noVNC but I'm unable to access VNC console on multiple screen as it is password protected. Is there any way to disable the VNC Console Password and change it to a fixed value?

3 2

query on running OST
by Pooja Pandey 23 Jan '19

23 Jan '19

Hello Team, Could you please help me in answering a query about OST run.I am trying to run on a virtual machine and it is failing with an error that libvirtError: unsupported configuration: Domain requires KVM, but it is not available. Is it necessary to run this Ovirt System Test on a hypervisor only?Please reply on this so that I can proceed further.Thanks.... Regards, Pooja -- DISCLAIMER - *MSysTechnologies LLC* This email message, contents and its attachments may contain confidential, proprietary or legally privileged information and is intended solely for the use of the individual or entity to whom it is actually intended. If you have erroneously received this message, please permanently delete it immediately and notify the sender. If you are not the intended recipient of the email message,you are notified strictly not to disseminate,distribute or copy this e-mail.E-mail transmission cannot be guaranteed to be secure or error-free as Information could be intercepted, corrupted, lost, destroyed, incomplete or contain viruses and MSysTechnologies LLC accepts no liability for the contents and integrity of this mail or for any damage caused by the limitations of the e-mail transmission.

5 9

ovirt-engine has been tagged (ovirt-engine-4.3.0)
by Tal Nisan 22 Jan '19

22 Jan '19

1 0

vdsm has been tagged (v4.30.8)
by Milan Zamazal 22 Jan '19

22 Jan '19

1 0

vdsm has been tagged (v4.30.7)
by Milan Zamazal 22 Jan '19

22 Jan '19

1 0

Jenkins was restarted this morning
by Daniel Belenky 22 Jan '19

22 Jan '19

Hi all, Some of you have probably noticed that Jenkins was not responsive this morning. As a result, we've had to restart it. The service is up and running and everything should be back to normal by now. If you've had any running jobs by the time of the restart, please re-trigger them by going to your patch in Gerrit or PR in GitHub and comment '*ci test please*' to make sure that the CI system will test your jobs. Sorry for any inconvenience that was caused and do not hesitate to reach out to me or anyone from the CI team with questions or requests for assistance. Thanks, -- DANIEL BELENKY

1 0

[ANN] oVirt 4.2.8 is now generally available
by Sandro Bonazzola 22 Jan '19

22 Jan '19

The oVirt Project is pleased to announce the general availability of oVirt 4.2.8, as of January 22nd, 2019. This update is the eighth and last in a series of stabilization updates to the 4.2 series. Please note that no further updates will be issued for the 4.2 series. We encourage users to upgrade to 4.3 series when generally available to receive new features and updates. This release is available now for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.2 See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available - oVirt Node update is available, ISO will be available soon [2] - oVirt Tools Setup ISO is available[2] oVirt Node has been updated including: - oVirt 4.2.8: http://www.ovirt.org/release/4.2.8/ - Release for CentOS Linux 7 (1810) ( https://lists.centos.org/pipermail/centos-announce/2018-December/023082.html ) - Ansible 2.7.5: https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.… Relevant CentOS Errata included: - CEBA-2019:0037 CentOS 7 tzdata BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2019-January/023142.html ) - CESA-2019:0049 Important CentOS 7 systemd Security Update ( https://lists.centos.org/pipermail/centos-announce/2019-January/023143.html ) - CESA-2018:3651 Moderate CentOS 7 kernel Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023132.html ) - CEBA-2018:3338 CentOS 7 sos BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023125.html ) - CEBA-2018:3664 CentOS 7 selinux-policy BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023124.html ) - CESA-2018:3738 Important CentOS 7 ruby Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023122.html ) - CESA-2018:3347 Critical CentOS 7 python-paramiko Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023119.html ) - CESA-2018:3665 Important CentOS 7 NetworkManager Security Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023116.html ) - CEBA-2018:3442 CentOS 7 lvm2 BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023112.html ) - CEBA-2018:3669 CentOS 7 libvirt BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023110.html ) - CEBA-2018:3659 CentOS 7 libguestfs BugFix Update ( https://lists.centos.org/pipermail/centos-announce/2018-December/023108.html ) Additional Resources: * Read more about the oVirt 4.2.8 release highlights: http://www.ovirt.org/release/4.2.8/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.2.8/ [2] http://resources.ovirt.org/pub/ovirt-4.2/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

[vdsm] Flaky IPAddressTest
by Vojtech Juranek 21 Jan '19

21 Jan '19

Hi, FIY, IPAddressTest seems to randomly failing, e.g. in [1] with FAIL: test_add_delete_ipv4 (network.ip_address_test.IPAddressTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ ip_address_test.py", line 222, in test_add_delete_ipv4 self._test_add_delete(IPV4_A_WITH_PREFIXLEN, IPV4_B_WITH_PREFIXLEN) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ ip_address_test.py", line 247, in _test_add_delete self._assert_has_no_address(nic, ip_b) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ ip_address_test.py", line 344, in _assert_has_no_address self._assert_address_not_in(address_with_prefixlen, addresses) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ ip_address_test.py", line 352, in _assert_address_not_in self.assertNotIn(address_with_prefixlen, addresses_list) AssertionError: '192.168.98.1/29' unexpectedly found in ['192.168.99.1/29', '192.168.98.1/29', 'fe80::1442:7bff:fea7:7775/64'] Thanks Vojta [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/2141//artifact/ check-patch.tests-py27.el7.x86_64/mock_logs/script/stdout_stderr.log

2 1

[Ovirt] [CQ weekly status] [18-01-2019]
by Dafna Ron 18 Jan '19

18 Jan '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*: RED (#1) one issue still pending: 1. ovirt-provider-ovn is failing due to change https://gerrit.ovirt.org/#/c/96926/ - ip_version is mandatory on POSTs The change is failing the ost test because ip version needs to be specifically provided as a result of introducing v6 There is a patch by Miguel which I merged. there are a few patches in test now so waiting to see if the patch fixes the issue. https://gerrit.ovirt.org/#/c/97072/ - basic-suite-42: align w/ networking API Jira: https://ovirt-jira.atlassian.net/browse/OVIRT-2655 *CQ-Master:* GREEN (#2) Last failure was on Jan 14th for project ovirt-ansible-hosted-engine-setup. The project was failing on https://docs.fedoraproject.org/en-US/packaging-guidelines/Directory_Replace… Jira was closed today as projects are passing: https://ovirt-jira.atlassian.net/browse/OVIRT-2650 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

[ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]
by Dafna Ron 18 Jan '19

18 Jan '19

Hi, we are failing test 001_upgrade_engine.test_initialize_engine on ovirt 4.2 for project ovirt-ansible-hosted-engine-setup. Patch reported by CQ: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d… - Rename the role - replacing '-' with '_' Ido, can you please check this issue? failed build: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/ error: [ INFO ] Checking for an update for Setup... An update for the Setup packages ovirt-engine-setup ovirt-engine-setup-plugin-websocket-proxy ovirt-engine-dwh-setup was found. Please update that package by running: "yum update ovirt-engine-setup ovirt-engine-setup-plugin-websocket-proxy ovirt-engine-dwh-setup" and then execute Setup again. [ ERROR ] Failed to execute stage 'Environment customization': Please update the Setup packages [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20190114053840-4ysu6y.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20190114053855-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed ('FATAL Internal error (main): Please update the Setup packages',) lago.ssh: DEBUG: Command 8e6b18d0 on lago-upgrade-from-release-suite-4-2-engine errors: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in main installer.execute() File "/usr/lib/python2.7/site-packages/otopi/main.py", line 157, in execute self.context.runSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 771, in runSequence util.raiseExceptionInformation(infos[0]) File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in raiseExceptionInformation exec('raise info[1], None, info[2]') File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/distro-rpm/packages.py", line 410, in _customization raise RuntimeError(_('Please update the Setup packages')) RuntimeError: Please update the Setup packages Error Thanks, Dafna

4 8

ovirt-containers - is this project still alive?
by Sandro Bonazzola 18 Jan '19

18 Jan '19

Hi, I was removing 4.1 jenkins job and found out a 4.1 job for ovirt-containers project. Owners are Fabian Deutsch and Evgheni Dereveanchin, in CC. Contributors are Juan Hernandez and Simone Tiraboschi. I see no activity there in a while, jobs have not been created for 4.2. Is this an abandoned project? Can we drop jenkins jobs at all? 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>

3 3

[ OST Failure Report ] [ oVirt 4.2 (ovirt-provider-ovn) ] [ 18-01-2019 ] [ 098_ovirt_provider_ovn.use_ovn_provider ]
by Dafna Ron 18 Jan '19

18 Jan '19

Hi, We have a failure in ovn tests in branch 4.2. Marcin/Miguel, can you please take a look? Jira opened: https://ovirt-jira.atlassian.net/browse/OVIRT-2655 Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/96926/ - ip_version is mandatory on POSTs Link to Job: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3742/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3742/artifact/ba… (Relevant) error snippet from the log: <error> 2019-01-18 00:14:30,591 root Starting server 2019-01-18 00:14:30,592 root Version: 1.2.19-0.20190117180529.gite1d4195 2019-01-18 00:14:30,592 root Build date: 20190117180529 2019-01-18 00:14:30,592 root Githash: e1d4195 2019-01-18 00:20:39,394 ovsdbapp.backend.ovs_idl.vlog ssl:127.0.0.1:6641: no response to inactivity probe after 5.01 seconds, disconnecting 2019-01-18 00:45:01,435 root From: ::ffff:192.168.200.1:49008 Request: POST /v2.0/subnets/ 2019-01-18 00:45:01,435 root Request body: {"subnet": {"network_id": "99c260ec-dad4-40b9-8732-df32dd54bd00", "dns_nameservers": ["8.8.8.8"], "cidr": "1.1.1.0/24", "gateway_ip": "1.1.1.1", "name": "subnet_1"}} 2019-01-18 00:45:01,435 root Missing 'ip_version' attribute Traceback (most recent call last): File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", line 134, in _handle_request method, path_parts, content File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", line 175, in handle_request return self.call_response_handler(handler, content, parameters) File "/usr/share/ovirt-provider-ovn/handlers/neutron.py", line 36, in call_response_handler return response_handler(ovn_north, content, parameters) File "/usr/share/ovirt-provider-ovn/handlers/neutron_responses.py", line 154, in post_subnets subnet = nb_db.add_subnet(received_subnet) File "/usr/share/ovirt-provider-ovn/neutron/neutron_api_mappers.py", line 74, in wrapper validate_rest_input(rest_data) File "/usr/share/ovirt-provider-ovn/neutron/neutron_api_mappers.py", line 596, in validate_add_rest_input raise BadRequestError('Missing \'ip_version\' attribute') BadRequestError: Missing 'ip_version' attribute </error>

3 3

[VDSM] FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest) fail again
by Nir Soffer 16 Jan '19

16 Jan '19

We had this failure a lot in the past and it seems to be resolve, but I see it again today: ====================================================================== FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py", line 333, in wrapper return f(*args, **kwargs) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py", line 226, in test_add_delete_ipv6 self._test_add_delete(IPV6_A_WITH_PREFIXLEN, IPV6_B_WITH_PREFIXLEN) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py", line 247, in _test_add_delete self._assert_has_no_address(nic, ip_b) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py", line 344, in _assert_has_no_address self._assert_address_not_in(address_with_prefixlen, addresses) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py", line 352, in _assert_address_not_in self.assertNotIn(address_with_prefixlen, addresses_list) AssertionError: '2002:99::1/64' unexpectedly found in ['2002:99::1/64', '2001:99::1/64', 'fe80::6:23ff:fead:ed34/64'] -------------------- >> begin captured logging << -------------------- 2019-01-04 16:01:53,543 DEBUG (MainThread) [root] /sbin/ip link add name dummy_NKzY1 type dummy (cwd None) (cmdutils:133) 2019-01-04 16:01:53,559 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) 2019-01-04 16:01:53,563 DEBUG (netlink/events) [root] START thread <Thread(netlink/events, started daemon 139806010234624)> (func=<bound method Monitor._scan of <vdsm.network.netlink.monitor.Monitor object at 0x7f271d654cd0>>, args=(), kwargs={}) (concurrent:193) 2019-01-04 16:01:53,567 DEBUG (MainThread) [root] /sbin/ip link set dev dummy_NKzY1 up (cwd None) (cmdutils:133) 2019-01-04 16:01:53,586 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) 2019-01-04 16:01:53,593 DEBUG (netlink/events) [root] FINISH thread <Thread(netlink/events, started daemon 139806010234624)> (concurrent:196) 2019-01-04 16:01:53,597 DEBUG (MainThread) [root] /sbin/ip -6 addr add dev dummy_NKzY1 2001:99::1/64 (cwd None) (cmdutils:133) 2019-01-04 16:01:53,615 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) 2019-01-04 16:01:53,620 DEBUG (MainThread) [root] /sbin/ip -6 addr add dev dummy_NKzY1 2002:99::1/64 (cwd None) (cmdutils:133) 2019-01-04 16:01:53,632 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) 2019-01-04 16:01:53,639 DEBUG (MainThread) [root] /sbin/ip -6 addr del dev dummy_NKzY1 2002:99::1/64 (cwd None) (cmdutils:133) 2019-01-04 16:01:53,656 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) 2019-01-04 16:01:53,670 DEBUG (MainThread) [root] /sbin/ip link del dev dummy_NKzY1 (cwd None) (cmdutils:133) 2019-01-04 16:01:53,705 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) --------------------- >> end captured logging << --------------------- Build: https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st…

2 6

Request for adding ovirt-engine-sdk-go as an incubator project under oVirt
by Joey Ma 16 Jan '19

16 Jan '19

Hi fellows, My name is Joey. Now I'm maintaining the project ovirt-engine-sdk-go[1] which provides a Golang based sdk for oVirt engine REST API. During the past year, I was keeping in touch Ondra, Juan and Martin. It's very appreciated that they helped me a lot to improve the sdk and also added me into the oVirt developer team[2] in github. Both Ondra and I think that the project is in great shape and ready for production use. :-) The original plan is to add the project into oVirt 4.3 official release. While according to the schedules[3] for 4.3, maybe there's no enough time to make it done due to some additional CI work. So if I may ask, is that possible to add the project as an oVirt incubator project first, by transferring the project from my personal account to oVirt orgnization in github or gerrit? And then accept it as a full oVirt project after all the graduation requirements are matched. Thank you all in advance. Regards, Joey [1]: https://github.com/imjoey/ovirt-engine-sdk-go [2]: https://ovirt-jira.atlassian.net/browse/OVIRT-2460 [3]: https://www.ovirt.org/develop/release-management/releases/4.3/release-manag…

4 6

[VDSM] Network tests started to fail on Fedora 28 in travis
by Nir Soffer 15 Jan '19

15 Jan '19

________ ERROR at setup of TestOvsApiBase.test_execute_a_single_command ________ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() with xfail_when_running_on_travis_with_centos(): > service.setup() network/integration/ovs/conftest.py:38: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7fbdc2256a58> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError This line looks wrong: with xfail_when_running_on_travis_with_centos() The test fail on Fedora: https://travis-ci.org/nirs/vdsm/jobs/480027211 https://travis-ci.org/nirs/vdsm/jobs/480027212 works on CentOS: https://travis-ci.org/nirs/vdsm/jobs/480027210 Looks like we need to switch the check to Fedora. I think this started to fail today, after I rebuild the Fedora 28 image: https://gerrit.ovirt.org/c/96847/ maybe an update in Fedora is related? Nir

1 1

[Call for Testing] oVirt 4.3.0
by Sandro Bonazzola 15 Jan '19

15 Jan '19

Hi, we are planning to release a 4.3.0 RC2 tomorrow morning, January 16th 2019. We have a scheduled final release for oVirt 4.3.0 on January 29th: this is the time when testing is most effective to ensure the release will be as much stable as possible. Please join us testing the RC2 release this week and reporting issues to https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt Please remember this is still pre-release material, we recommend not installing it on production environments yet. 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>

1 0

vdsm has been tagged (v4.30.6)
by Milan Zamazal 15 Jan '19

15 Jan '19

1 0

Error while executing action Attach Storage Domain: AcquireHostIdFailure
by Fedor Gavrilov 15 Jan '19

15 Jan '19

Hi, I'm setting up iSCSI domain on freshly installed ovirt and hitting subj when I try adding new data domain. After it's added it's in Unattached state and can't be removed either. I found something in bugzilla about NFS storage and sanlock, could it be related? I allocated iSCSI fileio storage on the same machine where host is (so I'm connecting 127.0.0.1:3260), was that my mistake? Thanks in advance, Fedor Gavrilov

2 3

SSO with lightdm
by jeremiah52＠naver.com 15 Jan '19

15 Jan '19

I knows there are the GDM plugin and KDM plugin of ovirt-guest-agent that makes SSO in linux is possible. I want to make SSO with lightdm is possble. To add lightdm plugin to ovirt-guest-agent is enough? or something more is needed? I don't know how to develop SSO with lightdm.

3 2

Hard disk requirement
by Hetz Ben Hamo 13 Jan '19

13 Jan '19

Hi, The old oVirt (3.x?) ISO image wasn't requiring a big hard disk in order to install the node part on a physical machine, since the HE and other parts were running using NFS/iSCSI etc. oVirt 4.X if I understand correctly - does require hard disk on the node. Can this requirement be avoided and just use an SD Card? Whats the minimum storage for the local node? Thanks, Hetz

2 1

Can we drop fc27 jobs / rpms from CI/tested repos?
by Eyal Edri 13 Jan '19

13 Jan '19

5 8

[Ovirt] [CQ weekly status] [11-01-2019]
by Dafna Ron 11 Jan '19

11 Jan '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 (#3) we have not had any failures since before the holidays. *CQ-Master:* YELLOW (#2) - We had two different code regressions for ovirt-engine and vdsm both were reported and solved during the week. - we had missing packages which were fixed with this patch: https://gerrit.ovirt.org/#/c/96831/ Last successful build for vdsm and ovirt-engine was today (11th Jan). Current status 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_rc)
by Tal Nisan 10 Jan '19

10 Jan '19

1 1

s390x repository closure issue
by Sandro Bonazzola 09 Jan '19

09 Jan '19

Hi, just an heads up that s390x repository is failing repository closure: *00:05:15.127* Problem 2: package ovirt-host-dependencies-4.3.0-0.2.master.20190109065452.gite6c98f4.fc28.s390x requires vdsm >= 4.30.3, but none of the providers can be installed*00:05:15.127* - package vdsm-4.30.3-1.fc28.s390x requires ovirt-imageio-daemon >= 1.2.0, but none of the providers can be installed*00:05:15.127* - conflicting requests*00:05:15.127* - nothing provides ovirt-imageio-common = 1.5.0 needed by ovirt-imageio-daemon-1.5.0-0.201901061027.gita4be4ca.fc28.noarch*00:05:15.127* - nothing provides libvirt-daemon-kvm >= 4.9.0-1 needed by vdsm-4.30.4-92.git2282ef29b.fc28.s390x*00:05:15.127* - nothing provides ovirt-imageio-common = 1.4.6 needed by ovirt-imageio-daemon-1.4.6-1.fc28.noarch*00:05:15.127* - nothing provides libvirt-daemon-kvm >= 4.9.0-1 needed by vdsm-4.30.4-1.fc28.s390x If you can provide missing dependencies please let me know. 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>

1 0

oVirt 4.3.0 RC build delay
by Sandro Bonazzola 08 Jan '19

08 Jan '19

As per subject, Jenkins is under maintenance so no build can be done till maintenance is completed. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 1

Jenkins Jobs Are Not Always Triggered From Gerrit
by Anton Marchukov 08 Jan '19

08 Jan '19

Hello All. We noted that jenkins CI jobs are not always triggered for gerrit changes. While we are investigating this, I want to remind that you always can trigger / re-trigger check-patch jobs yourself. Just go to to the link [1], insert your change id and trigger it. Thanks. [1] https://jenkins.ovirt.org/gerrit_manual_trigger/ -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat

2 2

vdsm has been tagged (v4.30.5)
by Milan Zamazal 08 Jan '19

08 Jan '19

1 0

ovirt-engine has been tagged (ovirt-engine-4.2.8.2)
by Tal Nisan 07 Jan '19

07 Jan '19

1 0

vdsm has been tagged (v4.20.46)
by Milan Zamazal 07 Jan '19

07 Jan '19

1 0

Please review "dump-chains-sqlite"
by Germano Veit Michel 07 Jan '19

07 Jan '19

Hi, With these 2 changes the ovirt-log-collector will collect storage domain metadata from all storage domains of the environment in a more efficient way. https://gerrit.ovirt.org/#/q/topic:dump-chains-sqlite I'll be away for the next 2 weeks, but reviews are welcome. If there is any problem with one of these patches, please don't merge any of them as they require each other. And if you have extra time, reviews are welcome on this series too =D https://gerrit.ovirt.org/#/q/topic:snapshot-tools Thanks, Germano

2 2

preventing modifications of exiting upgrade scripts
by Eli Mesika 03 Jan '19

03 Jan '19

Hi Please note that patch[1] was merged. This patch will prevent(with a detailed ERROR[2]) any attempt to modify an existing DB upgrade script since this may lead to upgrade problems. The correct way to change something in the database is a new upgrade script. In a case that the upgrade script must be changed, this can be forced by adding a special keyword[3] to your commit header. Please see [1] description for details. If you have any questions, please let me know. [1] https://gerrit.ovirt.org/#/c/96421/ [2] [ERROR] : Changing an existing upgrade script is dangerous and can cause upgrade problems, if you are doing that in purpose and sure that there is no other way to fix the issue you are working on, please add the key 'Allow-db-upgrade-script-changes:Yes' to your patch commit message." [3] "Allow-db-upgrade-script-changes:Yes" Thanks Eli Mesika

1 0

Failed to add host to oVirt
by Eyal Shenitzky 02 Jan '19

02 Jan '19

Hey, I am failing to add a host to oVirt due to the following error: 2018-12-23 11:15:29,482+0200 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Environment customization': Cannot find a valid baseurl for repo: ovirt -master-centos-gluster5/7Server/x86_64 Does someone encounter this issue? -- Regards, Eyal Shenitzky

2 1