[ https://issues.apache.org/jira/browse/JCLOUDS-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410921#comment-17410921 ]
Andrew Gaul commented on JCLOUDS-1584: -------------------------------------- Sorry the jclouds team no longer has the volunteers to support multiple branches. Fortunately 2.4.0 should release later this week. > Deployment API fails when ARM Template deploys for creating Azure VM > -------------------------------------------------------------------- > > Key: JCLOUDS-1584 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1584 > Project: jclouds > Issue Type: Bug > Components: jclouds-compute > Affects Versions: 2.3.0 > Reporter: Rajani Palavala > Assignee: Andrew Gaul > Priority: Major > Labels: azurecompute-arm > Fix For: 2.4.0 > > Attachments: Deployment.java, Value.java > > Time Spent: 40m > Remaining Estimate: 0h > > Hello, > we are using jclouds for azure compute operations. while using deployment API > for creating virtual machine using ARM Template get success but fails to get > the deployment details. > > while investigating we found two issues > *1.* java.lang.NullPointerException: Null > valuejava.lang.NullPointerException: Null value at > org.jclouds.azurecompute.arm.domain.AutoValue_Value.<init>(AutoValue_Value.java:20) > at org.jclouds.azurecompute.arm.domain.Value.create(Value.java:39) > The ARM template have secure information (password) which Azure is not > returning the value when we do GET on the deployment, which is causing null > pointer @Value.java > *Solution:* We added @Nullable to value() which solved our issue. > > *2.* com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: > Expected a string but was BEGIN_ARRAY at line 1 column 472 path > $.properties.parameters..value > at > org.jclouds.json.internal.DeserializationConstructorAndReflectiveTypeAdapterFactory$DeserializeIntoParameterizedConstructor.read(DeserializationConstructorAndReflectiveTypeAdapterFactory.java:193) > > The ARM Template have parameters which is type Array is the reason. > > *Solution:* We have modified parameter map value to JSONBALL to accept all > types of values. > > we would like to have patch including the solutions, please review and accept > the request. > Thanks. > -- This message was sent by Atlassian Jira (v8.3.4#803005)