er.java:47)
> > > at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)
> > > at
> > >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > > at java.lang.reflect.Method.invoke(Method.java:597)
> &
t.processRequest(ApiServlet.java:302)
> > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> > at org.mortbay.jetty.servlet.ServletHol
onnection.java:928)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectC
ust updated my repo today, rebuilt master, and ran the MS...so far, so
> good.
>
> When I went to set up my DevCloud2 environment, however, I noticed a
> problem creating primary storage (when executing the Python script to set
> up my environment).
>
> Is this a known problem an
Hi,
I just updated my repo today, rebuilt master, and ran the MS...so far, so
good.
When I went to set up my DevCloud2 environment, however, I noticed a
problem creating primary storage (when executing the Python script to set
up my environment).
Is this a known problem and - if so - is there a
