According to my own experience, also check if there are any zombie Zuul processes. If there are, restart won't take effect. Kill them manually first.
> On May 21, 2014, at 6:58 AM, [email protected] (James E. Blair) wrote: > > "[email protected]" <[email protected]> writes: > >> Hi- >> >> >> With Zuul version, 2.0.0.155, I'm facing a problem with layout.yaml >> >> >> The projects section is as follows in layout.yaml. >> >> projects: >> - name: openstack-dev/sandbox >> check: >> - TEST-SANDBOX >> >> but when the gerrit event arrives, zuul log shows the following warning. >> >> 2014-05-21 17:31:34,566 WARNING zuul.Scheduler: Project >> openstack-dev/sandbox not found? > > I don't see anything wrong with that. Are you sure that Zuul was > restarted after changing the config file? It only reloads the config > file after changes if it's told to (either with a signal or by > restarting). > > If it still doesn't work, would you attach the full layout.yaml as well > as the debug output from starting it beginning with "Configured Pipeline > Manager check". > > -Jim > > _______________________________________________ > OpenStack-Infra mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra _______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
