-
Bug
-
Resolution: Done
-
Medium
-
Frankfurt Release
-
None
A new error occured on recent gates
the external API healthcheck is failing
ConnectionError: HTTPSConnectionPool(host='nbi.onap', port=8443): Max retries exceeded with url: /nbi/api/v4/status?fullStatus=true (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fe0de788e90>: Failed to establish a new connection: [Errno -2] Name does not resolve'))
it is not systematic
it is due to the fact that an error on the deployment of the helm chart reported by the onap-helm test
Chart onap-nbi
STATUS: FAILED
Chart problem
info:
Description: 'Release "onap-nbi" failed: unexpected error when reading response
body. Please retry. Original error: read tcp 10.233.77.87:46162->10.233.0.1:443:
read: connection reset by peer'
first_deployed:
nanos: 514050669
seconds: 1590650003
last_deployed:
nanos: 514050669
seconds: 1590650003
status:
code: 4
name: onap-nbi
namespace: onap
+ aosull01
as it is maybe not reproducible.. I set Medium severity
but I prefer to track it somewhere (as it seems we also got this error once recently)
- relates to
-
OOM-2436 mariadb-init config job reports success although db_init.sh fails
- Closed