Security jenkins jobs failed on importing data by core-data

[cherrycl]

20:37:11 ��core-data-importer
20:37:11
20:37:11 → Import valueDescriptor
20:37:11 GET https://kong:8443/coredata/api/v1/ping [errored]
20:37:11 connect ECONNREFUSED 172.17.0.8:8443
20:37:11 POST https://kong:8443/coredata/api/v1/valuedescriptor POST https://kong:8443/coredata/api/v1/valuedescriptor POST https://kong:8443/coredata/api/v1/valuedescriptor POST https://kong:8443/coredata/api/v1/valuedescriptor POST https://kong:8443/coredata/api/v1/valuedescriptor POST https://kong:8443/coredata/api/v1/valuedescriptor POST https://kong:8443/coredata/api/v1/valuedescriptor POST https://kong:8443/coredata/api/v1/valuedescriptor POST https://kong:8443/coredata/api/v1/valuedescriptor [errored]
20:37:11 connect ECONNREFUSED 172.17.0.8:8443
20:37:11 [errored]
20:37:11 connect ECONNREFUSED 172.17.0.8:8443
20:37:11 [errored]
20:37:11 connect ECONNREFUSED 172.17.0.8:8443
20:37:11 [errored]
20:37:11 connect ECONNREFUSED 172.17.0.8:8443
20:37:11 [errored]
20:37:11 connect ECONNREFUSED 172.17.0.8:8443
20:37:11 [errored]
20:37:11 connect ECONNREFUSED 172.17.0.8:8443
20:37:11 [errored]
20:37:11 connect ECONNREFUSED 172.17.0.8:8443
20:37:11 [errored]
20:37:11 connect ECONNREFUSED 172.17.0.8:8443
20:37:11 [errored]
20:37:11 connect ECONNREFUSED 172.17.0.8:8443
21:33:01 Build timed out (after 60 minutes). Marking the build as failed.

[cloudxxx8]

@tingyuz @bnevis-i The security test on master are failed to run. Do you have any idea?

[bnevis-i]

Initial triage suggests that kong-migrations is failing to start due to kong-db (postgres) failing to start.

[bnevis-i]

Apparently the upstream postgres release was changed 4 days ago from a WARNING that POSTGRES_PASSWORD is unspecified to an ERROR.

https://hub.docker.com/layers/postgres/library/postgres/9.6/images/sha256-92cba31ae0ab4480e227d03b68cfc9406b6c69d0b731f0b20e12de00c3d4c311?context=explore

(Old prior to 9.6.17)

****************************************************
WARNING: No password has been set for the database.
         This will allow anyone with access to the
         Postgres port to access your database. In
         Docker's default configuration, this is
         effectively any other container on the same
         system.

         Use "-e POSTGRES_PASSWORD=password" to set
         it in "docker run".
****************************************************

(New: 9.6.17 or later)

Error: Database is uninitialized and superuser password is not specified.
       You must specify POSTGRES_PASSWORD for the superuser. Use
       "-e POSTGRES_PASSWORD=password" to set it in "docker run".

       You may also use POSTGRES_HOST_AUTH_METHOD=trust to allow all connections
       without a password. This is *not* recommended. See PostgreSQL
       documentation about "trust":
       https://www.postgresql.org/docs/current/auth-trust.html

[bnevis-i]

Fix submitted.

cc: @mkbhanda @tingyuz

[bnevis-i]

Colin submitted an unmerged fix for this days ago

edgexfoundry/developer-scripts#219

Pulling my PR and referring to Colin's instead.

[cloudxxx8]

is this related to edgexfoundry/go-mod-secrets#49 ?

[bnevis-i]

@cloudxxx8 No. go-mod-secrets 49 causes services to fail to get the mongodb password. This one just causes kong to fail to start because the Postgres database doesn't come up.

[bnevis-i]

I believe this issue can be closed now.

[cloudxxx8]

@bnevis-i since the blackbox test is still blocked now, I will close this issue once we can verify it on Jenkins

[bnevis-i]

@cloudxxx8 Is this still an issue?

[cloudxxx8]

yes, let's close this issue.
thanks for the reminder.