July 2019 - Infra - oVirt List Archives

[JIRA] (OVIRT-1396) Add a new 'test-system-artifacts' Standard-CI stage
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1396?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1396: ---------------------------------- [~bkorren(a)redhat.com] still relevant? > Add a new 'test-system-artifacts' Standard-CI stage > --------------------------------------------------- > > Key: OVIRT-1396 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1396 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > An order to allow building and testing processes for containers to be triggered after package that are needed for them are built, we will introduce the "{{test-system-artifacts}}" standard-CI stage. > This stage will be invoked from the 'experimental' or 'change-queue-tester' pipelines jost like the existing OST-based flows. > In order to provide package and repo information to the std-CI script invoked by this stage we well need to implement OVIRT-1391 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-914) Better arch support for mock_runner.sh
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-914?page=com.atlassian.jira.p… ] Eyal Edri commented on OVIRT-914: --------------------------------- [~bkorren(a)redhat.com] is this still planned/needed? > 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#100105)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Eyal Edri updated OVIRT-886: ---------------------------- Status: Done (was: To Do) > 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#100105)

1 0

[JIRA] (OVIRT-2635) Puppet failed to configure the sudoers file
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2635?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2635: ---------------------------------- [~gbenhaim(a)redhat.com] is this still relevant? > Puppet failed to configure the sudoers file > ------------------------------------------- > > Key: OVIRT-2635 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2635 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gal Ben Haim > Assignee: infra > > We are affected by https://bugs.centos.org/view.php?id=15567 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2187) Create master suite based on FC 28
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2187?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2187: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) Doesn't seem there is need/resources for this effort ATM. Its more likely we'll run oVirt 4.4 on CentOS 8 sooner. > Create master suite based on FC 28 > ---------------------------------- > > Key: OVIRT-2187 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2187 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1956) manual job upgrade options/table are messy
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1956?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1956: ---------------------------------- [~amarchuk] this looks like a text update, can [~szidmi] handle it? > manual job upgrade options/table are messy > ------------------------------------------ > > Key: OVIRT-1956 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1956 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > This was originally reported as [1]. > It's not completely clear what each choice of 'ENGINE_VERSION' and > 'SUITE_TYPE' runs. We should clarify that, add to the table missing > information if needed, including noting somehow combinations that > should not work, if any (e.g. upgrade from 4.0 to 4.2 or master). > In addition to what I wrote in [1], I now checked and saw that a patch > [2] for 4.1 made the change-queue run [3]: > - basic-suite > - upgrade-from-prevrelease - this caused upgrade from 4.0 to 4.1 > - upgrade-from-release - this caused upgrade from 4.1 (released?) to > 4.1 (tested) > Which looks just fine to me, but if that's also supported by the > manual job, it's very hard to guess from the table. > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1552703 > [2] https://gerrit.ovirt.org/89556 > [3] http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1746/artifact/ex… > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2617) Allow rerunning only failed test lanes
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2617?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2617: ----------------------------- Resolution: Fixed Status: Done (was: To Do) This was achived in the end by moving to Prow. There are no plans to add it to STD-CI at this stage. > Allow rerunning only failed test lanes > -------------------------------------- > > Key: OVIRT-2617 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2617 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roman Mohr > Assignee: infra > > Hi, > In KubeVirt we run a lot of differnent test lanes. Even if our tests are > written in a good way and if the underlying CI infra is stable and fast, > there will always be cases where for-whatever reason one or two tests can > fail out of hundreds in a lane. > It would be very helpful if we could have a /retest command or something > similar where only failed lanes are re-run. That would be similar to how it > is handled in Kubernetes. > Right now it is an all-or-nothing thing. > What I would expect, is that it is still possible to see the test history > somewhere then (e.g. the first two attempts where it failed and then the > third one where it succeeds). > Best Regards, > Roman -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#28). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 65 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/28 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 28 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

[JIRA] (OVIRT-2709) Please create new repositories on ovirt github for new Ansible role
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2709?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2709: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Please create new repositories on ovirt github for new Ansible role > ------------------------------------------------------------------- > > Key: OVIRT-2709 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2709 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shirly Radco > Assignee: infra > > Please create following repositories: > ovirt-ansible-origin-on-ovirt > And please assign sradco, rgolan, machacekondra and mwperina as administrators. > Thanks. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2714: ---------------------------------- [~gbenhaim(a)redhat.com] [~dbelenky(a)redhat.com] what do we need to do in order to move the manual OST job to use containers? > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0