November 2020 - Devel - Ovirt List Archives

Merge rights changes in the oVirt Engine project

by Tal Nisan

Hi everyone, As you probably know we are now in a mode in which we develop our next zstream version on the master branch as opposed to how we worked before where the master version was dedicated for the next major version. This makes the rapid changes in master to be delivered to customers in a much higher cadence thus affecting stability. Due to that we think it's best that from now on merges in the master branch will be done only by stable branch maintainers after inspecting those closely. What you need to do in order to get your patch merged: - Have it pass Jenkins - Have it get code review +2 - Have it mark verified +1 - It's always encourage to have it tested by OST, for bigger changes it's a must Once you have all those covered, please add me as a reviewer and I'll examine it and merge if everything seems right, if I haven't done it in a timely manner feel free to ping me.

4 weeks

3
4
0 / 0

Error Java SDK Issue??

by Geschwentner, Patrick

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/j... ). Can you confirm the defect? Best regards Patrick

1 month

6
11
0 / 0

CentOS Stream support

by Michal Skrivanek

Hi all, we would like to ask about interest in community about oVirt moving to CentOS Stream. There were some requests before but it’s hard to see how many people would really like to see that. With CentOS releases lagging behind RHEL for months it’s interesting to consider moving to CentOS Stream as it is much more up to date and allows us to fix bugs faster, with less workarounds and overhead for maintaining old code. E.g. our current integration tests do not really pass on CentOS 8.1 and we can’t really do much about that other than wait for more up to date packages. It would also bring us closer to make oVirt run smoothly on RHEL as that is also much closer to Stream than it is to outdated CentOS. So..would you like us to support CentOS Stream? We don’t really have capacity to run 3 different platforms, would you still want oVirt to support CentOS Stream if it means “less support” for regular CentOS? There are some concerns about Stream being a bit less stable, do you share those concerns? Thank you for your comments, michal

3 months

6
12
0 / 0

Dropping all el7 OST runs

by Marcin Sobczyk

Hi, since all the important suites are working on el8 already, we're planning to drop all el7 OST runs with [1] very soon. This means we can finally say goodbye to py2 and other legacy stuff! We still need to move manual OST runs not to use containers for that to happen. This effort is tracked here [2]. Regards, Marcin [1] https://gerrit.ovirt.org/112378 [2] https://ovirt-jira.atlassian.net/browse/OST-145

4 months, 3 weeks

5
13
0 / 0

planned Jenkins restart

by Evgheni Dereveanchin

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new CI jobs will be scheduled during this maintenance period. I will inform you once it is back online. -- Regards, Evgheni Dereveanchin

5 months

2
2
0 / 0

[OST] Error updating ost images - packages with conflicts/broken deps

by Nir Soffer

Trying dnf update on ost system fails now with: $ sudo dnf update ... Error: Problem 1: package ost-images-el8-host-deps-installed-1-202011270303.x86_64 requires ost-images-el8-upgrade = 1-202011270303, but none of the providers can be installed - cannot install both ost-images-el8-upgrade-1-202011290315.x86_64 and ost-images-el8-upgrade-1-202011270303.x86_64 - cannot install the best update candidate for package ost-images-el8-upgrade-1-202011270303.x86_64 - cannot install the best update candidate for package ost-images-el8-host-deps-installed-1-202011270303.x86_64 Problem 2: package ost-images-el8-engine-deps-installed-1-202011270303.x86_64 requires ost-images-el8-upgrade = 1-202011270303, but none of the providers can be installed - cannot install both ost-images-el8-upgrade-1-202011290315.x86_64 and ost-images-el8-upgrade-1-202011270303.x86_64 - package ost-images-el8-engine-installed-1-202011290315.x86_64 requires ost-images-el8-upgrade = 1-202011290315, but none of the providers can be installed - cannot install the best update candidate for package ost-images-el8-engine-installed-1-202011270303.x86_64 - cannot install the best update candidate for package ost-images-el8-engine-deps-installed-1-202011270303.x86_64 Problem 3: problem with installed package ost-images-el8-host-deps-installed-1-202011270303.x86_64 - package ost-images-el8-host-deps-installed-1-202011270303.x86_64 requires ost-images-el8-upgrade = 1-202011270303, but none of the providers can be installed - cannot install both ost-images-el8-upgrade-1-202011290315.x86_64 and ost-images-el8-upgrade-1-202011270303.x86_64 - package ost-images-el8-host-installed-1-202011290315.x86_64 requires ost-images-el8-upgrade = 1-202011290315, but none of the providers can be installed - cannot install the best update candidate for package ost-images-el8-host-installed-1-202011270303.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) $ sudo dnf update --nobest works, but complains about: Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): ost-images-el8-upgrade x86_64 1-202011290315 ost-images 15 M Skipping packages with broken dependencies: ost-images-el8-engine-installed x86_64 1-202011290315 ost-images 1.0 G ost-images-el8-host-installed x86_64 1-202011290315 ost-images 518 M I have not tried to run ost with the updated packages yet. Nir

