With the changes in master a new entry "Off" got introduced in the disk offering table which made things to break.
The database entries for provisioning_type in the disk_offering_view table shows "Off" mysql> select provisioning_type from disk_offering_view; +-------------------+ | provisioning_type | +-------------------+ | Off | | Off | | thin | | thin | | thin | | thin | | thin | | thin | | thin | | thin | | thin | | thin | | thin | +-------------------+ 13 rows in set (0.00 sec) Change the provisioning_type to *thin (provisioning_type can only have values as thin, fat, sparse) *and things works fine. Was this new value introduced for a purpose ?? On Thu, Jun 19, 2014 at 12:06 PM, Wilder Rodrigues < wrodrig...@schubergphilis.com> wrote: > I have a clean environment, just created 2 VPCs. Before that, DB and > everything was cleaned up and built based on the latest code. > > I will have a look in the code, then. > > Cheers, > Wilder > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] > Sent: woensdag 18 juni 2014 5:22 > To: dev@cloudstack.apache.org > Cc: int-toolkit > Subject: Re: [ACS-Master] Cannot load compute offerings: NPE > > I noticed a similar issue yesterday when trying to retrieve a list of > storage volumes. > > I was planning on building everything up from scratch again (including the > DB) to repro the issue to see if it's gone now, but it looks like it might > be a more wide-spread problem than what I was just seeing. > > On Wed, Jun 18, 2014 at 8:07 AM, Wilder Rodrigues < > wrodrig...@schubergphilis.com<mailto:wrodrig...@schubergphilis.com>> > wrote: > Hi guys, > > I'm facing a problem when loading service offerings on ACS Master branch. > Is anyone aware of this? Is there any issue open? > > 2014-06-18 15:54:52,495 DEBUG [c.c.a.ApiServlet] > (19418424@qtp-9894122-6:ctx-3a0f1094) > ===START=== 0:0:0:0:0:0:0:1 -- GET command=listServ > > iceOfferings&response=json&sessionkey=pzJwAgN95saj%2FfExWkezaytg7U4%3D&listAll=true&page=1&pagesize=20&issystem=false&_=1403099692481 > 2014-06-18 15:54:52,608 WARN [c.c.a.d.ParamGenericValidationWorker] > (19418424@qtp-9894122-6:ctx-3a0f1094 ctx-226b1105) Received unknown par > ameters for command listServiceOfferings. Unknown parameters : listall > 2014-06-18 15:54:52,710 ERROR [c.c.a.ApiServer] > (19418424@qtp-9894122-6:ctx-3a0f1094 > ctx-226b1105) unhandled exception executing api command > : [Ljava.lang.String;@fd06cb > java.lang.NullPointerException > at > com.cloud.api.query.dao.ServiceOfferingJoinDaoImpl.newServiceOfferingResponse(ServiceOfferingJoinDaoImpl.java:62) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) > at > com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) > at > org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) > at > org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) > at > org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) > at com.sun.proxy.$Proxy270.newServiceOfferingResponse(Unknown > Source) > at > com.cloud.api.ApiDBUtils.newServiceOfferingResponse(ApiDBUtils.java:1794) > at > com.cloud.api.query.ViewResponseHelper.createServiceOfferingResponse(ViewResponseHelper.java:354) > at > com.cloud.api.query.QueryManagerImpl.searchForServiceOfferings(QueryManagerImpl.java:2415) > at > org.apache.cloudstack.api.command.user.offering.ListServiceOfferingsCmd.execute(ListServiceOfferingsCmd.java:106) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) > at com.cloud.api.ApiServer.queueCommand(ApiServer.java:689) > at com.cloud.api.ApiServer.handleRequest(ApiServer.java:512) > at > com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:317) > at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) > at > org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115) > at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77) > 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(ContextHandlerCollection.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(HttpConnection.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:410) > at > org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) > 2014-06-18 15:54:52,772 DEBUG [c.c.a.ApiServlet] > (19418424@qtp-9894122-6:ctx-3a0f1094 > ctx-226b1105) ===END=== 0:0:0:0:0:0:0:1 -- GET > > command=listServiceOfferings&response=json&sessionkey=pzJwAgN95saj%2FfExWkezaytg7U4%3D&listAll=true&page=1&pagesize=20&issystem=false&_=1403099692481 > > Cheers, > Wilder > > > > -- > Mike Tutkowski > Senior CloudStack Developer, SolidFire Inc. > e: mike.tutkow...@solidfire.com<mailto:mike.tutkow...@solidfire.com> > o: 303.746.7302 > Advancing the way the world uses the cloud< > http://solidfire.com/solution/overview/?video=play>™ > -- *Thanks and Regards,* *Sonal Ojha ▪ Sr.Engineer - Product Development **▪ **Sungard Availability Services, India* 2nd Floor, Wing 4, Cluster D, MIDC Kharadi Knowledge Park, Pune - 411 014 ▪ Office: 267-234-9014 ▪ Mobile: +91 9922412645 ▪ sonal.o...@sungardas.com ▪ www.sungardas. <http://www.sungardas.com/>*in* *[image: Logo]* <http://www.sungardas.com/> *[image: cid:image019.png@01CF48EC.6617C7F0]* <http://blog.sungardas.com/> *[image: cid:image020.png@01CF48EC.6617C7F0]* <http://www.youtube.com/user/SunGardAS> *[image: cid:image021.png@01CF48EC.6617C7F0]* <https://plus.google.com/u/0/102459878242108588663/posts> *[image: cid:image022.png@01CF48EC.6617C7F0]* <https://www.facebook.com/SunGardAS> *[image: cid:image023.png@01CF48EC.6617C7F0]* <http://www.linkedin.com/company/sungard-availability-services> *[image: cid:image024.png@01CF48EC.6617C7F0]* <https://twitter.com/SunGardAS> *CONFIDENTIALITY:* This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system.