- Devel - oVirt List Archives

dwh failing on master, perhaps because engine is 4.4
by Yedidyah Bar David 20 Mar '19

20 Mar '19

Hi all, https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… fails with: ... lambda: engine.service('ovirt-engine-dwhd').alive() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 282, in assert_true_within_short assert_equals_within_short(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) 'False != True after 180 seconds dwhd log has: 2019-03-20 03:07:06|5iRyfJ|KapTFh|KapTFh|OVIRT_ENGINE_DWH|MinimalVersionCheck|Default|5|tDie|tDie_1|2019-03-20 03:07:06|You have upgraded your oVirt Engine and now require an upgrade of the ovirt-engine-dwh package. Please run engine-setup to upgrade the version. Service will now exit.|4 I assume that this is because the engine is now 4.4 and dwh master is still 4.3. I see that dwh already branched 4.3, should we bump master to 4.4? Thanks and best regards, -- Didi

1 0

Re: OST failures (Update to use gluster 5)
by Sahina Bose 20 Mar '19

20 Mar '19

On Wed, Mar 20, 2019 at 12:31 AM Greg Sheremeta <gshereme(a)redhat.com> wrote: > Hey, > > Is someone looking at all the OST failures? > he, hc, and network are all failing with the 409 error. Started after the > merge of > "Update to use gluster 5" > I'm not positive that's the problem, but seems likely. > > Do you mean https://gerrit.ovirt.org/#/c/98470/ ? this should have affected only the hc-master suite Both hc and he suites are failing with this error..this is probably not related to gluster, as he suite does not use gluster. Adding Simone and devel ml for insights "tar: ebaaaefb-5d8c-4059-a59e-b81cdb09e001.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.00144612 s, 7.1 MB/s", "stderr_lines": ["tar: ebaaaefb-5d8c-4059-a59e-b81cdb09e001.ovf: Not found in archive" > 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> >

2 3

oVirt Engine 4.3 has been branched
by Tal Nisan 19 Mar '19

19 Mar '19

Which means that if you want your content in Engine 4.3.3 and onwards you should backport to the ovirt-engine-4.3 branch, master now basically serves as the future branch (4.4)

2 1

Are we ready to branch ovirt-engine for 4.3?
by Sandro Bonazzola 18 Mar '19

18 Mar '19

Hi, we built 4.3.2 RC2 this week and we have a planned GA for it next week. Since branching engine requires a bit of coordination, are we ready to branch it? 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 8

Missed ovirt-openshift-extensions release?
by Sandro Bonazzola 18 Mar '19

18 Mar '19

Hi, just seen https://twitter.com/RealGophersShip/status/1105791600762986496 Are we missing a release of ovirt-openshift-extensions? It wasn't included in 4.3.2 RC2 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 7

oci: command line tool for oVirt CI
by Nir Soffer 18 Mar '19

18 Mar '19

I want to share a nice little tool that can make your life easier. https://github.com/nirs/oci With this PR: https://github.com/nirs/oci/pull/1 You will be able to do this: $ python system-tests.py 98535 2019-03-15 21:17:04,579 INFO [system-tests] [ 1/8 ] Getting build info for change 98535 2019-03-15 21:17:05,295 INFO [system-tests] [ 2/8 ] Starting build-artifacts job for {'url': u'git://gerrit.ovirt.org/vdsm', 'ref': u'refs/changes/35/98535/3'} 2019-03-15 21:17:06,134 INFO [system-tests] [ 3/8 ] Waiting for queue item https://jenkins.ovirt.org/queue/item/382806/ 2019-03-15 21:17:07,960 INFO [system-tests] [ 4/8 ] Waiting for job http://jenkins.ovirt.org/job/standard-manual-runner/89/ 2019-03-15 21:26:21,381 INFO [system-tests] [ 5/8 ] Starting oVirt system tests basic suite with custom repos http://jenkins.ovirt.org/job/standard-manual-runner/89/ 2019-03-15 21:26:22,242 INFO [system-tests] [ 6/8 ] Waiting for queue item https://jenkins.ovirt.org/queue/item/382817/ 2019-03-15 21:30:43,558 INFO [system-tests] [ 7/8 ] Waiting for job http://jenkins.ovirt.org/job/ovirt-system-tests_manual/4330/ 2019-03-15 22:10:52,891 INFO [system-tests] [ 8/8 ] System tests completed with SUCCESS Yes, one command from your favorite shell. It takes about 53 minutes, but on Fedora you get notifications when commands finish. No need to to add "ci please build" comment, wait until the job is complete, copy the job url, open OST page, wait (jenkins is slow), paste the build artifacts url, start the job, wait, wait more, check if OST is done, (not yet), wait more..., OST finished, check the logs, did you paste the wrong url? The tool is not finished yet. If you like to contribute to this fun little project please check the issues: https://github.com/nirs/oci/issues Most of the issues are easy. Some harder like: - https://github.com/nirs/oci/issues/11 - https://github.com/nirs/oci/issues/12 Feel free to open new issues if you have an idea for this tool. Nir

