May 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1377) Make change-queue changes look like SCM changes in Jenkins
by Barak Korren (oVirt JIRA) 14 May '17

14 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1377?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1377: -------------------------------- Epic Link: OVIRT-400 > Make change-queue changes look like SCM changes in Jenkins > ---------------------------------------------------------- > > Key: OVIRT-1377 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1377 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Jenkins has special UI for showing changes. Since the change-queue is all about changes, it'll be great if Jenkins will "understand" that change-queue changes are also changes. > It looks like Jenkins does not provide an API the manipulate the list of changes included in a particular build. Instead, change lists come from the SCM plugins, so the way to do this is write a special SCM plugin. > [Here|https://wiki.jenkins-ci.org/display/JENKINS/Extend+Jenkins] is the Jenkins plugin documentation. It includes [a tutorial|https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugin…] as well as [specific documentation|https://wiki.jenkins-ci.org/display/JENKINS/Writing+an+SCM+pl…] about SCM plugins. > [Here|https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/huds…] is the source of the Git SCM plugin, as and example of how to write an SCM plugin. -- This message was sent by Atlassian JIRA (v1000.962.0#100041)

1 0

[JIRA] (OVIRT-1375) Re: [ovirt-devel] Vdsm merge rights
by eyal edri [Administrator] (oVirt JIRA) 14 May '17

14 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1375?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1375: -------------------------------------------------- Added. As a general note, any project owner ( in this case vdsm-maintainers ) should have rights to update his project as he sees fit, including add permissions. On Fri, May 12, 2017 at 4:27 PM, Dan Kenigsberg <danken(a)redhat.com> wrote: > infra-support, we have approval. Please add fromani to vdsm-maintainers. > > > On Fri, May 12, 2017 at 4:05 PM, Adam Litke <alitke(a)redhat.com> wrote: > > +2 :) > > > > On Fri, May 12, 2017 at 6:16 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > >> > >> +1 > >> > >> בתאריך יום ו׳, 12 במאי 2017, 12:59, מאת Fabian Deutsch > >> ‏<fdeutsch(a)redhat.com>: > >>> > >>> +1 > >>> > >>> On Fri, May 12, 2017 at 11:25 AM, Edward Haas <ehaas(a)redhat.com> > wrote: > >>> > Good news! +2 > >>> > > >>> > On Fri, May 12, 2017 at 11:27 AM, Piotr Kliczewski > >>> > <pkliczew(a)redhat.com> > >>> > wrote: > >>> >> > >>> >> +1 > >>> >> > >>> >> On Fri, May 12, 2017 at 9:14 AM, Dan Kenigsberg <danken(a)redhat.com> > >>> >> wrote: > >>> >>> > >>> >>> I'd like to nominate Francesco to the vdsm-maintainers > >>> >>> > >>> >>> > >>> >>> https://gerrit.ovirt.org/#/admin/groups/uuid- > becbf722723417c336de6c1646749678acae8b89 > >>> >>> list, so he can merge patches without waiting for Nir, Adam or me. > >>> >>> > >>> >>> I believe that he proved to be thorough and considerate (and > >>> >>> paranoid) > >>> >>> as the job requires. > >>> >>> > >>> >>> Vdsm maintainers, please approve. > >>> >>> > >>> >>> Dan > >>> >> > >>> >> > >>> > > >>> > > >>> > _______________________________________________ > >>> > Devel mailing list > >>> > Devel(a)ovirt.org > >>> > http://lists.ovirt.org/mailman/listinfo/devel > >>> _______________________________________________ > >>> Devel mailing list > >>> Devel(a)ovirt.org > >>> http://lists.ovirt.org/mailman/listinfo/devel > >> > >> > >> _______________________________________________ > >> Devel mailing list > >> Devel(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/devel > > > > > > > > > > -- > > Adam Litke > > > > _______________________________________________ > > Devel mailing list > > Devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > Re: [ovirt-devel] Vdsm merge rights > ----------------------------------- > > Key: OVIRT-1375 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1375 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > infra-support, we have approval. Please add fromani to vdsm-maintainers. > On Fri, May 12, 2017 at 4:05 PM, Adam Litke <alitke(a)redhat.com> wrote: > > +2 :) > > > > On Fri, May 12, 2017 at 6:16 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > >> > >> +1 > >> > >> בתאריך יום ו׳, 12 במאי 2017, 12:59, מאת Fabian Deutsch > >> ‏<fdeutsch(a)redhat.com>: > >>> > >>> +1 > >>> > >>> On Fri, May 12, 2017 at 11:25 AM, Edward Haas <ehaas(a)redhat.com> wrote: > >>> > Good news! +2 > >>> > > >>> > On Fri, May 12, 2017 at 11:27 AM, Piotr Kliczewski > >>> > <pkliczew(a)redhat.com> > >>> > wrote: > >>> >> > >>> >> +1 > >>> >> > >>> >> On Fri, May 12, 2017 at 9:14 AM, Dan Kenigsberg <danken(a)redhat.com> > >>> >> wrote: > >>> >>> > >>> >>> I'd like to nominate Francesco to the vdsm-maintainers > >>> >>> > >>> >>> > >>> >>> https://gerrit.ovirt.org/#/admin/groups/uuid-becbf722723417c336de6c16467496… > >>> >>> list, so he can merge patches without waiting for Nir, Adam or me. > >>> >>> > >>> >>> I believe that he proved to be thorough and considerate (and > >>> >>> paranoid) > >>> >>> as the job requires. > >>> >>> > >>> >>> Vdsm maintainers, please approve. > >>> >>> > >>> >>> Dan > >>> >> > >>> >> > >>> > > >>> > > >>> > _______________________________________________ > >>> > Devel mailing list > >>> > Devel(a)ovirt.org > >>> > http://lists.ovirt.org/mailman/listinfo/devel > >>> _______________________________________________ > >>> Devel mailing list > >>> Devel(a)ovirt.org > >>> http://lists.ovirt.org/mailman/listinfo/devel > >> > >> > >> _______________________________________________ > >> Devel mailing list > >> Devel(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/devel > > > > > > > > > > -- > > Adam Litke > > > > _______________________________________________ > > Devel mailing list > > Devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel -- This message was sent by Atlassian JIRA (v1000.962.0#100041)

