Bug 1552703 - manual job upgrade options/table are messy
Summary: manual job upgrade options/table are messy
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-system-tests
Classification: Community
Component: General
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Eyal Edri
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-07 14:58 UTC by Yedidyah Bar David
Modified: 2018-03-07 15:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-07 15:32:06 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Yedidyah Bar David 2018-03-07 14:58:12 UTC
Description of problem:

The manual job [1] has:

ENGINE_VERSION: drop down that lets you pick 4.1, 4.2 or master

Below that, a text table that does not mention 4.2 at all, and says that choosing engine '4.1' and then 'upgrade-from-release' will update _from_ master to 4.1.

SUITE_TYPE: drop down that includes "upgrade from release" and "upgrade from prev release".

It's not clear what the current options are.

Do we want to test upgrade-from-prevrelease at all? Current 4.1 and 4.2 prevent that (i.e. upgrade from 3.6 and 4.0, respectively). master (4.3) still allows upgrade from 4.1, but mainly because no-one yet pushed a patch to prevent that - there are no plans that I know of to allow that officially.

So, perhaps:

- Drop prevrelease altogether

- Allow only these upgrades:
4.0->4.1 (or just remove 4.1)
4.1->4.2
4.2->master

- Drop the table, or fix it to say the above

[1] http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/build?delay=0sec

Comment 1 Eyal Edri 2018-03-07 15:32:06 UTC
please open a JIRA ticket, this is a Jenkins UI issue, OST in Bugzilla is for tests failures or updates, mostly for oVirt developers.


Note You need to log in before you can comment on or make changes to this bug.