Re: [openstack-dev] [Neutron] Neutron Ryu status
just an update: the Neutron Ryu CI is getting stable now. please let me know if you noticed any problems. thank you. YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Neutron Ryu status
Third party CI maintainers can avoid problems related to version conflicts (which do not happen in the upstream CI) by doing fresh installation of python modules. OpenStack upstream CI installs dependent python modules every time a test is run. I also suggest to use fresh installation of python modules for every test running. Thanks, Akihiro On Sat, Jul 19, 2014 at 5:42 AM, Kevin Benton blak...@gmail.com wrote: While the long term fix is a bump up in the requirements, a workaround suggested for the 3rd party CI systems is to force an upgrade of alembic before running devstack. This will allow the setup to work so that patch isn't a high priority. -- Kevin Benton On Fri, Jul 18, 2014 at 9:22 AM, Kyle Mestery mest...@mestery.com wrote: On Fri, Jul 18, 2014 at 9:30 AM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: On Tue, Jul 15, 2014 at 9:12 AM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: if you are wondering why ofagent CI (Neutron Ryu) reported a failure (non-voting) for your review recently, you can probably safely ignore it. sorry for inconvenience. the CI has been fixed recently. unfortunately ofagent on master is broken (a consequence of the broken CI) and the CI started detecting the breakage correctly. the breakage will be fixed if the following changes are merged. https://review.openstack.org/#/c/103764/ https://review.openstack.org/#/c/106701/ an update: the above mentioned changes have been merged. (thanks) but shortly new problems are introduced and thus the CI started reporting failures again. the following changes would fix the relevant problems. https://review.openstack.org/#/c/107229/ (workarounded in our CI) Regarding this change, I have pinged infra people in channel again, I hope we can get some cores there to approve this one, as it's blocking a fair number of Neutron 3rd party CI systems. Thanks, Kyle https://review.openstack.org/#/c/107884/ YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Neutron Ryu status
On Tue, Jul 15, 2014 at 9:12 AM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: if you are wondering why ofagent CI (Neutron Ryu) reported a failure (non-voting) for your review recently, you can probably safely ignore it. sorry for inconvenience. the CI has been fixed recently. unfortunately ofagent on master is broken (a consequence of the broken CI) and the CI started detecting the breakage correctly. the breakage will be fixed if the following changes are merged. https://review.openstack.org/#/c/103764/ https://review.openstack.org/#/c/106701/ an update: the above mentioned changes have been merged. (thanks) but shortly new problems are introduced and thus the CI started reporting failures again. the following changes would fix the relevant problems. https://review.openstack.org/#/c/107229/ (workarounded in our CI) https://review.openstack.org/#/c/107884/ YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Neutron Ryu status
On Fri, Jul 18, 2014 at 9:30 AM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: On Tue, Jul 15, 2014 at 9:12 AM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: if you are wondering why ofagent CI (Neutron Ryu) reported a failure (non-voting) for your review recently, you can probably safely ignore it. sorry for inconvenience. the CI has been fixed recently. unfortunately ofagent on master is broken (a consequence of the broken CI) and the CI started detecting the breakage correctly. the breakage will be fixed if the following changes are merged. https://review.openstack.org/#/c/103764/ https://review.openstack.org/#/c/106701/ an update: the above mentioned changes have been merged. (thanks) but shortly new problems are introduced and thus the CI started reporting failures again. the following changes would fix the relevant problems. https://review.openstack.org/#/c/107229/ (workarounded in our CI) Regarding this change, I have pinged infra people in channel again, I hope we can get some cores there to approve this one, as it's blocking a fair number of Neutron 3rd party CI systems. Thanks, Kyle https://review.openstack.org/#/c/107884/ YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Neutron Ryu status
While the long term fix is a bump up in the requirements, a workaround suggested for the 3rd party CI systems is to force an upgrade of alembic before running devstack. This will allow the setup to work so that patch isn't a high priority. -- Kevin Benton On Fri, Jul 18, 2014 at 9:22 AM, Kyle Mestery mest...@mestery.com wrote: On Fri, Jul 18, 2014 at 9:30 AM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: On Tue, Jul 15, 2014 at 9:12 AM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: if you are wondering why ofagent CI (Neutron Ryu) reported a failure (non-voting) for your review recently, you can probably safely ignore it. sorry for inconvenience. the CI has been fixed recently. unfortunately ofagent on master is broken (a consequence of the broken CI) and the CI started detecting the breakage correctly. the breakage will be fixed if the following changes are merged. https://review.openstack.org/#/c/103764/ https://review.openstack.org/#/c/106701/ an update: the above mentioned changes have been merged. (thanks) but shortly new problems are introduced and thus the CI started reporting failures again. the following changes would fix the relevant problems. https://review.openstack.org/#/c/107229/ (workarounded in our CI) Regarding this change, I have pinged infra people in channel again, I hope we can get some cores there to approve this one, as it's blocking a fair number of Neutron 3rd party CI systems. Thanks, Kyle https://review.openstack.org/#/c/107884/ YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Kevin Benton ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron] Neutron Ryu status
if you are wondering why ofagent CI (Neutron Ryu) reported a failure (non-voting) for your review recently, you can probably safely ignore it. sorry for inconvenience. the CI has been fixed recently. unfortunately ofagent on master is broken (a consequence of the broken CI) and the CI started detecting the breakage correctly. the breakage will be fixed if the following changes are merged. https://review.openstack.org/#/c/103764/ https://review.openstack.org/#/c/106701/ YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Neutron Ryu status
On Tue, Jul 15, 2014 at 9:12 AM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: if you are wondering why ofagent CI (Neutron Ryu) reported a failure (non-voting) for your review recently, you can probably safely ignore it. sorry for inconvenience. the CI has been fixed recently. unfortunately ofagent on master is broken (a consequence of the broken CI) and the CI started detecting the breakage correctly. the breakage will be fixed if the following changes are merged. https://review.openstack.org/#/c/103764/ https://review.openstack.org/#/c/106701/ YAMAMOTO Takashi Thanks for the update on this YAMAMOTO. I'll work to try and get those two bug fixes merged by having other cores review them ASAP so we can get ofagent working again. Kyle ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Neutron Ryu status
On Tue, Jul 15, 2014 at 9:12 AM, YAMAMOTO Takashi yamam...@valinux.co.jp wrote: if you are wondering why ofagent CI (Neutron Ryu) reported a failure (non-voting) for your review recently, you can probably safely ignore it. sorry for inconvenience. the CI has been fixed recently. unfortunately ofagent on master is broken (a consequence of the broken CI) and the CI started detecting the breakage correctly. the breakage will be fixed if the following changes are merged. https://review.openstack.org/#/c/103764/ https://review.openstack.org/#/c/106701/ YAMAMOTO Takashi Thanks for the update on this YAMAMOTO. I'll work to try and get those two bug fixes merged by having other cores review them ASAP so we can get ofagent working again. thank you! YAMAMOTO Takashi Kyle ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
