[JIRA] (OVIRT-1956) manual job upgrade options/table are messy

2 Apr 2018

      This is a multi-part message in MIME format...

------------=_1522648927-23302-146
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Yedidyah Bar David created OVIRT-1956:
-----------------------------------------

             Summary: 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: By-EMAIL
            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/exp...
-- 
Didi

--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)

------------=_1522648927-23302-146
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<h3>Yedidyah Bar David created OVIRT-1956:</h3>
<pre>   Summary: 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: By-EMAIL
  Reporter: Yedidyah Bar David
  Assignee: infra</pre>
<p>Hi,</p>
<p>This was originally reported as [1].</p>
<p>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).</p>
<p>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]:</p>
<ul><li><p>basic-suite</p></li>
<li><p>upgrade-from-prevrelease – this caused upgrade from 4.0 to 4.1</p></li>
<li><p>upgrade-from-release – this caused upgrade from 4.1 (released?) to</p></li></ul>
<p>4.1 (tested)</p>
<p>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.</p>
<p>[1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1552703">https://bugzilla.redhat.com/show_bug.cgi?id=1552703</a> [2] <a href="https://gerrit.ovirt.org/89556">https://gerrit.ovirt.org/89556</a> [3] <a href="http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1746/artifact/exported-artifacts/">http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1746/artifact/exported-artifacts/</a> — Didi</p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p>

<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3t..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>

------------=_1522648927-23302-146--

Yedidyah Bar David (oVirt JIRA)

tags

participants (1)