Postponing 3.6.0 second alpha to next week
Hi, due to instability of the current code, we need to postpone second alpha to next week. Maintainers: - please ensure that all packages you maintain builds in jenkins - please ensure that all the dependencies required by your packages are available either in ovirt repository or in an external repository included in ovirt-release repo files. - please ensure that engine is at least able to add a couple of hosts, create a vm on one host and migrate it to the other one. Infra: - please help keeping jenkins monitored and stabilizing it. Community: - please help testing nightly build while stabilizing it for the second alpha release. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Logwatch for linode01.ovirt.org (Linux)
### Logwatch 7.3.6 (05/19/07) Processing Initiated: Wed Jun 17 03:12:11 2015 Date Range Processed: yesterday ( 2015-Jun-16 ) Period is day. Detail Level of Output: 0 Type of Output: unformatted Logfiles for Host: linode01.ovirt.org ## - httpd Begin Requests with error response codes 400 Bad Request /: 2 Time(s) /tmUnblock.cgi: 1 Time(s) 404 Not Found //admin/categories.php/login.php?cPath=ac ... product_preview: 97 Time(s) //components/com_jnews/includes/openflashc ... pload_image.php: 1 Time(s) //lists.ovirt.org/listinfo/board: 1 Time(s) //wp-admin/admin-ajax.php?action=revslider ... ./wp-config.php: 1 Time(s) //xmlrpc.php: 2 Time(s) /_h5ai/client/icons/96/text.png: 1 Time(s) /_h5ai/client/images/app-16x16.ico: 12 Time(s) /addons/fckeditor/editor/filemanager/conne ... uploadtest.html: 1 Time(s) /admin.php: 9 Time(s) /admin/: 8 Time(s) /admin/board: 1 Time(s) /admin/fckeditor/editor/filemanager/connec ... uploadtest.html: 1 Time(s) /admin/index.php: 1 Time(s) /admin/login.php: 8 Time(s) /administrator/index.php: 9 Time(s) /apple-touch-icon-precomposed.png: 1 Time(s) /apple-touch-icon.png: 1 Time(s) /assets/fckeditor/editor/filemanager/conne ... uploadtest.html: 1 Time(s) /automne/fckeditor/editor/filemanager/conn ... uploadtest.html: 1 Time(s) /bitrix/admin/index.php?lang=en: 9 Time(s) /blog/wp-admin/: 18 Time(s) /board: 2 Time(s) /browserconfig.xml: 1 Time(s) /category/news/feed: 2 Time(s) /category/news/feed/: 17 Time(s) /ckeditor/samples/plugins/htmlwriter/outputhtml.html: 1 Time(s) /core_main/editor/editor/filemanager/conne ... uploadtest.html: 1 Time(s) /dbreports/dwh: 1 Time(s) /favicon.ico: 719 Time(s) /fckeditor/editor/filemanager/connectors/uploadtest.html: 1 Time(s) /files/fckeditor/editor/filemanager/connec ... uploadtest.html: 1 Time(s) /files/filebox/File/fileUpload.Html: 1 Time(s) /hudson/script: 1 Time(s) /images/stories/food.php: 1 Time(s) /images/stories/petx.gif: 1 Time(s) /inc/fckeditor/editor/filemanager/connectors/uploadtest.html: 1 Time(s) /includes/fckeditor/editor/filemanager/con ... uploadtest.html: 1 Time(s) /index.php?gf_page=upload: 1 Time(s) /index.php?option=com_jcetask=pluginplug ... 86d0dd595c8e20b: 2 Time(s) /js/fckeditor/editor/filemanager/connectors/uploadtest.html: 1 Time(s) /lib/fckeditor/editor/filemanager/connectors/uploadtest.html: 1 Time(s) /listinfo/board: 2 Time(s) /listinfo/engine-devel: 1 Time(s) /listinfo/kimchi-devel: 1 Time(s) /listinfo/node-patches: 1 Time(s) /m/pipermail/users/2012-August/009196.html: 1 Time(s) /m/pipermail/users/2012-November/010647.html: 1 Time(s) /m/pipermail/users/2014-September/027700.html: 1 Time(s) /m/pipermail/users/2015-January/030740.html: 1 Time(s) /meetings/ovirt/2015/oVirt: 1 Time(s) /mobile/pipermail/node-devel/2013-August/000503.html: 1 Time(s) /mobile/pipermail/users/2012-May/007779.html: 1 Time(s) /mobile/pipermail/users/2014-September/027700.html: 1 Time(s) /news-and-events/workshop-1-to-3-november-2011/: 1 Time(s) /news-and-events/workshop/: 1 Time(s) /old/wp-admin/: 19 Time(s) /phpThumb.php: 2 Time(s) /pipermail: 1 Time(s) /pipermail/commits: 1 Time(s) /pipermail/engine-commits/2012-October/002 ... html/trackback/: 1 Time(s) /pipermail/engine-commits/2012-august/author.html: 1 Time(s) /pipermail/engine-commits/2012-august/subject.html: 1 Time(s) /pipermail/engine-commits/2012-august/thread.html: 1 Time(s) /pipermail/engine-commits/2012-december.txt.gz: 1 Time(s) /pipermail/engine-commits/2012-december/author.html: 1 Time(s) /pipermail/engine-commits/2012-december/date.html: 1 Time(s) /pipermail/engine-commits/2012-december/subject.html: 1 Time(s) /pipermail/engine-commits/2012-december/thread.html: 1 Time(s) /pipermail/engine-commits/2012-november.txt.gz: 1 Time(s) /pipermail/engine-commits/2012-november/author.html: 1 Time(s) /pipermail/engine-commits/2012-november/date.html: 1 Time(s) /pipermail/engine-commits/2012-november/subject.html: 1 Time(s) /pipermail/engine-commits/2012-november/thread.html: 1 Time(s) /pipermail/engine-commits/2012-october.txt.gz: 1 Time(s) /pipermail/engine-commits/2012-october/author.html: 1 Time(s) /pipermail/engine-commits/2012-october/date.html: 1 Time(s)
Re: Jenkins CI granting excessive +1s
On Tue, Jun 16, 2015 at 08:48:17PM +0200, dcaro wrote: On 06/16, Eyal Edri wrote: Sounds like a bug. Jenkins should only use the CI flag and not change CR and V flags. Might have been a misunderstanding. David, can you fix it so Jenkins will only update CI flag? Can someone pass me an example of the patch that had the reviews? It's possible that previously the jobs were manually modified to only set the ci flag and we updated them on yaml and the manual changes got reverted. Having a sample patch would allow me to trim down the list of possible jobs that give that review. That can be prevented globally easily, but until all projects have the ci flag we can't enforce it globally. See for example https://gerrit.ovirt.org/#/c/42362/ Patch Set 5: Code-Review+1 Continuous-Integration+1 Verified+1 in a later run seems to have fixed this Patch Set 6: Continuous-Integration+1 ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Jenkins CI granting excessive +1s
I just rolled out the CI flag to all the projects this morning, restricting jenkins to set only that flag, did that happen again after it? On 06/17, Dan Kenigsberg wrote: On Tue, Jun 16, 2015 at 08:48:17PM +0200, dcaro wrote: On 06/16, Eyal Edri wrote: Sounds like a bug. Jenkins should only use the CI flag and not change CR and V flags. Might have been a misunderstanding. David, can you fix it so Jenkins will only update CI flag? Can someone pass me an example of the patch that had the reviews? It's possible that previously the jobs were manually modified to only set the ci flag and we updated them on yaml and the manual changes got reverted. Having a sample patch would allow me to trim down the list of possible jobs that give that review. That can be prevented globally easily, but until all projects have the ci flag we can't enforce it globally. See for example https://gerrit.ovirt.org/#/c/42362/ Patch Set 5: Code-Review+1 Continuous-Integration+1 Verified+1 in a later run seems to have fixed this Patch Set 6: Continuous-Integration+1 -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 pgpHxDvi58vIn.pgp Description: PGP signature ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Jenkins CI granting excessive +1s
On Wed, Jun 17, 2015 at 03:05:52PM +0200, dcaro wrote: I just rolled out the CI flag to all the projects this morning, restricting jenkins to set only that flag, did that happen again after it? No, all seems clear now. Thanks. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
