March 2019 - Devel - oVirt List Archives

[OST upgrade suite] Looking for maintainer
by Ales Musil 25 Mar '19

25 Mar '19

Hi, I am not sure who is currently maintainer for the upgrade suite, but please take a look at [1]. This patch is testing the engine upgrade issue with database vm_id and vmt_id in interface table [2]. And at the same time serves as opening patch to put more sophisticated tests into upgrade suite. Thank you. Regards, Ales [1] https://gerrit.ovirt.org/c/98656/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1547038 -- ALES MUSIL Associate Software Engineer - rhv network Red Hat EMEA <https://www.redhat.com/> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

3 6

[OST][master] hc-basic-suite-master failing on OVF_STORE not ready
by Sandro Bonazzola 25 Mar '19

25 Mar '19

Job is: https://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/1054… Logs show: *03:19:46* TASK [ovirt.hosted_engine_setup : Wait for OVF_STORE disk content] **************03:19:47* FAILED - RETRYING: Wait for OVF_STORE disk content (12 retries left).*03:19:58* FAILED - RETRYING: Wait for OVF_STORE disk content (11 retries left).*03:20:09* FAILED - RETRYING: Wait for OVF_STORE disk content (10 retries left).*03:20:19* FAILED - RETRYING: Wait for OVF_STORE disk content (9 retries left).*03:20:30* FAILED - RETRYING: Wait for OVF_STORE disk content (8 retries left).*03:20:41* FAILED - RETRYING: Wait for OVF_STORE disk content (7 retries left).*03:20:52* FAILED - RETRYING: Wait for OVF_STORE disk content (6 retries left).*03:21:03* FAILED - RETRYING: Wait for OVF_STORE disk content (5 retries left).*03:21:14* FAILED - RETRYING: Wait for OVF_STORE disk content (4 retries left).*03:21:25* FAILED - RETRYING: Wait for OVF_STORE disk content (3 retries left).*03:21:36* FAILED - RETRYING: Wait for OVF_STORE disk content (2 retries left).*03:21:46* FAILED - RETRYING: Wait for OVF_STORE disk content (1 retries left).*03:21:57* failed: [localhost] (item={u'image_id': u'7df4f0be-0192-4e8b-bb6d-ee4cfd2a45d0', u'name': u'OVF_STORE', u'id': u'c55ba7d1-10cf-4f71-a9d2-59cf4ccb08e1'}) => {"attempts": 12, "changed": true, "cmd": "vdsm-client Image prepare storagepoolID=b9c1cfba-4ea2-11e9-b48c-00163e24d363 storagedomainID=a35d1e26-790d-4da6-90d1-df654cbfc0f3 imageID=c55ba7d1-10cf-4f71-a9d2-59cf4ccb08e1 volumeID=7df4f0be-0192-4e8b-bb6d-ee4cfd2a45d0 | grep path | awk '{ print $2 }' | xargs -I{} sudo -u vdsm dd if={} | tar -tvf - 5f87c4b6-2141-4d0c-8ce6-8bb1da97aeb6.ovf", "delta": "0:00:00.578484", "end": "2019-03-24 22:21:57.660496", "item": {"id": "c55ba7d1-10cf-4f71-a9d2-59cf4ccb08e1", "image_id": "7df4f0be-0192-4e8b-bb6d-ee4cfd2a45d0", "name": "OVF_STORE"}, "msg": "non-zero return code", "rc": 2, "start": "2019-03-24 22:21:57.082012", "stderr": "tar: 5f87c4b6-2141-4d0c-8ce6-8bb1da97aeb6.ovf: Not found in archive\ntar: Exiting with failure status due to previous errors\n20+0 records in\n20+0 records out\n10240 bytes (10 kB) copied, 0.00214885 s, 4.8 MB/s", "stderr_lines": ["tar: 5f87c4b6-2141-4d0c-8ce6-8bb1da97aeb6.ovf: Not found in archive", "tar: Exiting with failure status due to previous errors", "20+0 records in", "20+0 records out", "10240 bytes (10 kB) copied, 0.00214885 s, 4.8 MB/s"], "stdout": "", "stdout_lines": []} -- 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 1

