December 2016 - Infra - Ovirt List Archives

[JIRA] (OVIRT-884) check workspace cleanup task

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-884?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-884: -------------------------------------------- Epic Link: OVIRT-403 > check workspace cleanup task > ---------------------------- > > Key: OVIRT-884 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-884 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Reporter: Evgheni Dereveanchin > Assignee: infra > > Recently we get lots of failures due to dirty workspaces on Jenkins slaves. > The cleanup task is reporting success, yet its runtime is usually below 1 second, so it may not be running properly and causing the failures: > http://jenkins.ovirt.org/job/system_cleanup-workspaces/5261/console > Need to check this job to ensure it actually cleans up workspaces. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-884) check workspace cleanup task

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-884?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-884: -------------------------------------------- Epic Link: OVIRT-403 > check workspace cleanup task > ---------------------------- > > Key: OVIRT-884 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-884 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Reporter: Evgheni Dereveanchin > Assignee: infra > > Recently we get lots of failures due to dirty workspaces on Jenkins slaves. > The cleanup task is reporting success, yet its runtime is usually below 1 second, so it may not be running properly and causing the failures: > http://jenkins.ovirt.org/job/system_cleanup-workspaces/5261/console > Need to check this job to ensure it actually cleans up workspaces. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-867) Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing!

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-867?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-867: -------------------------------------------- Resolution: Fixed Status: Done (was: To Do) job is back to stable after removing bad mirror, there is another task to move these to standard CI so they can benefit from the proxy as well > Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing! > ------------------------------------------------------------------------------------ > > Key: OVIRT-867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-867 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > *00:01:53.955* Can't download or revert repomd.xml for > check-epel-el7*00:01:53.955* Some dependencies may not be complete for > this repository*00:01:53.956* Run as root to get all dependencies or > use -t to enable a user temp cache > Can you check? looks like it's not possible to update local cache of metadata. > On Fri, Nov 25, 2016 at 1:07 PM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/ > > Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/92/ > > Build Number: 92 > > Build Status: Still Failing > > Triggered By: Started by user Sandro Bonazzola > > > > ------------------------------------- > > Changes Since Last Success: > > ------------------------------------- > > Changes for Build #89 > > [Eyal Edri] deploy ovirt-engine-cli 3.6 to 4.0 and master repos as well > > > > [Yedidyah Bar David] master_upgrade_from_master: Upgrade to self instead > > of snapshot > > > > > > Changes for Build #90 > > No changes > > > > Changes for Build #91 > > No changes > > > > Changes for Build #92 > > No changes > > > > > > > > ----------------- > > Failed Tests: > > ----------------- > > No tests ran. > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-922) Add new project to standard ci from github

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira... ] eyal edri [Administrator] commented on OVIRT-922: ------------------------------------------------- Also, can you rename the repo to something with more context? ovirt-tests is very generic name ( we have system tests / functional tests/ unit tests ). If its ansbile, maybe worth calling it ovirt-ansible-tests or something else with ansible ) > Add new project to standard ci from github > ------------------------------------------ > > Key: OVIRT-922 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > I would like to request a jenkins machine for Ansible modules tests. > Those tests needs host with nested virtualization as it will create a few virtual machines for tests. > Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. > Then I would need some possibility to run this job from a hook from github, when new commit is pushed. > The tests are described here for an idea: > https://github.com/machacekondra/ovirt-tests > Would that be possible? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-898) Send committers in test experimental job's email

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-898?page=com.atlassian.jira... ] eyal edri [Administrator] reassigned OVIRT-898: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > Send committers in test experimental job's email > ------------------------------------------------ > > Key: OVIRT-898 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-898 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Daniel Belenky > > I can get the job that triggered deploy experimental and test experimental and get commiters from that job. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-922) Add new project to standard ci from github

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-922: -------------------------------------------- Summary: Add new project to standard ci from github (was: Please create new jenkins machine for Ansible modules tests) > Add new project to standard ci from github > ------------------------------------------ > > Key: OVIRT-922 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > I would like to request a jenkins machine for Ansible modules tests. > Those tests needs host with nested virtualization as it will create a few virtual machines for tests. > Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. > Then I would need some possibility to run this job from a hook from github, when new commit is pushed. > The tests are described here for an idea: > https://github.com/machacekondra/ovirt-tests > Would that be possible? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-922) Please create new jenkins machine for Ansible modules tests

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira... ] eyal edri [Administrator] commented on OVIRT-922: ------------------------------------------------- We don't maintain 'special' machines or mange them with any CM tools like we did in the past, instead we use mock to give an isolated environment for any testing you'd like to run and you have full control over what is running there. You will need to make your project part of the 'standard ci' flow and add automation dir under the root folder. ( see other projects for e.g, like ovirt-engine ). see [1] for detailed info. But, as an example, you said you need vagrant and ansible installed, then you'll just need to add them to the .packages file in the automation dir under check-patch or check-merge depends on when you want it tested. We don't support yet GitHub as a standard CI project, there is another ticket to add support for it ( as part of adding ovirt-web-ui project ), so it might take bit more time. (for projects in Gerrit is straightforward now) [1] http://infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards.html > Please create new jenkins machine for Ansible modules tests > ----------------------------------------------------------- > > Key: OVIRT-922 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > I would like to request a jenkins machine for Ansible modules tests. > Those tests needs host with nested virtualization as it will create a few virtual machines for tests. > Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. > Then I would need some possibility to run this job from a hook from github, when new commit is pushed. > The tests are described here for an idea: > https://github.com/machacekondra/ovirt-tests > Would that be possible? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-922) Please create new jenkins machine for Ansible modules tests

by Ondra Machacek (oVirt JIRA)

Ondra Machacek created OVIRT-922: ------------------------------------ Summary: Please create new jenkins machine for Ansible modules tests Key: OVIRT-922 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Reporter: Ondra Machacek Assignee: infra I would like to request a jenkins machine for Ansible modules tests. Those tests needs host with nested virtualization as it will create a few virtual machines for tests. Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. Then I would need some possibility to run this job from a hook from github, when new commit is pushed. The tests are described here for an idea: https://github.com/machacekondra/ovirt-tests Would that be possible? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-922) Please create new jenkins machine for Ansible modules tests

by Ondra Machacek (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira... ] Ondra Machacek commented on OVIRT-922: -------------------------------------- CC [~mperina] [~oourfali(a)redhat.com] > Please create new jenkins machine for Ansible modules tests > ----------------------------------------------------------- > > Key: OVIRT-922 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > I would like to request a jenkins machine for Ansible modules tests. > Those tests needs host with nested virtualization as it will create a few virtual machines for tests. > Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. > Then I would need some possibility to run this job from a hook from github, when new commit is pushed. > The tests are described here for an idea: > https://github.com/machacekondra/ovirt-tests > Would that be possible? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-908) jenkins failures

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-908?page=com.atlassian.jira... ] eyal edri [Administrator] reassigned OVIRT-908: ----------------------------------------------- Assignee: Shlomo Ben David (was: infra) > jenkins failures > ---------------- > > Key: OVIRT-908 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-908 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Polednik > Assignee: Shlomo Ben David > > Hi, > after pushing update to my patch series[1], I've been greeted with > unhealthy amount of jenkins failures. Actually, it's a single fail > that affected all but one(!) patch. > The failure: ERROR: Command failed. See logs for output. [2] > Can we get these issues solved or have some > false-positive/false-negative protection (preferably both)? > [1] https://gerrit.ovirt.org/#/q/topic:hostdev-caching > [2] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5788/con... > Regards, > mpolednik -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra December 2016