All issues should be resolved, and CI is passing. Please start testing.
On Thu, Jul 17, 2014 at 4:30 AM, Vladimir Kuklin <vkuk...@mirantis.com> wrote: > Andrew, we have extended system tests passing with our current pacemaker > corosync code. Either it is your environment or some bug we cannot > reproduce. Also, it may be related to puppet ordering issues thus trying to > start some services before some others. As [2] is the only issue you are > pointing at now, let's create a bug and track it in Launchpad. > > > On Thu, Jul 17, 2014 at 11:20 AM, Andrew Woodward <xar...@gmail.com> > wrote: > >> [2] still has no positive progress, simply making puppet stop the >> services isn't all that usefull, will need to move towards always >> using over-ride files >> [3] is closed as it hasn't occurred in two days >> [4] may be closed as its not occuring in CI or on my testing anymore >> >> [5] is closed, was due to [7] >> >> [7] https://bugs.launchpad.net/puppet-neutron/+bug/1343009 >> >> CI is passing CentOS now, and only failing ubuntu in OSTF. This >> appears to be due services not being properly managed in >> corosync/pacemaker >> >> On Tue, Jul 15, 2014 at 11:24 PM, Andrew Woodward <xar...@gmail.com> >> wrote: >> > [2] appears to be made worse, if not caused by neutron services >> > autostarting with debian, no patch yet, need to add mechanism to ha >> > layer to generate override files. >> > [3] appears to have stopped with this mornings master >> > [4] deleting the cluster, and restarting mostly removed this, was >> > getting issue with $::osnailyfacter::swift_partition/.. not existing >> > (/var/lib/glance), but is fixed in rev 29 >> > >> > [5] is still the critical issue blocking progress, I'm super at a loss >> > of why this is occuring. Changes to ordering have no affect. Next >> > steps probably involve pre-hacking keystone and neutron and >> > nova-client to be more verbose about it's key usage. As a hack we >> > could simply restart neutron-server but I'm not convinced the issue >> > can't come back since we don't know how it started. >> > >> > >> > >> > On Tue, Jul 15, 2014 at 6:34 AM, Sergey Vasilenko >> > <svasile...@mirantis.com> wrote: >> >> [1] fixed in https://review.openstack.org/#/c/107046/ >> >> Thanks for report a bug. >> >> >> >> _______________________________________________ >> >> OpenStack-dev mailing list >> >> OpenStack-dev@lists.openstack.org >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> > >> > >> > >> > -- >> > Andrew >> > Mirantis >> > Ceph community >> >> >> >> -- >> Andrew >> Mirantis >> Ceph community >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > > -- > Yours Faithfully, > Vladimir Kuklin, > Fuel Library Tech Lead, > Mirantis, Inc. > +7 (495) 640-49-04 > +7 (926) 702-39-68 > Skype kuklinvv > 45bk3, Vorontsovskaya Str. > Moscow, Russia, > www.mirantis.com <http://www.mirantis.ru/> > www.mirantis.ru > vkuk...@mirantis.com > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Andrew Mirantis Ceph community
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev