- Infra - oVirt List Archives

[JIRA] (OVIRT-1983) Switch to using JJB >= 2.0.6
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1983?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1983: ----------------------------------- Assignee: Barak Korren (was: infra) > Switch to using JJB >= 2.0.6 > ---------------------------- > > Key: OVIRT-1983 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1983 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: Barak Korren > > Version 2.0.6 is the latest released version of JJB at the time of this writing. We've been using a very old development version of JJB (1.4.1.dev50) for a long time and its about time we upgraded. Other then that the post 2.0.0 has one major feature which is Jinja2 support which may be very useful for us. > In order to upgrade, we probably need to implement OVIRT-1466 first. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92435, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Jun '18

24 Jun '18

A system test invoked by the "ovirt-master" change queue including change 92435,1 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 91908,6 (otopi) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91908,6 (otopi) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/92435/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91908/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8326/

1 0

[JIRA] (OVIRT-2231) QEMU can't access "/home/jenkins/*" on FC28 slaves.
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2231?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2231: ------------------------------------- This should probably be done from {{globals_setup.sh}} so setting component as "Jenkins Slaves" > QEMU can't access "/home/jenkins/*" on FC28 slaves. > --------------------------------------------------- > > Key: OVIRT-2231 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2231 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > Lago creates VM images under "/home/jenkins", QEMU process fails to access those images because of missing permissions. > The solution is to set the "execute/search" bit on "/home/jenkins". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2231) QEMU can't access "/home/jenkins/*" on FC28 slaves.
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2231?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2231: -------------------------------- Component/s: (was: Lago) Jenkins Slaves > QEMU can't access "/home/jenkins/*" on FC28 slaves. > --------------------------------------------------- > > Key: OVIRT-2231 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2231 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > Lago creates VM images under "/home/jenkins", QEMU process fails to access those images because of missing permissions. > The solution is to set the "execute/search" bit on "/home/jenkins". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1144) Make projects support more than one CI system
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1144?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1144: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We're not going to support other CI systems. > Make projects support more than one CI system > --------------------------------------------- > > Key: OVIRT-1144 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1144 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: Eyal Edri > Assignee: infra > > Today we use 'automation' dir for running all standard CI flows on oVirt CI. > We need to take into consideration future projects will use multiple CI systems and be a part of multiple projects. > So a question is raised on how will the structure of dirs/files served in oVirt will look like. > One suggestion was to use .ovirtci which will translate to all the needs the oVirt CI will need. > There can be other options, this is the place to discuss them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-891) Add support for verification / testing of containers in standard CI
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-891?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-891: ------------------------------- Resolution: Fixed Status: Done (was: To Do) We already have support for doing various things with containers in STDCI. > Add support for verification / testing of containers in standard CI > ------------------------------------------------------------------- > > Key: OVIRT-891 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-891 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: Eyal Edri > Assignee: infra > > From check-patch scripts, verifying docker files to running system test suit on the new image. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-886: ------------------------------- Epic Link: (was: OVIRT-400) > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-886: ------------------------------- Epic Link: (was: OVIRT-400) > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-886: ------------------------------- Component/s: (was: oVirt CI) mock_runner > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-914) Better arch support for mock_runner.sh
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-914?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-914: ------------------------------- Epic Link: (was: OVIRT-400) > Better arch support for mock_runner.sh > -------------------------------------- > > Key: OVIRT-914 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-914 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock_runner.sh, standard-ci > > We managed to us "{{mock_runner.sh}}" in multi-arch so far because it was flexible enough to allow us to select the chroot file. > The issue is that mock_runner does not actually *know* the arch we are running on so we can`t:: > * do different mounts per-arch > * install different packages per-arch > * have different {{check_*}} scripts per-arch -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0