1 0

[JIRA] (OVIRT-1375) Re: [ovirt-devel] Vdsm merge rights
by eyal edri [Administrator] (oVirt JIRA) 14 May '17

14 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1375?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1375: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > Re: [ovirt-devel] Vdsm merge rights > ----------------------------------- > > Key: OVIRT-1375 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1375 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > infra-support, we have approval. Please add fromani to vdsm-maintainers. > On Fri, May 12, 2017 at 4:05 PM, Adam Litke <alitke(a)redhat.com> wrote: > > +2 :) > > > > On Fri, May 12, 2017 at 6:16 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > >> > >> +1 > >> > >> בתאריך יום ו׳, 12 במאי 2017, 12:59, מאת Fabian Deutsch > >> ‏<fdeutsch(a)redhat.com>: > >>> > >>> +1 > >>> > >>> On Fri, May 12, 2017 at 11:25 AM, Edward Haas <ehaas(a)redhat.com> wrote: > >>> > Good news! +2 > >>> > > >>> > On Fri, May 12, 2017 at 11:27 AM, Piotr Kliczewski > >>> > <pkliczew(a)redhat.com> > >>> > wrote: > >>> >> > >>> >> +1 > >>> >> > >>> >> On Fri, May 12, 2017 at 9:14 AM, Dan Kenigsberg <danken(a)redhat.com> > >>> >> wrote: > >>> >>> > >>> >>> I'd like to nominate Francesco to the vdsm-maintainers > >>> >>> > >>> >>> > >>> >>> https://gerrit.ovirt.org/#/admin/groups/uuid-becbf722723417c336de6c16467496… > >>> >>> list, so he can merge patches without waiting for Nir, Adam or me. > >>> >>> > >>> >>> I believe that he proved to be thorough and considerate (and > >>> >>> paranoid) > >>> >>> as the job requires. > >>> >>> > >>> >>> Vdsm maintainers, please approve. > >>> >>> > >>> >>> Dan > >>> >> > >>> >> > >>> > > >>> > > >>> > _______________________________________________ > >>> > Devel mailing list > >>> > Devel(a)ovirt.org > >>> > http://lists.ovirt.org/mailman/listinfo/devel > >>> _______________________________________________ > >>> Devel mailing list > >>> Devel(a)ovirt.org > >>> http://lists.ovirt.org/mailman/listinfo/devel > >> > >> > >> _______________________________________________ > >> Devel mailing list > >> Devel(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/devel > > > > > > > > > > -- > > Adam Litke > > > > _______________________________________________ > > Devel mailing list > > Devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel -- This message was sent by Atlassian JIRA (v1000.962.0#100041)

