- Infra - oVirt List Archives

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by Dafna Ron (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520353920-12885-275 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Dafna Ron created OVIRT-1919: -------------------------------- Summary: missing documentation on ci re-merge please in github Key: OVIRT-1919 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra we needed to re-merge a change from github and did not know how to do it. looking at the documentation it either does not exist or not documented. http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520353920-12885-275 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Dafna Ron created OVIRT-1919:</h3> <pre> Summary: missing documentation on ci re-merge please in github Key: OVIRT-1919 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra</pre> we needed to re-merge a change from github and did not know how to do it. looking at the documentation it either does not exist or not documented. <a href="http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…">http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub…</a> I am assuming that we can re-merge so opening a jira for the doc. — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1520353920-12885-275--

1 0

Fwd: Still Failing: oVirt/ovirt-engine#4888 (master - 1cc377f)
by Sandro Bonazzola 06 Mar '18

06 Mar '18

Hi, not sure who's monitoring Travis failures and maintaining Travis jobs, but looks like we have an error in the test suite It's currently failing on: ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.ovirt.engine.core.dal.job.ExecutionMessageDirectorTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.234 sec Running org.ovirt.engine.core.dal.dbbroker.DbConnectionUtilTest Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.936 sec <<< FAILURE! org.ovirt.engine.core.dal.dbbroker.DbConnectionUtilTest Time elapsed: 936 sec <<< FAILURE! java.lang.AssertionError: Unable to init tests Looks pretty much similar to what happens in jenkins for fcraw builds, tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1550033 ---------- Forwarded message ---------- From: Travis CI <builds(a)travis-ci.org> Date: 2018-03-06 7:53 GMT+01:00 Subject: Still Failing: oVirt/ovirt-engine#4888 (master - 1cc377f) To: sbonazzo(a)redhat.com *oVirt / ovirt-engine <https://travis-ci.org/oVirt/ovirt-engine?utm_source=email&utm_medium=notifi…>* (master <https://github.com/oVirt/ovirt-engine/tree/master>) Build #4888 is still failing. <https://travis-ci.org/oVirt/ovirt-engine/builds/349675802?utm_source=email&…> 4 minutes and 38 seconds *Yedidyah Bar David* 1cc377f <https://github.com/oVirt/ovirt-engine/commit/1cc377fa30286733aeb68aa75a5bc8…> Changeset → <https://github.com/oVirt/ovirt-engine/compare/6c9465241694...1cc377fa3028> packaging: setup: postgres95: Refuse to upgrade if new data dir is not empty Change-Id: I9f69ceb2b8ea773d1bb883c3e81734a3c4c8af3c Bug-Url: https://bugzilla.redhat.com/1546771 Signed-off-by: Yedidyah Bar David <didi(a)redhat.com> *Want to know about upcoming build environment updates?* Would you like to stay up-to-date with the upcoming Travis CI build environment updates? We set up a mailing list for you! Sign up here <http://eepurl.com/9OCsP>. Documentation <https://docs.travis-ci.com> about Travis CI Need help? Mail support <support(a)travis-ci.com>! Choose who receives these build notification emails in your configuration file <https://docs.travis-ci.com/user/notifications>. *Would you like to test your private code?* Travis CI for Private Projects <https://travis-ci.com?utm_source=build_email_footer&utm_campaign=travis-ci.…> could be your new best friend! -- 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>

3 4

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Dafna Ron (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520344092-23374-193 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-1918: ---------------------------------- we monitor and report an issue once its identified. we do not however, report every failed change which has failed because of the original root cause. I do try to go and either re-trigger or re-merge changes if they failed cq once the root cause is fixed but if an issue lasts for a day or two it would be difficult to make sure we do not miss anything. maybe we need to add a warning message after an issue is fixed which lists all changes that need to be re-triggered or re-merged? > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520344092-23374-193 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ]</pre> <h3>Dafna Ron commented on OVIRT-1918:</h3> we monitor and report an issue once its identified. we do not however, report every failed change which has failed because of the original root cause. I do try to go and either re-trigger or re-merge changes if they failed cq once the root cause is fixed but if an issue lasts for a day or two it would be difficult to make sure we do not miss anything. maybe we need to add a warning message after an issue is fixed which lists all changes that need to be re-triggered or re-merged? <blockquote><h3>Single project tests in change-queue-tester</h3> <pre> Key: OVIRT-1918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra</pre> Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again “ci re-merge please” again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on tested repo. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1520344092-23374-193--

1 0

[JIRA] (OVIRT-1861) Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available
by eyal edri (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520343278-10207-157 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [ https://ovirt-jira.atlassian.net/browse/OVIRT-1861?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri reassigned OVIRT-1861: -------------------------------- Assignee: Marc Dequ=C3=A8nes (Duck) (was: infra) > Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available > ------------------------------------------------------------ > > Key: OVIRT-1861 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1861 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: wiki (MediaWiki) > Reporter: sbonazzo > Assignee: Marc Dequ=C3=A8nes (Duck) > > 2018-01-24 13:47 GMT+01:00 Arman Khalatyan <arm2arm(a)gmail.com>: > > Thanks for the announcement. > > A little comment: could you please fix the line yum install > > <http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm > > <http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm%3E> > > There is an extra '<' symbol there since 4.0.x :=3D) > > > > > Thanks for the feedback, I opened > https://github.com/oVirt/ovirt-site/issues/1503 to track this. > Opening a ticket on infra as well for further investigations. > > > > On Wed, Jan 24, 2018 at 12:00 PM, Lev Veyde <lveyde(a)redhat.com> wrote: > > > >> The oVirt Project is pleased to announce the availability of the oVirt > >> 4.1.9 release, as of January 24th, 2017 > >> > >> This update is the ninth in a series of stabilization updates to the 4= .1 > >> series. > >> > >> Please note that no further updates will be issued for the 4.1 series. > >> We encourage users to upgrade to 4.2 series to receive new features and > >> updates. > >> > >> This release is available now for: > >> * Red Hat Enterprise Linux 7.4 or later > >> * CentOS Linux (or similar) 7.4 or later > >> > >> This release supports Hypervisor Hosts running: > >> * Red Hat Enterprise Linux 7.4 or later > >> * CentOS Linux (or similar) 7.4 or later > >> * oVirt Node 4.1 > >> > >> See the release notes [1] for installation / upgrade instructions and > >> a list of new features and bugs fixed. > >> > >> Notes: > >> - oVirt Appliance is already available > >> - oVirt Live is already available [2] > >> - oVirt Node will be available soon [2] > >> > >> Additional Resources: > >> * Read more about the oVirt 4.1.9 release highlights:http://www.ovirt.= or > >> g/release/4.1.9/ > >> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt > >> * Check out the latest project news on the oVirt blog: > >> http://www.ovirt.org/blog/ > >> > >> [1] http://www.ovirt.org/release/4.1.9/ > >> [2] http://resources.ovirt.org/pub/ovirt-4.1/iso/ > >> > >> -- > >> > >> Lev Veyde > >> > >> Software Engineer, RHCE | RHCVA | MCITP > >> > >> Red Hat Israel > >> > >> <https://www.redhat.com> > >> > >> lev(a)redhat.com | lveyde(a)redhat.com > >> <https://red.ht/sig> > >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > >> > >> _______________________________________________ > >> Users mailing list > >> Users(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/users > >> > >> > > > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > > > > --=20 > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520343278-10207-157 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1861?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ]</pre> <h3>eyal edri reassigned OVIRT-1861:</h3> <pre>Assignee: Marc Dequ=C3=A8nes (Duck) (was: infra)</pre> <blockquote><h3>Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now availabl= e</h3> <pre> Key: OVIRT-1861 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1861 Project: oVirt - virtualization made easy Issue Type: Bug Components: wiki (MediaWiki) Reporter: sbonazzo Assignee: Marc Dequ=C3=A8nes (Duck)</pre> 2018-01-24 13:47 GMT+01:00 Arman Khalatyan <arm2arm(a)gmail.com>: <blockquote>Thanks for the announcement. A little comment: could you ple= ase fix the line yum install <<a href=3D"http://resources.ovirt.org/pub= /yum-repo/ovirt-release41.rpm">http://resources.ovirt.org/pub/yum-repo/ovir= t-release41.rpm</a> <<a href=3D"http://resources.ovirt.org/pub/yum-repo/= ovirt-release41.rpm%3E">http://resources.ovirt.org/pub/yum-repo/ovirt-relea= se41.rpm%3E</a>> There is an extra ‘<’ symbol there since= 4.0.x :=3D)</blockquote> Thanks for the feedback, I opened <a href=3D"https://github.com/oVirt/ov= irt-site/issues/1503">https://github.com/oVirt/ovirt-site/issues/1503</a> t= o track this. Opening a ticket on infra as well for further investigations.= <blockquote><pre>On Wed, Jan 24, 2018 at 12:00 PM, Lev Veyde <lveyde@red= hat.com> wrote:</pre> <blockquote>The oVirt Project is pleased to announce the availability of= the oVirt 4.1.9 release, as of January 24th, 2017 This update is the ninth in a series of stabilization updates to the 4.1= series. Please note that no further updates will be issued for the 4.1 series. W= e encourage users to upgrade to 4.2 series to receive new features and upda= tes. This release is available now for: <ul><li>Red Hat Enterprise Linux 7.4 or later</li> <li>CentOS Linux (or similar) 7.4 or later</li></ul> This release supports Hypervisor Hosts running: <ul><li>Red Hat Enterprise Linux 7.4 or later</li> <li>CentOS Linux (or similar) 7.4 or later</li> <li>oVirt Node 4.1</li></ul> See the release notes [1] for installation / upgrade instructions and a = list of new features and bugs fixed. Notes: <ul><li>oVirt Appliance is already available</li> <li>oVirt Live is already available [2]</li> <li>oVirt Node will be available soon [2]</li></ul> Additional Resources: <ul><li>Read more about the oVirt 4.1.9 release highlights:http://www.ov= irt.or</li></ul> g/release/4.1.9/ <ul><li>Get more oVirt Project updates on Twitter: <a href=3D"https://tw= itter.com/ovirt">https://twitter.com/ovirt</a></li> <li>Check out the latest project news on the oVirt blog:</li></ul> <a href=3D"http://www.ovirt.org/blog/">http://www.ovirt.org/blog/</a> [1] <a href=3D"http://www.ovirt.org/release/4.1.9/">http://www.ovirt.org= /release/4.1.9/</a> [2] <a href=3D"http://resources.ovirt.org/pub/ovirt-4.1= /iso/">http://resources.ovirt.org/pub/ovirt-4.1/iso/</a> — Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <<a href=3D"https://www.redhat.com/">https://www.redhat.com</a>></= p> lev(a)redhat.com | lveyde(a)redhat.com <<a href=3D"https://red.ht/sig">ht= tps://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href=3D"https://red= hat.com/trusted">https://redhat.com/trusted</a>> _____________________________________________ Users mailing lis= t Users(a)ovirt.org <a href=3D"http://lists.ovirt.org/mailman/listinfo/users"= >http://lists.ovirt.org/mailman/listinfo/users</a></blockquote> <pre>_______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users</pre></blockquote> — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA E= NG VIRTUALIZATION R&D Red Hat EMEA <<a href=3D"https://www.redhat.co= m/">https://www.redhat.com/</a>> <<a href=3D"https://red.ht/sig">http= s://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href=3D"https://redha= t.com/trusted">https://redhat.com/trusted</a>></blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#1000= 81) <img src=3D"https://u4043402.ct.sendgrid.net/wf/open?upn=3Di5TMWGV99amJbNxJ= pSp2-2BJ33BSM3tuiUfRTk64K-2BOjFTKd1eQk0jeaIcBJlLyWiNcvGIsCfxaYIbnSSZ5n5g-2F= FAwse349mKKxFQJ8h-2FY6gV-2BKhpyUfAO2xszwz4CcILXaNX6Xc-2FlDgmflUKntctunMYkPn= xKt-2FhBJX3P0x9ZCUF0GeONEQIUn-2FF1KBf1fAXvoXpIX-2B8RiS7xJQ0Xme2ELGa6QDZ5Vyo= Bxuz09XesU0NWy6cCNRrmBL4T-2FLqxAH84C-2Fc-2FDWj1psNJ2I-2Fk5PlVlqViAxQ32lzweU= MFLPJJPy6njDZHN6xVi4gM9vW6-2FvKdgPnHmd9FeysIx-2FU64ixmR06QXyRvcZ4G-2FYkv8Uh= ucMZdoj4VG5xSdhRMV8ymgDE6NTle2RPvrHBPzdVVJ2TyE5RY1Kp2Gf4-2BSSm0w9Q6dcolBHX3= YO0UsaTzrDbfWkrd" alt=3D"" width=3D"1" height=3D"1" border=3D"0" style=3D"h= eight:1px !important;width:1px !important;border-width:0 !important;margin-= top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margi= n-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;pa= dding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1520343278-10207-157--

1 0

Packages not landed on tested repo
by Sandro Bonazzola 06 Mar '18

06 Mar '18

Hi, looks like we have some packages which never passed OST, never landed in ovirt-4.2-snapshot repo and are currently causing failure building the appliance from 4.2 snapshot repo: 03:17:20,893 INFO program:Error: Package: ovirt-engine-4.2.2.3-0.0.master.20180305171049.git0e81394.el7.centos.noarch (ovirt-4.2-snapshot) 03:17:20,893 INFO program:Requires: ovirt-ansible-roles >= 1.1.2 03:17:20,894 INFO program:Error: Package: ovirt-engine-4.2.2.3-0.0.master.20180305171049.git0e81394.el7.centos.noarch (ovirt-4.2-snapshot) 03:17:20,896 INFO program:Requires: ovirt-js-dependencies 03:17:20,897 INFO program:Error: Package: ovirt-engine-4.2.2.3-0.0.master.20180305171049.git0e81394.el7.centos.noarch (ovirt-4.2-snapshot) 03:17:20,897 INFO program:Requires: ovirt-engine-wildfly-overlay >= 11.0.1 03:17:20,899 INFO program:Error: Package: ovirt-engine-api-explorer-0.0.3-0.alpha.1.20180215git9b54c9c.el7.centos.noarch (ovirt-4.2-snapshot) 03:17:20,900 INFO program:Requires: ovirt-js-dependencies >= 1.2 I'm now trying to get the missing packages pass thorough the whole testing pipeline but be aware those packages have already been released 3 months ago so they are stable and manually tested and were passing master OST. I've no clue on why they are missing in the 4.2 testing pipeline. -- 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

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Barak Korren (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520340937-32412-262 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1918: ------------------------------------- {quote} How a pacakge maintainer will know that a package didn't land in tested? It tooks me 2 months to discover we have packages not getting in tested and I noticed just by mistake. And I'm one of those maintainers that cares a lot about packages being published. {quote} [~dron]/infra-owner is supposed to tell you. This reporting is not fully automated yet because of false positives. Specifically WRT build failures you already get a comment in Gerrit. > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520340937-32412-262 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1918:</h3> {quote} How a pacakge maintainer will know that a package didn't land in tested? It tooks me 2 months to discover we have packages not getting in tested and I noticed just by mistake. And I'm one of those maintainers that cares a lot about packages being published. {quote} [~dron]/infra-owner is supposed to tell you. This reporting is not fully automated yet because of false positives. Specifically WRT build failures you already get a comment in Gerrit. <blockquote><h3>Single project tests in change-queue-tester</h3> <pre> Key: OVIRT-1918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra</pre> Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again “ci re-merge please” again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on tested repo. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1520340937-32412-262--

1 0

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by Barak Korren (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520340720-12851-179 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1918: ------------------------------------- {quote} I'm not sure that the bisection really works then, since we have still packages released 2 months ago not yet landing on tested. I don't recall to have seen any job triggered automatically after a change-queue-tester failure doing bisection tests. {quote} It works. 'change-queue-tester' itself gets re-triggered by 'change-queue' with a different set of patches after failure. Only failures that were narrowed down to a single patch are reported to infra-list. You can see the state of the queue an the bisection status in a graphical display on the status page of the 'change-queue' job. If you see something that wasn't moved to tested it can be because: # the HEAD itself that was tested is really broken # some build job failed because of an infra issue (e.g s390x/fcraw issue) # OST itself was broken at the time of the test "ci re-merge please" is for handling the last 2 reasons, essentially [~dron] or the infra owner is supposed to be monitoring the CQ reports, detecting theses cases and issuing "ci re-merge please" as needed. > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520340720-12851-179 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1918:</h3> {quote} I'm not sure that the bisection really works then, since we have still packages released 2 months ago not yet landing on tested. I don't recall to have seen any job triggered automatically after a change-queue-tester failure doing bisection tests. {quote} It works. ‘change-queue-tester’ itself gets re-triggered by ‘change-queue’ with a different set of patches after failure. Only failures that were narrowed down to a single patch are reported to infra-list. You can see the state of the queue an the bisection status in a graphical display on the status page of the ‘change-queue’ job. If you see something that wasn't moved to tested it can be because: # the HEAD itself that was tested is really broken # some build job failed because of an infra issue (e.g s390x/fcraw issue) # OST itself was broken at the time of the test “ci re-merge please” is for handling the last 2 reasons, essentially [~dron] or the infra owner is supposed to be monitoring the CQ reports, detecting theses cases and issuing “ci re-merge please” as needed. <blockquote><h3>Single project tests in change-queue-tester</h3> <pre> Key: OVIRT-1918 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra</pre> Please change change-queue-tester jobs for testing a single project at a time (ok for multiple patches at once, but from the same project). Right now if multiple patches are merged between a change-queue-tester execution and the next one are done, all of them will be tested in the next run, even if the changes are in different projects. So, supposing project A and B are completely fine, a failure in project C can still prevent changes in A and B to go ahead through the pipeline and get released. This cause major headaches at least to me, requiring me to go again over all the HEAD of the projects not being published and run yet again “ci re-merge please” again and again and again until I'm lucky enough to have nobody else merging patches or having all the ttested patches pass at once. I understand the need to reduce the amount of executions of the job since it takes an hour to execute but right now it's stealing days of execution for getting a patch landing on tested repo. — SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>></blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1520340720-12851-179--

1 0

[JIRA] (OVIRT-1918) Single project tests in change-queue-tester
by sbonazzo (oVirt JIRA) 06 Mar '18

06 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1918?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-1918: --------------------------------- bq. Maybe we need to use always the official release repo as fallback to tested? I don't think so. Tested repo should not require official release repo. Official release should be eventually generated from tested repo, not the other way around. bq. In case a specific PKG failed to build and it's maintainer didn't make sure bq. to fix it and redeploy, it makes sense to get missing pkgs from latest bq. official release, as we do in OST. How a pacakge maintainer will know that a package didn't land in tested? It tooks me 2 months to discover we have packages not getting in tested and I noticed just by mistake. And I'm one of those maintainers that cares a lot about packages being published. bq. Once the maintainer of the project will build a new image and it passes, it bq. will be in tested. That's not always true. I had several packages that required me to issue "ci re-merge please" multiple times before getting to tested repo without any code change on the project itself. > Single project tests in change-queue-tester > ------------------------------------------- > > Key: OVIRT-1918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1918 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Please change change-queue-tester jobs for testing a single project at a > time (ok for multiple patches at once, but from the same project). > Right now if multiple patches are merged between a change-queue-tester > execution and the next one are done, all of them will be tested in the next > run, even if the changes are in different projects. > So, supposing project A and B are completely fine, a failure in project C > can still prevent changes in A and B to go ahead through the pipeline and > get released. > This cause major headaches at least to me, requiring me to go again over > all the HEAD of the projects not being published and run yet again "ci > re-merge please" again and again and again until I'm lucky enough to have > nobody else merging patches or having all the ttested patches pass at once. > I understand the need to reduce the amount of executions of the job since > it takes an hour to execute but right now it's stealing days of execution > for getting a patch landing on tested repo. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by eyal edri (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520339293-14913-290 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1915: ---------------------------------- Here is the ticket to add this repoman filter option to the upstream job, can you or Dusan handle it? A similar code already exists in the old manual job in d/s, which doesn't work anymore. On Sun, Mar 4, 2018 at 2:39 PM, Daniel Belenky (oVirt JIRA) < -- Eyal edri 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) > Add option to filter packages in OST manual > ------------------------------------------- > > Key: OVIRT-1915 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins, ost > > Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520339293-14913-290 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ]</pre> <h3>eyal edri commented on OVIRT-1915:</h3> Here is the ticket to add this repoman filter option to the upstream job, can you or Dusan handle it? A similar code already exists in the old manual job in d/s, which doesn't work anymore. On Sun, Mar 4, 2018 at 2:39 PM, Daniel Belenky (oVirt JIRA) < — Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <<a href="https://www.redhat.com/">https://www.redhat.com/</a>> <<a href="https://red.ht/sig">https://red.ht/sig</a>> TRIED. TESTED. TRUSTED. <<a href="https://redhat.com/trusted">https://redhat.com/trusted</a>> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) <blockquote><h3>Add option to filter packages in OST manual</h3> <pre> Key: OVIRT-1915 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra Labels: jenkins, ost</pre> Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters.</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1520339293-14913-290--

1 0

[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by Daniel Belenky (oVirt JIRA) 06 Mar '18

06 Mar '18

This is a multi-part message in MIME format... ------------=_1520167161-24881-147 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1915: ---------------------------------- Labels: jenkins ost (was: ) > Add option to filter packages in OST manual > ------------------------------------------- > > Key: OVIRT-1915 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > Labels: jenkins, ost > > Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520167161-24881-147 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1915?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1915:</h3> <pre>Labels: jenkins ost (was: )</pre> <blockquote><h3>Add option to filter packages in OST manual</h3> <pre> Key: OVIRT-1915 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra Labels: jenkins, ost</pre> Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters.</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" 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> ------------=_1520167161-24881-147--

2 1