Skip to main content

An issue is occurring with uploading documents to the Azure blob repository.

In this scenario, customer is unable to attach documents to POs as the error, ‘Error when checking the repository validity: null’ appears.

 

Product version: 23.1.9

The problem was caused by the container ifs-file-storage which was Unhealthy and reported Readiness probe failure:

Error:
the error isEvents:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 71s (x37368 over 6d20h) kubelet Readiness probe failed: Get "http://10.228.22.151:8080/q/health/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

A "readiness probe failed" message typically indicates an issue with a Kubernetes pod. In Kubernetes, readiness probes are used to determine if a pod is ready for service requests. When a readiness probe fails, it means that the container within the pod is not ready to serve traffic even though it might be running.

Restarting the pod solved the problem and enables to attach a document without errors.

Hi @Divya Wickramasinghe ,

There was a similar issue resolved through https://support.ifs.com/csm?id=csm_ticket&table=sn_customerservice_case&sys_id=4e977a9f47f40a5800d8c752e36d43a1. Please refer the above case to get an additional information on this.

Regards,
Asitha

  

@Asitha Rajapaksha 

It might have been the same issue and Divya asked here earlier, but decided to remove the post/question, but I convinced her it's beneficial for others to see the problem and solution here 🙂 

 

Reply


Terms & ConditionsCookie settings