1 0

[JIRA] (OVIRT-1375) Re: [ovirt-devel] Vdsm merge rights
by eyal edri [Administrator] (oVirt JIRA) 14 May '17

14 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1375?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1375: -------------------------------------------------- [~danken(a)redhat.com] added him, but you should be able to do it as well, as project owner, no need to wait for infra team. > Re: [ovirt-devel] Vdsm merge rights > ----------------------------------- > > Key: OVIRT-1375 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1375 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > infra-support, we have approval. Please add fromani to vdsm-maintainers. > On Fri, May 12, 2017 at 4:05 PM, Adam Litke <alitke(a)redhat.com> wrote: > > +2 :) > > > > On Fri, May 12, 2017 at 6:16 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > >> > >> +1 > >> > >> בתאריך יום ו׳, 12 במאי 2017, 12:59, מאת Fabian Deutsch > >> ‏<fdeutsch(a)redhat.com>: > >>> > >>> +1 > >>> > >>> On Fri, May 12, 2017 at 11:25 AM, Edward Haas <ehaas(a)redhat.com> wrote: > >>> > Good news! +2 > >>> > > >>> > On Fri, May 12, 2017 at 11:27 AM, Piotr Kliczewski > >>> > <pkliczew(a)redhat.com> > >>> > wrote: > >>> >> > >>> >> +1 > >>> >> > >>> >> On Fri, May 12, 2017 at 9:14 AM, Dan Kenigsberg <danken(a)redhat.com> > >>> >> wrote: > >>> >>> > >>> >>> I'd like to nominate Francesco to the vdsm-maintainers > >>> >>> > >>> >>> > >>> >>> https://gerrit.ovirt.org/#/admin/groups/uuid-becbf722723417c336de6c16467496… > >>> >>> list, so he can merge patches without waiting for Nir, Adam or me. > >>> >>> > >>> >>> I believe that he proved to be thorough and considerate (and > >>> >>> paranoid) > >>> >>> as the job requires. > >>> >>> > >>> >>> Vdsm maintainers, please approve. > >>> >>> > >>> >>> Dan > >>> >> > >>> >> > >>> > > >>> > > >>> > _______________________________________________ > >>> > Devel mailing list > >>> > Devel(a)ovirt.org > >>> > http://lists.ovirt.org/mailman/listinfo/devel > >>> _______________________________________________ > >>> Devel mailing list > >>> Devel(a)ovirt.org > >>> http://lists.ovirt.org/mailman/listinfo/devel > >> > >> > >> _______________________________________________ > >> Devel mailing list > >> Devel(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/devel > > > > > > > > > > -- > > Adam Litke > > > > _______________________________________________ > > Devel mailing list > > Devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel -- This message was sent by Atlassian JIRA (v1000.962.0#100041)

1 0

[JIRA] (OVIRT-1376) Make mock_runner.sh easer to use locally
by Barak Korren (oVirt JIRA) 14 May '17

