Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

VVP Imagescanner Pod fails on OOM deploy due to lack of Redis conn error

Description

Upon successful deployment of Casablanca with all components present except PNDA, the VVP component shows frequent pod restarts on the Imagescanner pod.  Example VVP component pod status after a few days of Casablanca uptime (see highlighted red font):

onap onap-vvp-vvp-647df775c-kwgzp 1/1 Running 0 2d
onap onap-vvp-vvp-ci-uwsgi-869547b95d-8lfl5 1/1 Running 0 2d
onap onap-vvp-vvp-cms-uwsgi-67875bc58d-c2p6v 1/1 Running 0 2d
onap onap-vvp-vvp-em-uwsgi-cb5946fcd-75gbt 1/1 Running 1 2d
onap onap-vvp-vvp-ext-haproxy-78cfc9686-vlmhr 1/1 Running 0 2d
onap onap-vvp-vvp-gitlab-d854f8b88-dp9cd 1/1 Running 0 2d
onap onap-vvp-vvp-imagescanner-67ddfd664d-25dm5 3/3 Running 156 2d
onap onap-vvp-vvp-int-haproxy-6c77648b48-mgm9n 1/1 Running 0 2d
onap onap-vvp-vvp-jenkins-6c8b6fff88-fqtb9 1/1 Running 0 2d
onap onap-vvp-vvp-postgres-559b9fc8b5-mblhg 1/1 Running 0 2d
onap onap-vvp-vvp-redis-5d566fdf44-mznns 1/1 Running 0 2d

 

Log output from the pod shows respectively:

 # kubectl -n onap logs onap-vvp-vvp-imagescanner-67ddfd664d-25dm5 -c imagescanner-worker

<...snip...>

[2019-01-03 15:26:50,223: ERROR/MainProcess] consumer: Cannot connect to redis://redis:6379//: Error -2 connecting to redis:6379. Name does not resolve..
Trying again in 2.00 seconds...

 # kubectl -n onap logs onap-vvp-vvp-imagescanner-67ddfd664d-25dm5 -c notification-worker

<...snip...>

[2019-01-03 15:32:37,527: ERROR/MainProcess] consumer: Cannot connect to redis://redis:6379//: Error -2 connecting to redis:6379. Name does not resolve..
Trying again in 32.00 seconds...

 

Also, there is a (perhaps unrelated) warning at the top of each of these logs which may need attention:

/usr/lib/python3.6/site-packages/celery/platforms.py:796: RuntimeWarning: You're running the worker with superuser privileges: this is
absolutely not recommended!

Please specify a different user using the --uid option.

User information: uid=0 euid=0 gid=0 egid=0

uid=uid, euid=euid, gid=gid, egid=egid,

 

The related JIRA issue noted (VVP-117) appears to have the same vvp-imagescanner pod restarts shown in that ticket's description text.

Environment

None

Activity

Show:

Former user February 11, 2019 at 9:29 PM

Thanks guys, I'll close it.

Former user February 11, 2019 at 7:38 PM

Hi , , : this is good to cancel/close as far as I'm concerned.  Thank you.

Former user February 11, 2019 at 5:28 PM

VVP was removed from OOM via . Can we cancel/close this ticket?

Former user February 8, 2019 at 3:57 PM

are we good to close this one?

Former user January 18, 2019 at 12:01 AM

putting a hold on vvp's merge https://gerrit.onap.org/r/#/c/75779/1/kubernetes/vvp/charts/vvp-imagescanner/values.yaml

so that gary's tested larger patch does not get a merge conflict in https://gerrit.onap.org/r/#/c/75910/1/kubernetes/vvp/charts/vvp-imagescanner/values.yaml

When OOM-1053 is merged it will close this one as well

Done

Details

Assignee

Reporter

Labels

Sprint

Fix versions

Affects versions

Priority

Created January 3, 2019 at 3:47 PM
Updated February 11, 2019 at 9:30 PM
Resolved February 11, 2019 at 9:30 PM