[JIRA] (OVIRT-903) master-to-master CI upgrade tests
Yedidyah Bar David created OVIRT-903: Summary: master-to-master CI upgrade tests Key: OVIRT-903 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Hi all, Recently a patch to the engine [1] added a new package, with a certain set of dependencies, which broke upgrade. This is similar to [2] but for a new package. CI wasn't affected, I think because of [3]. To make CI test such flows, we should have a job that: 1. Builds, installs and sets up the version we want to test 2. Pushes a dummy change to the local git repo (to force a new version), build the patched tree, create a yum repo with the build and add it to yum.repos.d. 3. yum update 4. engine-setup Another option is to revert [3], or to duplicate - have both "upgrade current to self" and "upgrade latest snapshot to current". The downside is that it will be checked later than above plan - instead of in the same build, will only be tested in the first build that uses the snapshot after it was updated, and also will be misleading, as the reason why that job failed will not be apparent (which was why [3] was added). Please handle. I can of course try to help. Best, [1] https://gerrit.ovirt.org/66999 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 [3] https://gerrit.ovirt.org/67263 -- Didi -- This message was sent by Atlassian JIRA (v1000.610.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-903) master-to-master CI upgrade tests
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23805#comment-23805 ] eyal edri [Administrator] commented on OVIRT-903: - We have master->master upgrade job: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/ > master-to-master CI upgrade tests > - > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: infra > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.610.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-903) master-to-master CI upgrade tests
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23817#comment-23817 ] Yedidyah Bar David commented on OVIRT-903: -- On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt Indeed, and I explained in the ticket why it's not enough as-is. Best, -- Didi > master-to-master CI upgrade tests > - > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: infra > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.610.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-903) master-to-master CI upgrade tests
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23818#comment-23818 ] eyal edri [Administrator] commented on OVIRT-903: - well, depending on the amount of effort needed to update the job, we might want to wait with it until the jobs are moved to an ost suit, which is in progress. On Dec 4, 2016 13:07, "Yedidyah Bar David" wrote: On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel&focusedCommentId=23805#comment-23805 ] from-master_el7_merged/ Indeed, and I explained in the ticket why it's not enough as-is. Best, -- Didi ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra > master-to-master CI upgrade tests > - > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: infra > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.610.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-903) master-to-master CI upgrade tests
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23819#comment-23819 ] eyal edri [Administrator] commented on OVIRT-903: - Also, you might want to change the ticket name for " fixing/updating upgrade job" the current title is misleading On Sun, Dec 4, 2016 at 1:11 PM, eyal edri [Administrator] (oVirt JIRA) < -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > master-to-master CI upgrade tests > - > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: infra > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.610.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-903) master-to-master CI upgrade tests
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-903: Epic Link: OVIRT-400 > master-to-master CI upgrade tests > - > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: infra > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.620.0#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-903) master-to-master CI upgrade tests
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-903: Epic Link: OVIRT-400 > master-to-master CI upgrade tests > - > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: infra > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.620.0#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-903) master-to-master CI upgrade tests
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-903: --- Assignee: Daniel Belenky (was: infra) reminder to add to upgrade suites > master-to-master CI upgrade tests > - > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: Yedidyah Bar David >Assignee: Daniel Belenky > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.621.5#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [JIRA] (OVIRT-903) master-to-master CI upgrade tests
On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt JIRA) wrote: > > [ > https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23805#comment-23805 > ] > > eyal edri [Administrator] commented on OVIRT-903: > - > > We have master->master upgrade job: > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/ Indeed, and I explained in the ticket why it's not enough as-is. Best, -- Didi ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [JIRA] (OVIRT-903) master-to-master CI upgrade tests
well, depending on the amount of effort needed to update the job, we might want to wait with it until the jobs are moved to an ost suit, which is in progress. On Dec 4, 2016 13:07, "Yedidyah Bar David" wrote: On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt JIRA) wrote: > > [ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com. atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel&focusedCommentId=23805#comment-23805 ] > > eyal edri [Administrator] commented on OVIRT-903: > - > > We have master->master upgrade job: > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade- from-master_el7_merged/ Indeed, and I explained in the ticket why it's not enough as-is. Best, -- Didi ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: [JIRA] (OVIRT-903) master-to-master CI upgrade tests
Also, you might want to change the ticket name for " fixing/updating upgrade job" the current title is misleading On Sun, Dec 4, 2016 at 1:11 PM, eyal edri [Administrator] (oVirt JIRA) < j...@ovirt-jira.atlassian.net> wrote: > > [ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com. > atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=23818#comment-23818 ] > > eyal edri [Administrator] commented on OVIRT-903: > - > > well, depending on the amount of effort needed to update the job, we > might want to wait with it until the jobs are moved to an ost suit, which > is in progress. > > On Dec 4, 2016 13:07, "Yedidyah Bar David" wrote: > > On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt > atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=23805#comment-23805 ] > from-master_el7_merged/ > > Indeed, and I explained in the ticket why it's not enough as-is. > > Best, > -- > Didi > ___ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > > > master-to-master CI upgrade tests > > - > > > > Key: OVIRT-903 > > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > > Project: oVirt - virtualization made easy > > Issue Type: By-EMAIL > >Reporter: Yedidyah Bar David > >Assignee: infra > > > > Hi all, > > Recently a patch to the engine [1] added a new package, > > with a certain set of dependencies, which broke upgrade. > > This is similar to [2] but for a new package. > > CI wasn't affected, I think because of [3]. > > To make CI test such flows, we should have a job that: > > 1. Builds, installs and sets up the version we want to test > > 2. Pushes a dummy change to the local git repo (to force > > a new version), build the patched tree, create a yum repo > > with the build and add it to yum.repos.d. > > 3. yum update > > 4. engine-setup > > Another option is to revert [3], or to duplicate - have > > both "upgrade current to self" and "upgrade latest snapshot > > to current". The downside is that it will be checked later > > than above plan - instead of in the same build, will only > > be tested in the first build that uses the snapshot after > > it was updated, and also will be misleading, as the reason > > why that job failed will not be apparent (which was why > > [3] was added). > > Please handle. I can of course try to help. Best, > > [1] https://gerrit.ovirt.org/66999 > > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > > [3] https://gerrit.ovirt.org/67263 > > -- > > Didi > > > > -- > This message was sent by Atlassian JIRA > (v1000.610.2#100023) > ___ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
