- Infra - oVirt List Archives

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1743: ------------------------------------- BTW I wonder why you need to run OST manually so often. We have change gating, so when merging a breaking change, you're only breaking the particular project you merged a change into. Other, unrelated projects can keep being tested against the last known working version... Could it be that the project contains too much independent stuff in it? > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

This is a multi-part message in MIME format... ------------=_1509983341-28314-112 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1743: ------------------------------------- The process is clunky because the whole idea if having to launch stuff manually in CI is clunky. We needed to provide a useful tool, so we brought some things together to make this possible. But I wouldn't want to spend efforts around automating a process which is IMO fundamentally broken. Ideally you would just get OST results for every patch before merging it, but this requires several things: # Asynchronous result notification to Gerrit, so you can see check-patch results while OST is still running (We have that in GitHub already, but our Gerrit framework is a bit rigid still) # Submitting pre-merged patches to CQ # Merge emulation, which is to say, emulate how the code will look if all patches being tested were merged together. We have bits and pieces of everything except #3 which is by far the most complex thing to do there... Adding OVIRT-627 as a blocker > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1509983341-28314-112 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1743:</h3> The process is clunky because the whole idea if having to launch stuff manually in CI is clunky. We needed to provide a useful tool, so we brought some things together to make this possible. But I wouldn't want to spend efforts around automating a process which is IMO fundamentally broken. Ideally you would just get OST results for every patch before merging it, but this requires several things: # Asynchronous result notification to Gerrit, so you can see check-patch results while OST is still running (We have that in GitHub already, but our Gerrit framework is a bit rigid still) # Submitting pre-merged patches to CQ # Merge emulation, which is to say, emulate how the code will look if all patches being tested were merged together. We have bits and pieces of everything except #3 which is by far the most complex thing to do there… Adding OVIRT-627 as a blocker <blockquote><h3>ci please build and send to OST</h3> <pre> Key: OVIRT-1743 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: danken Assignee: infra</pre> Can you please automate the frequent process, which is slow and error prone? I am writing a patch, and would like to test it in ost. now I need to <ul><li>“ci please build”</li> <li>copy el7 url</li> <li>wait for el7 build to finish</li> <li>copy artifacts url to ovirt--system-test-manual, start it</li> <li>copy the ost run URL to the gerrit patch, so I have it for reference of failure/success.</li></ul></blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1509983341-28314-112--

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Epic Link: OVIRT-400 > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Epic Link: OVIRT-400 > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by danken (oVirt JIRA) 06 Nov '17

06 Nov '17

