Ok I get it after a ping from Brian - integration override - dublin oom is currently pointing to 1.3.2 - could we put in a patch to also upgrade OOM to 1.4.0 - for anyone not running the integration override image: onap/testsuite:1.3.2 in https://git.onap.org/oom/tree/kubernetes/robot/values.yaml#n25
thank you /michael From: [email protected] <[email protected]> On Behalf Of Michael O'Brien Sent: Thursday, February 21, 2019 5:24 PM To: [email protected] Subject: [onap-discuss] robot healthcheck busted in master for last couple days - CD systems and reviews on hold Team, My CD system was offline until yesterday due to a VM issue - I restarted the system but am getting no healthcheck logs into my kibana. http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS from http://jenkins.onap.info/job/oom-cd-master2-aws/174/console 15:08:47 rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "exec: \"/var/opt/ONAP/runTags.sh\": stat /var/opt/ONAP/runTags.sh: no such file or directory" Later today I tried running healthcheck on 2 of my systems - one of which to do the standard get pods and HC prior to an OOM merge - a cherry pick of 1.3.3 data-router - I can't proceed until the robot config is restored from the new ONAP back to the EComp dir. https://gerrit.onap.org/r/#/c/78958/ onap onap-robot-robot-64886c7774<https://gerrit.onap.org/r/#/q/64886c7774>-lkk4h 1/1 Running 0 19m Michael O'Brien 4:55 PM Patch Set 1: New issue running health ++ kubectl --namespace onap exec onap-robot-robot-64886c7774<https://gerrit.onap.org/r/#/q/64886c7774>-lkk4h -- /var/opt/ONAP/runTags.sh -V /share/config/vm_properties.py -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py -v GLOBAL_BUILD_NUMBER:115706 -d /share/logs/0000_ete_health -i health --display 90 rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "exec: \"/var/opt/ONAP/runTags.sh\": stat /var/opt/ONAP/runTags.sh: no such file or directory" command terminated with exit code 126 amdocs@obriensystemsu0:~/oom/kubernetes/robot$ kubectl get pods --all-namespaces | grep robot onap onap-robot-robot-64886c7774<https://gerrit.onap.org/r/#/q/64886c7774>-lkk4h 1/1 Running 0 22m Michael O'Brien 4:57 PM Patch Set 1: root@onap-robot-robot-64886c7774<https://gerrit.onap.org/r/#/q/64886c7774>-lkk4h:/# ls /var/opt OpenECOMP_ETE root@onap-robot-robot-64886c7774<https://gerrit.onap.org/r/#/q/64886c7774>-lkk4h:/# ls /var/opt/OpenECOMP_ETE/runTags.sh /var/opt/OpenECOMP_ETE/runTags.sh Michael O'Brien 5:08 PM Patch Set 1: https://gerrit.onap.org/r/#/c/78445/ has broken healthcheck - pinging owner So the process before any OOM change is to run kubectl get pods -all-namespaces - check for 1/1 2/2 3/3 only - then cd into oom/kubernetes/robot and run the ete-k8s.sh onap health script Could we revert part of the following - thanks - it looks like the dir change does not match the directory. https://gerrit.onap.org/r/#/c/78445/2/kubernetes/robot/ete-k8s.sh /michael This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service <https://www.amdocs.com/about/email-terms-of-service> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15680): https://lists.onap.org/g/onap-discuss/message/15680 Mute This Topic: https://lists.onap.org/mt/29991305/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