14 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1376?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1376: -------------------------------- Summary: Make mock_runner.sh easer to use locally (was: Make mock_runner for easer to use) > Make mock_runner.sh easer to use locally > ---------------------------------------- > > Key: OVIRT-1376 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1376 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Low > > Currently to use '{{mock_runner.sh}}', one needs to: > # Install '{{mock}}' (Might require adding some '{{yum}}' repos, also reuquires one to be running RHEL, CentOS or Fedora in the 1st place) > # Add one`s user account to the '{{mock}}' group (requires logoff and logon) > # Clone the '{{jenkins}}' repo > # Use a long set of command line arguments to make '{{mock_runner.sh}}' use the right '{{mock}}' configuration files > All this is making '{{mock_runner.sh}}' hard and unpopular for local use. Also, no knowing one need to do the above leads to strange errors. We can improve this by: > # Making '{{mock_runner.sh}' check that everything is configured correctly and output meaningful warnings otherwise > # Setup the default so that '{{mock_runner.sh}}' knows how the find the right configuration files > # Package '{{mock_runner.sh}}' in one way or another so that one doesn't need to clone a whole repo to install it. > When it comes to packaging we have several options to consider: > * Using an RPM package: > ** Pros: > *** Familiar format > *** Can include '{{mock}}' as a dependency. > ** Cons: > *** One has to use CentOS or Fedora > *** One most have '{{root}}' permissions to install packages > * Using a self-contained executable built with a tool like [pyinstaller|https://pyinstaller.readthedocs.io/en/stable/operating-mode.html]. > ** Pros: > *** Installation is just downloading a single file to a directory in '{{$PATH}}' > ** Cons: > *** One will probably need to install '{{mock}}' and other dependencies manually. > *** '{{pyinstaller}}' is mostly for Python projects, while '{{mock_runner.sh}}' is a shell script. > * Using a Docker container: > ** Pros: > *** Everything can be pre-configured in the container, including '{{mock}}' itself and all needed permissions > *** Can run on any platform that can run Docker > ** Cons: > *** One needs Docker itself to be installed and configured > *** '{{mock}}' may not run well inside a container > *** Everything that is mounted into the mock environment must first be mounted into the container. This will probably require the container to run in privileged mode. This also means that running the container with the right mounts may be a complicated matter. > *** The container image may end up being quite big. -- This message was sent by Atlassian JIRA (v1000.962.0#100041)

1 0

[JIRA] (OVIRT-1376) Make mock_runner for easer to use
by Barak Korren (oVirt JIRA) 14 May '17

14 May '17

Barak Korren created OVIRT-1376: ----------------------------------- Summary: Make mock_runner for easer to use Key: OVIRT-1376 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1376 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: Low Currently to use '{{mock_runner.sh}}', one needs to: # Install '{{mock}}' (Might require adding some '{{yum}}' repos, also reuquires one to be running RHEL, CentOS or Fedora in the 1st place) # Add one`s user account to the '{{mock}}' group (requires logoff and logon) # Clone the '{{jenkins}}' repo # Use a long set of command line arguments to make '{{mock_runner.sh}}' use the right '{{mock}}' configuration files All this is making '{{mock_runner.sh}}' hard and unpopular for local use. Also, no knowing one need to do the above leads to strange errors. We can improve this by: # Making '{{mock_runner.sh}' check that everything is configured correctly and output meaningful warnings otherwise # Setup the default so that '{{mock_runner.sh}}' knows how the find the right configuration files # Package '{{mock_runner.sh}}' in one way or another so that one doesn't need to clone a whole repo to install it. When it comes to packaging we have several options to consider: * Using an RPM package: ** Pros: *** Familiar format *** Can include '{{mock}}' as a dependency. ** Cons: *** One has to use CentOS or Fedora *** One most have '{{root}}' permissions to install packages * Using a self-contained executable built with a tool like [pyinstaller|https://pyinstaller.readthedocs.io/en/stable/operating-mode.html]. ** Pros: *** Installation is just downloading a single file to a directory in '{{$PATH}}' ** Cons: *** One will probably need to install '{{mock}}' and other dependencies manually. *** '{{pyinstaller}}' is mostly for Python projects, while '{{mock_runner.sh}}' is a shell script. * Using a Docker container: ** Pros: *** Everything can be pre-configured in the container, including '{{mock}}' itself and all needed permissions *** Can run on any platform that can run Docker ** Cons: *** One needs Docker itself to be installed and configured *** '{{mock}}' may not run well inside a container *** Everything that is mounted into the mock environment must first be mounted into the container. This will probably require the container to run in privileged mode. This also means that running the container with the right mounts may be a complicated matter. *** The container image may end up being quite big. -- This message was sent by Atlassian JIRA (v1000.962.0#100041)

