Getting a JsonParseException with message "Unexpected character ('<' (code 60)): expected a valid value "

Hi All,
I got a very basic kubernetes deployment pipeline working in a single-stage deployment pipeline. I then went to add two more stages for “higher” environments (staging + prod) but my original single stage (still the first stage of the pipeline) started giving me this exception. I’m a little unsure how to proceed because I don’t see anything online about this message being associated with at all.

I’m going to try to reset everything in Docker Desktop but if anyone has come across this before, any insight would be greatly appreciated.

If the reset works I’ll take the question down.

UPDATE 1: I’m no longer getting the Exception but I am getting: “Delegates are not available”.
I’m not sure how that’s possible since my delegate pod tells me that it’s running:

delegatethree-0   1/1     Running   0          2m16s
newdelegate-0     1/1     Running   0          44m

When I try to run the pipeline, if I select the “tags” dropdown to add a tag to the execution, I get the following error:
Stage Deploy_Dev: Please make sure that your delegates are connected. Refer for more information on delegate Installation

Strangely, all of my connectors and delegates look to be connected from within the Harness UI.

Looks like I was pointing to the wrong delegate (an old one I had deleted). Now I’m back to getting the original:
JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (okhttp3.ResponseBody$BomAwareReader); line: 1, column: 2]

Hi Ramy -

Can you send a link to the failed execution where you’r getting that JsonParseException error? Also, feel free to join us on slack here Slack


1 Like

Thanks for getting back to me, @micah !
Here’s the link to my failed pipeline execution.

Turns out my link to a docker registry was incorrect so my connector was broken. Used a different URL and everything worked great! Thanks, @Shruthikini !

Awesome :smiley: @Ramy_Abdel-Azim. Feel free to reach out for any further queries :raised_hands: