In the last few days, our Jenkins master has lost the ability to communicate with our Openstack installation. When jenkins tries to create a slave, or reconnect to existing slaves after a Jenkins restart, there is an error:
...
May 09, 2016 9:17:33 AM org.jclouds.logging.jdk.JDKLogger logError
SEVERE: Error parsing input
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected a string but was BEGIN_ARRAY at line 1 column 930
at org.jclouds.json.internal.DeserializationConstructorAndReflectiveTypeAdapterFactory$DeserializeIntoParameterizedConstructor.read(DeserializationConstructorAndReflectiveTypeAdapterFactory.java:181)
...
Complete log file is attached as well as a sample response from Openstack.
Our Openstack engineer has examine the cloud configuration, and has not been able to identify any issues there.
Restarting the service & the host did not clear up the issue. We did not change any Jenkins config, and this was working normally previously.
Obviously, something in the openstack response has changed (some single value was expected, but an array value was returned). Similar exceptions have been noticed before, when some openstack components had been updated.
To find out the exact reason, please upload the json response again, but NOT beautified but as a single line. Otherwise it is impossible to determine what element started at column 930 originally.
Fritz Elfert
added a comment - Obviously, something in the openstack response has changed (some single value was expected, but an array value was returned). Similar exceptions have been noticed before, when some openstack components had been updated.
To find out the exact reason, please upload the json response again, but NOT beautified but as a single line . Otherwise it is impossible to determine what element started at column 930 originally.
Obviously, something in the openstack response has changed (some single value was expected, but an array value was returned). Similar exceptions have been noticed before, when some openstack components had been updated.
To find out the exact reason, please upload the json response again, but NOT beautified but as a single line. Otherwise it is impossible to determine what element started at column 930 originally.