Team, LF, Seeing issues as of 1400EDT where a major portion (about 35-50 of the 107 total) of the docker container images are failing to resolve Started around midday 20180427 after the slowdown that was occurring earlier in the day. 35 on both AWS systems as of a couple hours ago 50 on a slower internal system http://jenkins.onap.info/job/oom-cd-master2-aws/27/console http://jenkins.onap.info/job/oom-cd-master/2789/console ubuntu@ip-10-0-0-144:~$ kubectl get pods --all-namespaces | grep Image onap dev-aaf-84dbb784f-62xrj 0/1 ImagePullBackOff 0 41m onap dev-aai-babel-79d9cc58fb-98blr 0/1 ImagePullBackOff 0 41m onap dev-aai-data-router-cb4cf6b79-rr5sn 0/1 ImagePullBackOff 0 41m onap dev-aai-gizmo-657cb8556c-blbcc 1/2 ErrImagePull 0 41m onap dev-aai-search-data-8686bbd58c-tx84s 1/2 ErrImagePull 0 41m onap dev-appc-cdt-747fb47876-dffnw 0/1 ImagePullBackOff 0 41m onap dev-clamp-9dbb4686d-jwvcz 0/1 ImagePullBackOff 0 41m onap dev-consul-b5d9d5564-c72jq 0/1 ImagePullBackOff 0 40m onap dev-consul-server-8f8f8767-hwfgk 0/1 ImagePullBackOff 0 40m onap dev-dcae-cloudify-manager-d8748c658-gt7xd 0/1 ImagePullBackOff 0 40m onap dev-dcae-healthcheck-67f5dfc95-qf5sx 0/1 ImagePullBackOff 0 40m onap dev-dcae-redis-0 0/1 ImagePullBackOff 0 41m onap dev-multicloud-5d4648c6c5-lmgrm 1/2 ErrImagePull 0 40m onap dev-multicloud-ocata-6465ddf889-dsnw6 1/2 ErrImagePull 0 40m onap dev-multicloud-windriver-8579976b7c-r6qgz 1/2 ErrImagePull 0 40m onap dev-portal-cassandra-5f477975d4-h6rbt 0/1 ErrImagePull 0 40m onap dev-portal-db-745747866f-jh7gn 0/1 ImagePullBackOff 0 40m onap dev-postgres-config-44fxk 0/1 ErrImagePull 0 41m onap dev-robot-5fc4c7846b-b52g4 0/1 ImagePullBackOff 0 40m onap dev-sdc-cs-64f45d77dc-85rhg 0/1 ImagePullBackOff 0 40m onap dev-sdc-es-57777d7789-27b4b 0/1 ErrImagePull 0 40m onap dev-sdc-wfd-5b5d4f58f6-4xg86 0/1 ImagePullBackOff 0 40m onap dev-sms-857f6dbd87-9g87d 0/1 ErrImagePull 0 41m onap dev-smsdb-0 0/2 ErrImagePull 0 41m onap dev-vfc-catalog-7d89bc8b9d-5rdx2 1/2 ErrImagePull 0 40m onap dev-vfc-ems-driver-864685477c-fnthh 0/1 ImagePullBackOff 0 40m onap dev-vfc-multivim-proxy-767757dfd8-ntzkb 0/1 ImagePullBackOff 0 40m onap dev-vfc-nokia-v2vnfm-driver-7fbc7dd6d6-vrf85 0/1 ErrImagePull 0 40m onap dev-vfc-nokia-vnfm-driver-5f9c777fd8-k22hq 1/2 ErrImagePull 0 40m onap dev-vfc-nslcm-76fd6648cc-gk64s 1/2 ErrImagePull 0 40m onap dev-vfc-workflow-78f6466f9d-th8zf 0/1 ImagePullBackOff 0 40m onap dev-vfc-workflow-engine-79769874c7-5q5df 0/1 ImagePullBackOff 0 40m onap dev-vfc-zte-sdnc-driver-5b6c7cbd6b-2wnj8 0/1 ImagePullBackOff 0 40m onap sniro-emulator-7fc8658bcb-zst6d 0/1 ImagePullBackOff 0 40m
Warning Failed 24s (x11 over 5h) kubelet, beijing-oom Failed to pull image "nexus3.onap.org:10001/onap/sdc/sdc-workflow-designer:1.1.0-SNAPSHOT-STAGING-latest": rpc error: code = Unknown desc = Error: image onap/sdc/sdc-workflow-designer:1.1.0-SNAPSHOT-STAGING-latest not found Thank you /michael From: [email protected] [mailto:[email protected]] On Behalf Of Jessica Wagantall Sent: Friday, April 27, 2018 4:50 PM To: [email protected]; onap-release <[email protected]>; Jeremy Phelps <[email protected]>; Andrew Grimberg <[email protected]>; Gildas Lanilis <[email protected]> Subject: [onap-discuss] Nexus3 docker.public configuration changed. Dear ONAP team, Today morning we had some issues with our docker.io<http://docker.io> proxy for which some teams were not able to pull some needed libraries. This problem has been corrected this morning. However, while debugging this issue, we realized our docker.public (10001) had a configuration error. docker.public should only be a group for docker.releases and docker.io<http://docker.io> (in that order) so that any dependencies are first looked for in docker.releases and, if not found, it would be looked for in docker.io<http://docker.io>. Our configuration was erroneously including docker.snapshots and docker.staging in the group too. This configuration has been adjusted and some teams might see some dependency issues which need to be corrected by the teams making a release of their binaries so that they become available in the docker.public group. Basically, we are following this rule that we are already following in Nexus2: https://wiki.onap.org/display/DW/Release+Versioning+Strategy#ReleaseVersioningStrategy-ONAPVersioningStrategy I am here to help making any releases if the team needs and of course with PTL approval and via RT ticket. Please let me know if you guys have any questions. Thanks a ton! Jess This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
