Are you able to use CloudMonkey? Perhaps it is a UI issue? On 6/14/13 9:50 AM, "Will Stevens" <wstev...@cloudops.com> wrote:
>11 days ago I pulled the master code into my branch. Master was at: >48913679e80e50228b1bd4b3d17fe5245461626a > >When I pulled, I had Egress firewall rules working perfectly. After the >pull I now get the following error when trying to create Egress firewall >rules: >ERROR [cloud.api.ApiServer] (1784147987@qtp-213982037-11:) unhandled >exception executing api command: createEgressFirewallRule >java.lang.NullPointerException >at >com.cloud.network.firewall.FirewallManagerImpl.validateFirewallRule(Firewa >llManagerImpl.java:485) >at >com.cloud.network.firewall.FirewallManagerImpl.createFirewallRule(Firewall >ManagerImpl.java:191) >at >com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorD >ispatcher.intercept(ComponentInstantiationPostProcessor.java:125) >at >com.cloud.network.firewall.FirewallManagerImpl.createEgressFirewallRule(Fi >rewallManagerImpl.java:157) >at >org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCm >d.create(CreateEgressFirewallRuleCmd.java:252) >at com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:101) >at com.cloud.api.ApiServer.queueCommand(ApiServer.java:471) >at com.cloud.api.ApiServer.handleRequest(ApiServer.java:367) >at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304) >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.ServletHolder.handle(ServletHolder.java:511) >at >org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) >at >org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216 >) >at >org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) >at >org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) >at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) >at >org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCo >llection.java:230) >at >org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java: >114) >at >org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) >at org.mortbay.jetty.Server.handle(Server.java:326) >at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) >at >org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnect >ion.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(SelectChannelEndPoint.java:41 >0) >at >org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:5 >82) > >--- > >So I merged in master this morning to see if that issue was fixed. Now I >can not create a Network Service offering and select anything but Virtual >Router from any of the dropdowns for capabilities such as 'Firewall', >'Source NAT', etc... > >There are no JS errors, the dropdown just sits and thinks about it for a >second and does not change away from Virtual Router. > >So now I can't use my service provider at all, so my development is >completely stalled. > >Ideas??? > >ws
