February 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-922) Add new project to standard ci from github
by eyal edri [Administrator] (oVirt JIRA) 14 Feb '17

14 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-922: ------------------------------------------------- Won't it make sense to start with moving https://github.com/machacekondra/ovirt-tests under the oVirt organization in GitHub? If you would want to trigger jobs from GitHub then its mandatory, as we don't support triggering from private repos. Also, you might want to try out our staging jenkins if you want to try/test it before deploying to production. [~ederevea] can help with accessing it. > 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.747.1#100028)

1 0

[ OST Failure Report ] [ rhv master ] [ 14.02.17 ] [vm_run]
by Dusan Fodor 14 Feb '17

14 Feb '17

Hi, vm_run fails with following error: 12:01:21 [basic_suit_el7] # vm_run: 12:04:27 [basic_suit_el7] * Collect artifacts: 12:04:27 [basic_suit_el7] * Collect artifacts: ERROR (in 0:00:01) 12:04:27 [basic_suit_el7] # vm_run: ERROR (in 0:03:05) 12:04:27 [basic_suit_el7] # snapshots_merge: 12:08:35 [basic_suit_el7] Error while running thread 12:08:35 [basic_suit_el7] Traceback (most recent call last): 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 56, in _ret_via_queue 12:08:35 [basic_suit_el7] queue.put({'return': func()}) 12:08:35 [basic_suit_el7] File "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py", line 427, in snapshot_live_merge 12:08:35 [basic_suit_el7] lambda: api.vms.get(VM0_NAME).status.state == 'up' 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 260, in assert_true_within_short 12:08:35 [basic_suit_el7] assert_equals_within_short(func, True, allowed_exceptions) 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 244, in assert_equals_within_short 12:08:35 [basic_suit_el7] func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions 12:08:35 [basic_suit_el7] File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 230, in assert_equals_within 12:08:35 [basic_suit_el7] '%s != %s after %s seconds' % (res, value, timeout) 12:08:35 [basic_suit_el7] AssertionError: False != True after 180 seconds 12:08:35 [basic_suit_el7] * Collect artifacts: 12:08:36 [basic_suit_el7] * Collect artifacts: ERROR (in 0:00:02) 12:08:36 [basic_suit_el7] # snapshots_merge: ERROR (in 0:04:10) 12:08:36 [basic_suit_el7] # suspend_resume_vm: 12:08:36 [basic_suit_el7] * Collect artifacts: 12:08:38 [basic_suit_el7] * Collect artifacts: ERROR (in 0:00:01) 12:08:38 [basic_suit_el7] # suspend_resume_vm: ERROR (in 0:00:02) Link to job: http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper…

1 0

[JIRA] (OVIRT-1149) Add VDSM container build in build-artifacts stage
by eyal edri [Administrator] (oVirt JIRA) 14 Feb '17

14 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1149?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1149: --------------------------------------------- Description: As part of [1], we need to start building VDSM as container and publish it so that OST can consume it and verify it. This ticket is for tracking progress on VDSM, a similar ticket will be opened for ovirt-engine. [1] https://ovirt-jira.atlassian.net/browse/OST-39 was: As part of [1], we need to start building ovirt-engine as container and publish it so that OST can consume it and verify it. This ticket is for tracking progress on ovirt-engine, a similar ticket will be opened for VDSM. [1] https://ovirt-jira.atlassian.net/browse/OST-39 > Add VDSM container build in build-artifacts stage > ------------------------------------------------- > > Key: OVIRT-1149 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1149 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > As part of [1], we need to start building VDSM as container and publish it so that OST can consume it and verify it. > This ticket is for tracking progress on VDSM, a similar ticket will be opened for ovirt-engine. > [1] https://ovirt-jira.atlassian.net/browse/OST-39 -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1149) Add VDSM container build in build-artifacts stage
by eyal edri [Administrator] (oVirt JIRA) 14 Feb '17

