[ovirt-devel] oci: command line tool for oVirt CI

2019-03-15 Thread Nir Soffer 
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
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/GU4SE5DGZ3UW4KUK4GL7V55R3RWZKAVB/

[ovirt-devel] [Ovirt] [CQ weekly status] [15-03-2019]

2019-03-15 Thread Dafna Ron 
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-queue-tester/

[2]
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change-queue-tester/

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 failuresYELLOW (#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)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SH57CDHCMRYL5PGQFP3E4KYATT7TFKB3/

[ovirt-devel] Re: OST hyperconverged master fails

2019-03-15 Thread Dafna Ron 
Hi Greg,

I just ran it locally myself and it ran properly.
are you running it from the ds-ovirt-system-tests project or from
ovirt-system-tests project?

Thanks,
Dafna


On Fri, Mar 15, 2019 at 10:45 AM Greg Sheremeta  wrote:

> 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
>
> 
>
> gsher...@redhat.comIRC: gshereme
> 
> ___
> Infra mailing list -- in...@ovirt.org
> To unsubscribe send an email to infra-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/in...@ovirt.org/message/DAXCULUHLQMNXM3CA5BXVERPBSYVKOTK/
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ST6DK6UJJDXP774OUAATZ35IVD3DWYFS/

[ovirt-devel] OST hyperconverged master fails

2019-03-15 Thread Greg Sheremeta 
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



gsher...@redhat.comIRC: gshereme

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/DAXCULUHLQMNXM3CA5BXVERPBSYVKOTK/

[ovirt-devel] Are we ready to branch ovirt-engine for 4.3?

2019-03-15 Thread Sandro Bonazzola 
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 RHV

Red Hat EMEA 

sbona...@redhat.com

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/KDDEALQJHM33GDZPM77SX6CEYKPE2CED/