danken created OVIRT-1743: ----------------------------- Summary: ci please build and send to OST Key: OVIRT-1743 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: danken Assignee: infra Can you please automate the frequent process, which is slow and error prone? I am writing a patch, and would like to test it in ost. now I need to * "ci please build" * copy el7 url * wait for el7 build to finish * copy artifacts url to ovirt--system-test-manual, start it * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1742) wrong augeas-libs package downloaded from bob repo on 3.6 els
by Dafna Ron (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1742?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-1742: -------------------------------- Assignee: Dafna Ron (was: infra) > wrong augeas-libs package downloaded from bob repo on 3.6 els > -------------------------------------------------------------- > > Key: OVIRT-1742 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1742 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Dafna Ron > > we are failing 3.6 tests on package augeas-libs: YumBaseError: [u'1:libguestfs-1.28.1-1.55.el7_2.2.x86_64 requires augeas-libs >= 1.1.0-16'] > looking at lago we can see that the package arrives from bob repo: > https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ds-ovirt-sys… > > also, running the below shows the package is downloaded from bob: > [dron@dron rhv-suite-3.6-els]$ repoquery --repofrompath=testrepo,http://bob.eng.lab.tlv.redhat.com/builds/latest_3.6/el7/ --repoid=testrepo --query --all | grep augeas-* > Repository google-chrome is listed more than once in the configuration > Repository google-talkplugin is listed more than once in the configuration > augeas-0:1.1.0-12.el7_0.1.x86_64 > augeas-debuginfo-0:1.1.0-12.el7_0.1.x86_64 > augeas-devel-0:1.1.0-12.el7_0.1.x86_64 > augeas-libs-0:1.1.0-12.el7_0.1.x86_64 > [dron@dron rhv-suite-3.6-els]$ > I am submitting a patch to exclude the package from bob repo to force download of the correct package from the correct repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1742) wrong augeas-libs package downloaded from bob repo on 3.6 els
by Dafna Ron (oVirt JIRA) 06 Nov '17

06 Nov '17

This is a multi-part message in MIME format... ------------=_1509979003-13625-130 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Dafna Ron created OVIRT-1742: -------------------------------- Summary: wrong augeas-libs package downloaded from bob repo on 3.6 els Key: OVIRT-1742 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1742 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra we are failing 3.6 tests on package augeas-libs: YumBaseError: [u'1:libguestfs-1.28.1-1.55.el7_2.2.x86_64 requires augeas-libs >= 1.1.0-16'] looking at lago we can see that the package arrives from bob repo: https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ds-ovirt-sys… also, running the below shows the package is downloaded from bob: [dron@dron rhv-suite-3.6-els]$ repoquery --repofrompath=testrepo,http://bob.eng.lab.tlv.redhat.com/builds/latest_3.6/el7/ --repoid=testrepo --query --all | grep augeas-* Repository google-chrome is listed more than once in the configuration Repository google-talkplugin is listed more than once in the configuration augeas-0:1.1.0-12.el7_0.1.x86_64 augeas-debuginfo-0:1.1.0-12.el7_0.1.x86_64 augeas-devel-0:1.1.0-12.el7_0.1.x86_64 augeas-libs-0:1.1.0-12.el7_0.1.x86_64 [dron@dron rhv-suite-3.6-els]$ I am submitting a patch to exclude the package from bob repo to force download of the correct package from the correct repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1509979003-13625-130 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Dafna Ron created OVIRT-1742:</h3> <pre> Summary: wrong augeas-libs package downloaded from bob repo on 3.6 els Key: OVIRT-1742 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1742 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra</pre> we are failing 3.6 tests on package augeas-libs: YumBaseError: [u'1:libguestfs-1.28.1-1.55.el7_2.2.x86_64 requires augeas-libs >= 1.1.0-16'] looking at lago we can see that the package arrives from bob repo: <a href="https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ds-ovirt-sys…">https://rhv-devops-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/ds-ovirt-sys…</a> also, running the below shows the package is downloaded from bob: [dron@dron rhv-suite-3.6-els]$ repoquery --repofrompath=testrepo,<a href="http://bob.eng.lab.tlv.redhat.com/builds/latest_3.6/el7/">http://bob.eng.lab.tlv.redhat.com/builds/latest_3.6/el7/</a> --repoid=testrepo --query --all | grep augeas-* Repository google-chrome is listed more than once in the configuration Repository google-talkplugin is listed more than once in the configuration augeas-0:1.1.0-12.el7_0.1.x86_64 augeas-debuginfo-0:1.1.0-12.el7_0.1.x86_64 augeas-devel-0:1.1.0-12.el7_0.1.x86_64 augeas-libs-0:1.1.0-12.el7_0.1.x86_64 [dron@dron rhv-suite-3.6-els]$ I am submitting a patch to exclude the package from bob repo to force download of the correct package from the correct repo. — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" 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> ------------=_1509979003-13625-130--

1 0

[CQ]: 83521,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 06 Nov '17

06 Nov '17

Change 83521,4 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83521/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3633/

1 0

[JIRA] (OVIRT-1741) Get oVirt listed on https://release-monitoring.org/
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1741?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1741: ------------------------------------- [~sbonazzo(a)redhat.com] [~eedri] WDYT? > Get oVirt listed on https://release-monitoring.org/ > --------------------------------------------------- > > Key: OVIRT-1741 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1741 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: Low > > https://release-monitoring.org/ seems to be a system that sends notification events when opens source projects release new versions. > Various systems seem to be listening and reacting on those events. > We should probably have oVirt listed there and sending events. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1741) Get oVirt listed on https://release-monitoring.org/
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

Barak Korren created OVIRT-1741: ----------------------------------- Summary: Get oVirt listed on https://release-monitoring.org/ Key: OVIRT-1741 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1741 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: Low https://release-monitoring.org/ seems to be a system that sends notification events when opens source projects release new versions. Various systems seem to be listening and reacting on those events. We should probably have oVirt listed there and sending events. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0