On Wed, Jul 5, 2017 at 9:05 PM Sam Ruby <[email protected]> wrote:
> On Wed, Jul 5, 2017 at 8:43 PM, John D. Ament <[email protected]> > wrote: > > Heron is currently marked as danger on the podling list. I tracked it > down > > to them not being in ldap. I attempted to start setting up the podling, > > but it failed with a 500 error. > > > > Any ideas why? > > I looked at the stack traceback, and it was a NPE due to the project > not being found. > > I've just pushed a change that will disable modification of new > projects until they are set up in LDAP. > > Only the infrastructure and secretarial teams can create new projects. > I've just done this for this project. > So is there a step required after a podling is created now? > > > John > > - Sam Ruby >
