[JIRA] (OVIRT-1956) manual job upgrade options/table are messy
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39476#comment-39476 ] 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/exported-artifacts/ > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/KG564DMCRUMRNYBGIDFRERDVJJEPF2IX/
[JIRA] (OVIRT-1956) manual job upgrade options/table are messy
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liora Milbaum reassigned OVIRT-1956: Assignee: infra (was: Daniel Belenky) > 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/exported-artifacts/ > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/WUOVZ2L7XKHG4BDDGJ5T4XCCPOG6EVG2/
[JIRA] (OVIRT-1956) manual job upgrade options/table are messy
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri reassigned OVIRT-1956: Assignee: Daniel Belenky (was: infra) > 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: Daniel Belenky > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1956) manual job upgrade options/table are messy
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/exported-artifacts/ -- Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