5 5

Dependencies issue on manual OST
by Eyal Shenitzky 18 Mar '19

18 Mar '19

Hi, I encounter this dependency issue while trying to run OST manually: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4343/ *09:49:35* @ Deploy oVirt environment: *09:49:35* # Deploy environment: *09:49:35* * [Thread-2] Deploy VM lago-basic-suite-master-host-0: *09:49:35* * [Thread-3] Deploy VM lago-basic-suite-master-host-1: *09:49:35* * [Thread-4] Deploy VM lago-basic-suite-master-engine: *09:49:54* * [Thread-3] Deploy VM lago-basic-suite-master-host-1: Success (in 0:00:18) *09:49:56* STDERR*09:49:56* + yum -y install ovirt-host*09:49:56* Error: Package: ovirt-host-dependencies-4.4.0-0.0.master.20190308162916.git4c2aa13.el7.x86_64 (alocalsync)*09:49:56* Requires: vdsm-client >= 4.40.0*09:49:56* Available: vdsm-client-4.30.11-10.gitf23ba52.el7.noarch (alocalsync)*09:49:56* vdsm-client = 4.30.11-10.gitf23ba52.el7*09:49:56* Error: Package: ovirt-host-dependencies-4.4.0-0.0.master.20190308162916.git4c2aa13.el7.x86_64 (alocalsync)*09:49:56* Requires: vdsm >= 4.40.0*09:49:56* Installing: vdsm-4.30.11-10.gitf23ba52.el7.x86_64 (alocalsync)*09:49:56* vdsm = 4.30.11-10.gitf23ba52.el7*09:49:56* Error: Package: ovirt-host-dependencies-4.4.0-0.0.master.20190308162916.git4c2aa13.el7.x86_64 (alocalsync)*09:49:56* Requires: vdsm-client >= 4.40.0*09:49:56* Installing: vdsm-client-4.30.11-10.gitf23ba52.el7.noarch (alocalsync)*09:49:56* vdsm-client = 4.30.11-10.gitf23ba52.el7 Does someone encounter it? Thanks -- Regards, Eyal Shenitzky

3 3

OST hyperconverged master fails
by Greg Sheremeta 17 Mar '19

17 Mar '19

Hi, I'm trying to run OST hyperconverged master locally, but it's missing some ansible inventory file and fails. Is this a known issue? + lago copy-to-vm lago-hc-basic-suite-master-host-0 /home/greg/projects/ovirt-system-tests/hc-basic-suite-master/generate-hc-answerfile.sh /root/generate-hc-answerfile.sh @ Copy /home/greg/projects/ovirt-system-tests/hc-basic-suite-master/generate-hc-answerfile.sh to lago-hc-basic-suite-master-host-0:/root/generate-hc-answerfile.sh: @ Copy /home/greg/projects/ovirt-system-tests/hc-basic-suite-master/generate-hc-answerfile.sh to lago-hc-basic-suite-master-host-0:/root/generate-hc-answerfile.sh: Success (in 0:00:00) + lago shell lago-hc-basic-suite-master-host-0 /root/exec_playbook.sh lago-hc-basic-suite-master-host-0 lago-hc-basic-suite-master-host-1 lago-hc-basic-suite-master-host-2 */root/exec_playbook.sh: line 9: /usr/share/doc/gluster.ansible/playbooks/hc-ansible-deployment/ohc_gluster_inventory.yml: No such file or directory* + RET_CODE=1 + '[' 1 -ne 0 ']' + echo 'ansible setup on lago-hc-basic-suite-master-host-0 failed with status 1.' ansible setup on lago-hc-basic-suite-master-host-0 failed with status 1. + exit 1 + on_exit + [[ 1 -ne 0 ]] + logger.error 'on_exit: Exiting with a non-zero status' + logger.log ERROR 'on_exit: Exiting with a non-zero status' + set +x 2019-03-15 06:16:36.021775858-0400 run_suite.sh::on_exit::ERROR:: on_exit: Exiting with a non-zero status -- 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>

3 4

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

15 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 14-03-2019 on project v2v-conversion-host due to missing failed build artifacts which was fixed the same day. *CQ-4.3*: RED (#1) Last job to failed today. it had 13 changes and CQ is still bisecting the result. *CQ-Master:* RED (#1) Last failure was today due to a build-artifacts failure. a message was sent to patch owner. 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

Re: [URGENT] stop merging to vdsm master
by Sandro Bonazzola 13 Mar '19

13 Mar '19

Adding missing devel list. Il giorno mar 12 mar 2019 alle ore 10:24 Dafna Ron <dron(a)redhat.com> ha scritto: > Hi, > > We have been continuously failing CQ on the vdsm project since 07-03-2019. > > The latest failure is still in vm migration test and root cause is still > pointing to: > > https://gerrit.ovirt.org/#/c/97381/22 - virt: In FIPS mode, use SASL auth > instead of qemu passwords > > Please stop merging until issue is resolved as we are risking further > regressions being merged. > > Thanks, > Dafna > > -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

5 6