[Ovirt] [CQ weekly status] [22-03-2019]
by Dafna Ron 22 Mar '19

22 Mar '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) Last CQ job failure on 4.2 was 21-03-2019 on project ovirt-hosted-engine-setup due to access to repo centos-cr-el7 in mirrors. this can be solved by projects setting their repo list to work with CI local mirrors. *CQ-4.3*: RED (#1) vdsm is failing on 4.3 due to failure in add_master_storage_domain. this issue is currently investigated by Marcin Sobczyk *CQ-Master:* RED (#1) we are failing on project ovirt-engine for test hotplug_cpu. this was debugged by Evgheni and myself to determine that the issue is indeed in ovirt and not in infra. The test is failing as the internal vm is not responding and we cannot ssh to vm0. *There is a random failure for test get_host_hooks. * It fails on all branches and I can see a NPE in the engine log. The test owner was Yaniv Kaul and Marcin Sobczyk is now looking into the failure. I created a skiptest patch but I am hoping that this would be resolved soon so we do not have to use it. Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [3] 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

virtual floppy disk bug
by Hetz Ben Hamo 22 Mar '19

22 Mar '19

Hi, Since the ISO domain is being deprecated, it seems that when uploading a VFD to the data domain, it won't show when trying to select it in either VM configuration or Run Once windows. Which component on bugzilla should I report this bug into? Thanks

2 1

where is the vdsm-hook-nestedvt package?
by Hetz Ben Hamo 22 Mar '19

22 Mar '19

Hi, I'm testing the master branch and looking here <https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/x86_64/> it seems the package vdsm-hook-nestedvt is missing.. Thanks

1 2

Is only master branch of ovirt-engine analyzed on coverity scan?
by simtiaz＠ncsu.edu 21 Mar '19

21 Mar '19

I see the github project ovirt-engine (https://github.com/oVirt/ovirt-engine) is registered on Coverity Scan for routine analysis (https://scan.coverity.com/projects/ovirt-engine?tab=project_settings) My question is - 1) do we only build and analyze the master branch on Coverity? 1a) If yes, why do we not analyze the other branches?

3 3

Usage of ntpdate in OST suites
by Sandro Bonazzola 21 Mar '19

21 Mar '19

Hi, just noticed today we are calling "ntpdate -4 <engine fqdn>" within OST suites but then it fails with "ntpdate: command not found" and we ignore it. I think "chronyc -4 makestep" should be used instead after having configure the engine as server. Any insight on this? -- 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

Is only master branch of ovirt-engine analyzed on coverity scan?
by simtiaz＠ncsu.edu 20 Mar '19

20 Mar '19

I see the github project ovirt-engine (https://github.com/oVirt/ovirt-engine) is registered on Coverity Scan for routine analysis (https://scan.coverity.com/projects/ovirt-engine?tab=project_settings) My question is - 1) do we only build and analyze the master branch on Coverity? 1a) If yes, why do we not analyze the other branches? 1b) If no, how to detect which alert on coverity is for which branch? Thanks, Nasif

1 0

ovirt-jboss-modules-maven-plugin package
by Sandro Bonazzola 20 Mar '19

20 Mar '19

Hi, just noticed today we are building on master a package named ovirt-jboss-modules-maven-plugin. The package is not required by any other package at spec file / rpm level and it has never been shipped in an official release as far as I can tell. Grep says we are using a java package through maven called ovirt-jboss-modules-maven-plugin in: - ovirt-engine - ovirt-engine-api-metamodel It doesn't seem we are bundling the library so it looks like a build time dependency only. Am I correct? Why aren't we adding it as BuildRequires to ovirt-engine spec file and keeping downloading it from maven central at every build instead of using system installed library? 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

Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs
by Nir Soffer 20 Mar '19

20 Mar '19

We started to use this job to build artifacts for running OST. Looks like this job is limited to one concurrent job, which make it less useful than it could be. If we don't make it easy to run OST, people will not run it, and the change queue will break. Please change the limit to use the same limit used for regular builds. We seem to be able to create more then 10 concurrent builds by uploading patches to gerrit. The manual runner should this as well. Nir

1 0