- Devel - oVirt List Archives

[Blocker] master builds with lower NVR than 4.3 builds
by Sandro Bonazzola 22 Nov '19

22 Nov '19

ovirt-engine-sdk master has a lower version than the one shipped in 4.3. Current master a1e1067 from https://gerrit.ovirt.org/#/c/104083/ generated: python-ovirt-engine-sdk4-4.3.1-2.20191015gita1e1067.el7.x86_64.rpm in https://jenkins.ovirt.org/job/ovirt-engine-sdk_standard-on-merge/8/ while latest released build (in 4.3.5) is: python-ovirt-engine-sdk4-4.3.2-1 Action item for all maintainers: please go over your packages and ensure the master branch has a newer version than the one shipped in 4.3 branch. Thanks -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 1

unit tests, surefire and spotbugs tests on ovirt-engine at check-patch stage
by Sandro Bonazzola 22 Nov '19

22 Nov '19

Hi, looking at ovirt-engine CI automation scripts, I see: export EXTRA_BUILD_FLAGS="-gs $MAVEN_SETTINGS \ -Dovirt.surefire.reportsDirectory=${PWD}/exported-artifacts/tests \ " But looking at exported data, there's no exported-artifacts/tests directory. Looking at build execution I see: [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ ovirt-findbugs-filters --- [INFO] Tests are skipped. ... [INFO] --- maven-surefire-plugin:2.22.0:test (default-test) @ checkstyles --- [INFO] Tests are skipped. and so on. This is due to the build happening with RPM_BUILD_MODE="ovirt_build_quick" which cause the setting of %global _ovirt_build_ut 0 which set BUILD_UT=0 which skip all tests due to: ifeq ($(BUILD_UT),0) BUILD_FLAGS:=$(BUILD_FLAGS) -D skipTests endif Also, check patch has: # Since spotbugs is a pure java task, there's no reason to run it on multiple # platforms. # Spotbugs currently has false negatives using mvn 3.5.0, which is the currnt centos version from SCL (rh-maven35). # We will work with the Fedora version meanwhile which has maven 3.5.4 and is known to work. if [[ "$STD_CI_DISTRO" =~ "fc" ]]; then source automation/spotbugs.sh fi so spotbugs is executed only on Fedora but then: if [[ "$STD_CI_DISTRO" = "el7" ]]; then # Collect any mvn spotbugs artifacts mkdir -p exported-artifacts/find-bugs find * -name "*spotbugs.xml" -o -name "spotbugsXml.xml" | \ while read source_file; do destination_file=$( sed -e 's#/#-#g' -e 's#$.*$-#\1.#' <<< "$source_file" ) mv $source_file exported-artifacts/find-bugs/"$destination_file" done mv ./*tar.gz exported-artifacts/ fi so assuming we re-enable tests there, results are collected only on el7 meaning we are never getting results of this test. Can we decide what we really want check-patch to do? Either we want test results and we should enable proper build including tests or we should drop all of this broken test result collection code. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

gathering builds for oVirt 4.4.0 Alpha release
by Sandro Bonazzola 22 Nov '19

22 Nov '19

While waiting for CentOS Linux 8.1 to be released, we are now preparing an alpha compose that will be made available on top of CentOS Linux 8.0. I'm starting gathering the builds to be included in the alpha release with the first commit here: https://gerrit.ovirt.org/#/c/104880/ If you want a specific version to be included in alpha please push a patch updating the release configuration file. For needed packages that won't be included in the release file, latest build passing CI tests will be included in the compose. Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

3 5

building ovirt-engine 4.0
by Fedor Gavrilov 21 Nov '19

21 Nov '19

Hi, To validate an issue I am working on I was trying to build ovirt-engine 4.0 on my CentOS 7.7 but it seems to fail for me. If my JAVA_HOME is pointing to where java 7 is installed, I get javac: invalid target release: 1.8 if it points to where java 8 is, checkstyle strikes again: Failed to execute goal on project ovirt-checkstyle-extension: Could not resolve dependencies for project org.ovirt.engine:ovirt-checkstyle-extension:jar:4.0.6: Could not find artifact com.sun:tools:jar:1.7.0 at specified path /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.232.b09-0.el7_7.x86_64/jre/../lib/tools.jar Is that how it works for everyone? Thanks, Fedor

3 5

SDK: Editing VM memory size and max memory attribute
by donagh.moran＠oracle.com 21 Nov '19

21 Nov '19

