Could you check if following commit fixed your problem? It's checked in 3 hours ago.
commit 4b2eb18cfc82093640b2cb6c47c0378e69b9f8a2 Author: Jessica Wang <jessicaw...@apache.org> Date: Fri Jun 14 14:17:50 2013 -0700 CLOUDSTACK-2981: UI - create network offering - fix a bug that provider dropdown always bounced back to the first enabled option. It should only bounce back to the first enabled option when the selected option is disabled. --Sheng On Fri, Jun 14, 2013 at 4:39 PM, Chiradeep Vittal < chiradeep.vit...@citrix.com> wrote: > Did you build the nonoss build? You have to add the SRX provider using > addNetworkServiceProvider api, enable it and then the drop down for > network offering should work. > > > On 6/14/13 12:09 PM, "Will Stevens" <wstev...@cloudops.com> wrote: > > >BTW, I am using cloudmonkey 4.1.0... Thx > > > > > >On Fri, Jun 14, 2013 at 3:04 PM, Will Stevens <wstev...@cloudops.com> > >wrote: > > > >> Chiradeep, can you send me the format of the cloudmonkey call for the > >>api > >> request 'createNetworkOffering' with 'supportedservices' of > >> 'dhcp:virtualrouter', 'dns:virtualrouter', 'firewall:junipersrx'. I can > >> not figure out the format of this call. > >> > >> I have confirmed that I can reproduce the issue of not being able to > >> select capability dropdowns in multiple browsers on master. > >> > >> Thanks, > >> > >> Will > >> > >> > >> On Fri, Jun 14, 2013 at 1:56 PM, Will Stevens > >><wstev...@cloudops.com>wrote: > >> > >>> I will try that. I am doing some testing right now. I am compiling > >>>and > >>> running just master now to validate everything. > >>> > >>> I will be in touch when I have more details... > >>> > >>> ws > >>> > >>> > >>> On Fri, Jun 14, 2013 at 1:20 PM, Chiradeep Vittal < > >>> chiradeep.vit...@citrix.com> wrote: > >>> > >>>> 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(Fi > >>>>>rewa > >>>> >llManagerImpl.java:485) > >>>> >at > >>>> > >>>> > >>>>>com.cloud.network.firewall.FirewallManagerImpl.createFirewallRule(Fire > >>>>>wall > >>>> >ManagerImpl.java:191) > >>>> >at > >>>> > >>>> > >>>>>com.cloud.utils.component.ComponentInstantiationPostProcessor$Intercep > >>>>>torD > >>>> >ispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > >>>> >at > >>>> > >>>> > >>>>>com.cloud.network.firewall.FirewallManagerImpl.createEgressFirewallRul > >>>>>e(Fi > >>>> >rewallManagerImpl.java:157) > >>>> >at > >>>> > >>>> > >>>>>org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRu > >>>>>leCm > >>>> >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:40 > >>>>>1) > >>>> >at > >>>> > >>>> > >>>>>org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java > >>>>>:216 > >>>> >) > >>>> >at > >>>> > >>>>>org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:18 > >>>>>2) > >>>> >at > >>>> > >>>>>org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:76 > >>>>>6) > >>>> >at > >>>>org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) > >>>> >at > >>>> > >>>> > >>>>>org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandl > >>>>>erCo > >>>> >llection.java:230) > >>>> >at > >>>> > >>>> > >>>>>org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.j > >>>>>ava: > >>>> >114) > >>>> >at > >>>> > >>>>>org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:15 > >>>>>2) > >>>> >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(HttpCon > >>>>>nect > >>>> >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.jav > >>>>>a:41 > >>>> >0) > >>>> >at > >>>> > >>>> > >>>>>org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.ja > >>>>>va: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 > >>>> > >>>> > >>> > >> > >