1 0

[JIRA] (OVIRT-1376) Make mock_runner for easer to use
by Barak Korren (oVirt JIRA) 14 May '17

14 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1376?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1376: -------------------------------- Epic Link: OVIRT-400 > Make mock_runner for easer to use > --------------------------------- > > Key: OVIRT-1376 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1376 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Low > > Currently to use '{{mock_runner.sh}}', one needs to: > # Install '{{mock}}' (Might require adding some '{{yum}}' repos, also reuquires one to be running RHEL, CentOS or Fedora in the 1st place) > # Add one`s user account to the '{{mock}}' group (requires logoff and logon) > # Clone the '{{jenkins}}' repo > # Use a long set of command line arguments to make '{{mock_runner.sh}}' use the right '{{mock}}' configuration files > All this is making '{{mock_runner.sh}}' hard and unpopular for local use. Also, no knowing one need to do the above leads to strange errors. We can improve this by: > # Making '{{mock_runner.sh}' check that everything is configured correctly and output meaningful warnings otherwise > # Setup the default so that '{{mock_runner.sh}}' knows how the find the right configuration files > # Package '{{mock_runner.sh}}' in one way or another so that one doesn't need to clone a whole repo to install it. > When it comes to packaging we have several options to consider: > * Using an RPM package: > ** Pros: > *** Familiar format > *** Can include '{{mock}}' as a dependency. > ** Cons: > *** One has to use CentOS or Fedora > *** One most have '{{root}}' permissions to install packages > * Using a self-contained executable built with a tool like [pyinstaller|https://pyinstaller.readthedocs.io/en/stable/operating-mode.html]. > ** Pros: > *** Installation is just downloading a single file to a directory in '{{$PATH}}' > ** Cons: > *** One will probably need to install '{{mock}}' and other dependencies manually. > *** '{{pyinstaller}}' is mostly for Python projects, while '{{mock_runner.sh}}' is a shell script. > * Using a Docker container: > ** Pros: > *** Everything can be pre-configured in the container, including '{{mock}}' itself and all needed permissions > *** Can run on any platform that can run Docker > ** Cons: > *** One needs Docker itself to be installed and configured > *** '{{mock}}' may not run well inside a container > *** Everything that is mounted into the mock environment must first be mounted into the container. This will probably require the container to run in privileged mode. This also means that running the container with the right mounts may be a complicated matter. > *** The container image may end up being quite big. -- This message was sent by Atlassian JIRA (v1000.962.0#100041)

1 0

TestOnly bugs, automatic move to ON_QE
by Sandro Bonazzola 14 May '17

14 May '17

Hi, looking at https://bugzilla.redhat.com/show_bug.cgi?id=1446159#c8 I think that condition: [No external trackers attached] can be waived when TestOnly keyword is set, bug is on modified, and target release is set. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 1

oVirt infra daily report - unstable production jobs - 321
by jenkins＠jenkins.phx.ovirt.org 14 May '17

14 May '17

------=_Part_323_716052851.1494716407780 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/321//artifact/exported-a… Cheers, Jenkins ------=_Part_323_716052851.1494716407780 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 13/05/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_323_716052851.1494716407780--

1 0

Automatic move to QE on wrong ovirt-engine tag
by Sandro Bonazzola 13 May '17

13 May '17

According to https://bugzilla.redhat.com/show_bug.cgi?id=1415691#c14 4.1.2 RC2 automatic move to ON_QA was executed on ovirt-engine-4.1.2 tag, but engine tag was ovirt-engine-4.1.2.2. Please re-run it. -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 1