-
Bug
-
Resolution: Won't Do
-
Medium
-
None
-
None
-
None
Installing a released ONAP version (e.g. 3.0.0-ONAP) using OOM can lead to different behavior due to the usage of "floating" versions of container images in the helm charts:
# find oom/kubernetes/|grep values.yaml|xargs grep image: ... oom/kubernetes/dmaap/charts/message-router/charts/message-router-zookeeper/values.yaml:image: wurstmeister/zookeeper:latest oom/kubernetes/aai/values.yaml: image: onap/fproxy:2.1-STAGING-latest oom/kubernetes/aai/values.yaml: image: onap/rproxy:2.1-STAGING-latest oom/kubernetes/aai/values.yaml: image: onap/tproxy-config:2.1-STAGING-latest ... oom/kubernetes/common/music/charts/music-cassandra-job/values.yaml: image: library/busybox:latest oom/kubernetes/common/music/charts/music-tomcat/values.yaml: image: library/busybox:latest ...
So the released version cannot be reproduced (see https://jira.onap.org/browse/SDC-2058)
Maybe before releasing OOM a check should be implemented to verify the usage of fixed versions in the helm charts.
- relates to
-
COMMON-27
ONAP Docker images and base images should be ONAP controlled
-
- Open
-
-
-
- Closed
-