Ovirt version 4.2.8 Hi I'm attempting to set the memory size or the max memory attributes of a VM via the Vmbuilder. Both of the following rest calls result in the same error on both vmStatic.memSizeMb and vmStatic.maxMemorySizeMb VmService vms = sysService.vmsService().list().search(vmName).send().vms().get(0); vms.update().vm(vm().memory(12).build()).send(); or vms.update().vm(vm().memoryPolicy(memoryPolicy().max(2096)).build()).send(); org.ovirt.engine.sdk4.Error: Fault reason is "Operation Failed". Fault detail is "[must be greater than or equal to 1, Attribute: vmStatic.maxMemorySizeMb ]". HTTP response code is "400". HTTP response message is "Bad Request". at org.ovirt.engine.sdk4.internal.services.ServiceImpl.throwError(ServiceImpl.java:116) at org.ovirt.engine.sdk4.internal.services.ServiceImpl.checkFault(ServiceImpl.java:43) at org.ovirt.engine.sdk4.internal.services.VmServiceImpl$UpdateRequestImpl.send(VmServiceImpl.java:1563) at org.ovirt.engine.sdk4.internal.services.VmServiceImpl$UpdateRequestImpl.send(VmServiceImpl.java:1482) at com.oracle.testbox.product.ovirt.tests.regression.cluster.ClusterOptimizationTest.memoryOptimizationTest(ClusterOptimizationTest.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85) at org.testng.internal.Invoker.invokeMethod(Invoker.java:639) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:816) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1124) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108) at org.testng.TestRunner.privateRun(TestRunner.java:774) at org.testng.TestRunner.run(TestRunner.java:624) at org.testng.SuiteRunner.runTest(SuiteRunner.java:359) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:354) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:312) at org.testng.SuiteRunner.run(SuiteRunner.java:261) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1215) at org.testng.TestNG.runSuitesLocally(TestNG.java:1140) at org.testng.TestNG.run(TestNG.java:1048) at org.testng.TestNG.privateMain(TestNG.java:1355) at org.testng.TestNG.main(TestNG.java:1324) at com.oracle.testbox.framework.runner.Testbox.run(Testbox.java:116) at com.oracle.testbox.framework.runner.Testbox.main(Testbox.java:121) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.simontuffs.onejar.Boot.run(Boot.java:342) at com.simontuffs.onejar.Boot.main(Boot.java:168) I've seen related bugs logged and marked as fixed in 4.1.0 https://bugzilla.redhat.com/show_bug.cgi?id=1408577 Can shed some light on whether I am missing some code pre the rest request or is this a bug? Regards Donagh

2 1

[feedback needed] oVirt master test
by Sandro Bonazzola 20 Nov '19

20 Nov '19

Hi, as part of the 4.4 development we'd like to ask for testing current master. In order to ease the test, you can take: oVirt Node: https://resources.ovirt.org/pub/ovirt-master-snapshot/iso/ovirt-node-ng-ins… when this link won't be available anymore due to nightly build rotation you can take the latest from https://resources.ovirt.org/pub/ovirt-master-snapshot/iso/ovirt-node-ng-ins… oVirt appliance: https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el8/x86_64/ovirt-… as per oVirt Node, you can take the latest from https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el8/x86_64/ if above link doesn't work. The above 2 builds have been tested on a single host nested VM system with 70Gb disk, 8Gb of RAM and 4 cores for the node. Both oVirt Node and oVirt Engine appliance installation succeeded on 80GB NFS external storage with static IP addressing. We have a known issue on booting with more than 1 NIC that will be addressed soon, so please use a single NIC in your tests for now. Looking forward for your feedback, thanks. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

3 3

Fwd: Orphaning my packages
by Sandro Bonazzola 20 Nov '19

20 Nov '19

FYI, we consume those packages on Fedora. Any volunteer for taking them? ---------- Forwarded message --------- Da: Roman Mohr <roman(a)fenkhuber.at> Date: mar 19 nov 2019 alle ore 15:20 Subject: Orphaning my packages To: <devel(a)lists.fedoraproject.org> Hi, I take [1] as the opportunity to orphan the following packages: rpms/aspectjweaver rpms/assertj-core rpms/hystrix rpms/memoryfilesystem rpms/rxjava rpms/archaius I don't use these projects anymore, and I don't have time to follow them. Best Regards, Roman [1] https://pagure.io/fesco/issue/2280 _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*

4 4

OST fails for collecting artifacts
by Amit Bawer 20 Nov '19

20 Nov '19

Happens for several runs, full log can be seen at http://jenkins.ovirt.org/job/ovirt-system-tests_manual/6057/artifact/export… 2019-11-18 12:28:12,710::log_utils.py::end_log_task::670::root::ERROR:: - [Thread-42] lago-basic-suite-master-engine: [31mERROR [0m (in 0:00:08) 2019-11-18 12:28:12,731::log_utils.py::__exit__::607::lago.prefix::DEBUG:: File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1526, in _collect_artifacts vm.collect_artifacts(path, ignore_nopath) File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 748, in collect_artifacts ignore_nopath=ignore_nopath File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 468, in extract_paths return self.provider.extract_paths(paths, *args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/providers/libvirt/vm.py", line 398, in extract_paths ignore_nopath=ignore_nopath, File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 253, in extract_paths self._extract_paths_tar_gz(paths, ignore_nopath) File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 102, in wrapper return func(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 341, in _extract_paths_tar_gz raise ExtractPathNoPathError(remote_path) 2019-11-18 12:28:12,731::utils.py::_ret_via_queue::63::lago.utils::DEBUG::Error while running thread Thread-42 Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1526, in _collect_artifacts vm.collect_artifacts(path, ignore_nopath) File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 748, in collect_artifacts ignore_nopath=ignore_nopath File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 468, in extract_paths return self.provider.extract_paths(paths, *args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/providers/libvirt/vm.py", line 398, in extract_paths ignore_nopath=ignore_nopath, File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 253, in extract_paths self._extract_paths_tar_gz(paths, ignore_nopath) File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 102, in wrapper return func(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/plugins/vm.py", line 341, in _extract_paths_tar_gz raise ExtractPathNoPathError(remote_path) ExtractPathNoPathError: Failed to extract files: /tmp/otopi*

4 4

upgrade-suite in manual system test is broken
by Sandro Bonazzola 20 Nov '19

20 Nov '19

Hi Just executed manual system test on https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6072/ for testing upgrade from latest released to 4.3.7 rc4 and instead of using latest released it used latest rpms passing CI so the test was not useful at all. Who's maintaining the upgrade suite? -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 1

manual system test runner broken
by Sandro Bonazzola 19 Nov '19

19 Nov '19

Hi, just executed basic suite for testing 4.3.7 rc4 and instead of falling back on latest released it was falling back on latest tested which is newer than 4.3.7 rc4 so made the test useless. Job execution is here: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6071/ who's maintaining manual ost runner? I have the feeling it's not a suite bug, but a job bug. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 3