5 months, 1 week

2
3
0 / 0

Planned gerrit.ovirt.org outage 24.11.2020 from 21:00 UTC

by Evgheni Dereveanchin

Hi everyone, I will be performing planned upgrades on gerrit.ovirt.org tonight. The following services will be unreachable for up to several hours: * gerrit.ovirt.org - code review service * jenkins.ovirt.org - continuous integration service Further announcements will be sent out once the outage window opens and closes. -- Regards, Evgheni Dereveanchin

5 months, 1 week

3
7
0 / 0

Breaking change introduced in vdsm-jsonrpc-java-1.6.0

by Artur Socha

Hi, We have recently introduced the breaking change in vdsm-jsonrpc-java [1]. Reactive streams package has been replaced with java.util.concurrent.Flow (shipped with JDK). This change is released with vdsm-jsonrpc-java-1.6.0. This change had to be reflected in ovirt-engine as well (otherwise it would not compile). I was handled by this patch [2]. Unfortunately these two changes must be in sync. Please update vdsm-jsonrpc-java to 1.6.0 if you are already working on ovirt engine revision that includes [2]. [1] https://gerrit.ovirt.org/#/c/vdsm-jsonrpc-java/+/109916/ [2] https://gerrit.ovirt.org/#/c/ovirt-engine/+/112347/ Please accept my apologies for not letting you know earlier, ideally before these patches got merged. -- Artur Socha Senior Software Engineer, RHV Red Hat

5 months, 1 week

1
0
0 / 0

Health check endpoint in the engine hanging forever on CheckDBConnection

by Marcin Sobczyk

Hi, I'm trying out (I think) the latest build of ovirt-engine in OST [1] and the basic suite fails when we do engine reconfiguration and then restart the service [2]. After restarting we wait on the health check endpoint status here [3]. This however ends with a timeout. I tried running manually: curl -D - http://engine/ovirt-engine/services/health and that command also hangs forever. In the engine log the last related entry seem to be: 2020-11-26 16:20:15,761+01 DEBUG [org.ovirt.engine.core.utils.servlet.LocaleFilter] (default task-7) [] Incoming locale 'en-US'. Filter determined locale to be 'en-US' 2020-11-26 16:20:15,761+01 DEBUG [org.ovirt.engine.core.services.HealthStatus] (default task-7) [] Health Status servlet: entry 2020-11-26 16:20:15,761+01 DEBUG [org.ovirt.engine.core.services.HealthStatus] (default task-7) [] Calling CheckDBConnection query Has anyone else also encountered that? Regards, Marcin [1] ovirt-engine-4.4.4.3-0.0.master.20201126133903.gitc2c805a2662.el8.noarch [2] https://github.com/oVirt/ovirt-system-tests/blob/3e2fc267b376a12eda131fa0... [3] https://github.com/oVirt/ovirt-system-tests/blob/3e2fc267b376a12eda131fa0...

5 months, 1 week

4
5
0 / 0

ovirt-engine has been tagged (ovirt-engine-4.4.4.2)

by Tal Nisan

5 months, 1 week

1
0
0 / 0

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Devel November 2020