Shield import errand is failing

[julweber]

Hi,

we experience an issue when running the import errand for our shield deployment in many cases. Normally the import errand runs fine, but after a stemcell/vm update many times we experience the following issue with exactly the same shield configuration that is imported fine normally:

Using deployment 'shield' 
Task 4841332 
Task 4841332 | 08:29:20 | Preparing deployment: Preparing deployment (00:00:01) 
Task 4841332 | 08:29:21 | Running errand: shield/863fa9a1-e840-4ff3-abaf-d131a9e6d7b9 (0) (00:00:01) 
Task 4841332 | 08:29:22 | Fetching logs for shield/863fa9a1-e840-4ff3-abaf-d131a9e6d7b9 (0): Finding and packing log files (00:00:05) 
Task 4841332 Started Wed Jun 2 08:29:20 UTC 2021 
Task 4841332 Finished Wed Jun 2 08:29:27 UTC 2021 
Task 4841332 Duration 00:00:07 Task 4841332 done 

Instance shield/863fa9a1-e840-4ff3-abaf-d131a9e6d7b9 

Exit Code 1 

Stdout set api to shield-int.sys.q.ocf.<our domain>

revoke token Stderr 
!!! invalid character '<' looking for beginning of value

1 errand(s)

Errand 'import' completed with error (exit code 1)

It seems that the API is not giving back a correct JSON format and this leads to the failing requests.

We also introduced a 10 minute waiting time after the shield deployment before the import errand run, which also does not fix the issue. Sometimes after the third try it works as expected but in other cases we need to delete the shield deployment completely via bosh and redeploy to make it work again.

Do you have any idea how to solve this? Any help would be appreciated.

Kind regards, Julian Weber

[stale[bot]]

This issue has been automatically marked as abandoned because it has not seen any activity or updates in 30 days. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.