14 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1149?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1149: --------------------------------------------- Epic Link: OVIRT-400 > Add VDSM container build in build-artifacts stage > ------------------------------------------------- > > Key: OVIRT-1149 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1149 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > As part of [1], we need to start building ovirt-engine as container and publish it so that OST can consume it and verify it. > This ticket is for tracking progress on ovirt-engine, a similar ticket will be opened for VDSM. > [1] https://ovirt-jira.atlassian.net/browse/OST-39 -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1149) Add VDSM container build in build-artifacts stage
by eyal edri [Administrator] (oVirt JIRA) 14 Feb '17

14 Feb '17

eyal edri [Administrator] created OVIRT-1149: ------------------------------------------------ Summary: Add VDSM container build in build-artifacts stage Key: OVIRT-1149 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1149 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Priority: High As part of [1], we need to start building ovirt-engine as container and publish it so that OST can consume it and verify it. This ticket is for tracking progress on ovirt-engine, a similar ticket will be opened for VDSM. [1] https://ovirt-jira.atlassian.net/browse/OST-39 -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1148) Add ovirt-engine container build in build-artifacts stage
by eyal edri [Administrator] (oVirt JIRA) 14 Feb '17

14 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1148?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1148: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > Add ovirt-engine container build in build-artifacts stage > --------------------------------------------------------- > > Key: OVIRT-1148 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1148 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: Daniel Belenky > Priority: High > > As part of [1], we need to start building ovirt-engine as container and publish it so that OST can consume it and verify it. > This ticket is for tracking progress on ovirt-engine, a similar ticket will be opened for VDSM. > [1] https://ovirt-jira.atlassian.net/browse/OST-39 -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1148) Add ovirt-engine container build in build-artifacts stage
by eyal edri [Administrator] (oVirt JIRA) 14 Feb '17

14 Feb '17

eyal edri [Administrator] created OVIRT-1148: ------------------------------------------------ Summary: Add ovirt-engine container build in build-artifacts stage Key: OVIRT-1148 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1148 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Priority: High As part of [1], we need to start building ovirt-engine as container and publish it so that OST can consume it and verify it. This ticket is for tracking progress on ovirt-engine, a similar ticket will be opened for VDSM. [1] https://ovirt-jira.atlassian.net/browse/OST-39 -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1148) Add ovirt-engine container build in build-artifacts stage
by eyal edri [Administrator] (oVirt JIRA) 14 Feb '17

14 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1148?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1148: --------------------------------------------- Epic Link: OVIRT-400 > Add ovirt-engine container build in build-artifacts stage > --------------------------------------------------------- > > Key: OVIRT-1148 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1148 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > As part of [1], we need to start building ovirt-engine as container and publish it so that OST can consume it and verify it. > This ticket is for tracking progress on ovirt-engine, a similar ticket will be opened for VDSM. > [1] https://ovirt-jira.atlassian.net/browse/OST-39 -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5296 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 14 Feb '17

14 Feb '17

------=_Part_97_1536078182.1487061749199 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5296/, Build Number: 5296, Build Status: FAILURE ------=_Part_97_1536078182.1487061749199--

1 1

[JIRA] (OVIRT-1047) Build and check KubeVirt Demo image
by Barak Korren (oVirt JIRA) 14 Feb '17

14 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1047?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1047: ------------------------------------- Well, there is a big conceptual difference between '{{.travisci}}' and '{{automation}}'. While '{{.travisci}}' was designed as just the signalling interface for the Travis system. '{{automation}}' was designed to generalize the interface of build systems, so that a generic, isolating, dependency-resolving build system could be created. It was always a goal to also allow running the build/test process locally. In that sense '{{automation}}' is considered as inseparable from the code as its '{{Makefile}}'. > Build and check KubeVirt Demo image > ----------------------------------- > > Key: OVIRT-1047 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1047 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Fabian Deutsch > Assignee: infra > Priority: High > Labels: kubevirt > > Hey, > a job is needed which will build the following image: > https://github.com/kubevirt/demo > $ make clean build check > should do the job. virt-builder and guestfish are used. -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0