adoroszlai opened a new pull request, #7496:
URL: https://github.com/apache/ozone/pull/7496

   ## What changes were proposed in this pull request?
   
   Logs are not collected if Kubernetes check fails before starting tests (due 
to `set -e` exiting early).
   
   On `master` prior to HDDS-11718 `kubernetes` check was failing (silently):
   https://github.com/apache/ozone/actions/runs/12033431383/job/33548517871
   
   Excerpt from Kubernetes check output:
   
   ```
   100 'grep_log scm-0 SCM exiting safe mode.' is failed...
   ...
   Process completed with exit code 1.
   ```
   
   
[Artifact](https://github.com/apache/ozone/actions/runs/12033431383/artifacts/2239592951)
 has no logs from the cluster.
   
   https://issues.apache.org/jira/browse/HDDS-11801
   
   ## How was this patch tested?
   
   Tested this change on top of cc1a37476bb6e24c0d2c83b25ac64b5499f1390d:
   https://github.com/adoroszlai/ozone/actions/runs/12048774547
   
   Excerpt from Kubernetes check output:
   
   ```
   100 'grep_log scm-0 SCM exiting safe mode.' is failed...
   ...
   ERROR: Test execution of getting-started is FAILED!!!!
   ```
   
   
[Artifact](https://github.com/adoroszlai/ozone/actions/runs/12048774547/artifacts/2244067180)
 has logs:
   
   ```
   $ unzip -t kubernetes.zip 
   Archive:  kubernetes.zip
       testing: getting-started/pod-datanode-0.log   OK
       testing: getting-started/pod-datanode-1.log   OK
       testing: getting-started/pod-datanode-2.log   OK
       testing: getting-started/pod-om-0.log   OK
       testing: getting-started/pod-s3g-0.log   OK
       testing: getting-started/pod-scm-0-init.log   OK
       testing: getting-started/pod-scm-0.log   OK
       testing: minikube/pod-datanode-0.log   OK
       testing: minikube/pod-datanode-1.log   OK
       testing: minikube/pod-datanode-2.log   OK
       testing: minikube/pod-om-0.log    OK
       testing: minikube/pod-s3g-0.log   OK
       testing: minikube/pod-scm-0-init.log   OK
       testing: minikube/pod-scm-0.log   OK
       testing: output.log               OK
       testing: ozone/pod-datanode-0.log   OK
       testing: ozone/pod-datanode-1.log   OK
       testing: ozone/pod-om-0.log       OK
       testing: ozone/pod-s3g-0.log      OK
       testing: ozone/pod-scm-0-init.log   OK
       testing: ozone/pod-scm-0.log      OK
       testing: ozone-dev/pod-datanode-0.log   OK
       testing: ozone-dev/pod-datanode-1.log   OK
       testing: ozone-dev/pod-datanode-2.log   OK
       testing: ozone-dev/pod-jaeger-0.log   OK
       testing: ozone-dev/pod-om-0.log   OK
       testing: ozone-dev/pod-prometheus-548f95bb6b-tr9b9.log   OK
       testing: ozone-dev/pod-s3g-0.log   OK
       testing: ozone-dev/pod-scm-0-init.log   OK
       testing: ozone-dev/pod-scm-0.log   OK
       testing: ozone-ha/pod-datanode-0.log   OK
       testing: ozone-ha/pod-datanode-1.log   OK
       testing: ozone-ha/pod-datanode-2.log   OK
       testing: ozone-ha/pod-om-0.log    OK
       testing: ozone-ha/pod-s3g-0.log   OK
       testing: ozone-ha/pod-scm-0-bootstrap.log   OK
       testing: ozone-ha/pod-scm-0-init.log   OK
       testing: ozone-ha/pod-scm-0.log   OK
       testing: ozone-ha/pod-scm-1-bootstrap.log   OK
       testing: ozone-ha/pod-scm-1-init.log   OK
       testing: ozone-ha/pod-scm-1.log   OK
       testing: ozone-ha/pod-scm-2-bootstrap.log   OK
       testing: ozone-ha/pod-scm-2-init.log   OK
       testing: ozone-ha/pod-scm-2.log   OK
       testing: summary.txt              OK
   No errors detected in compressed data of kubernetes.zip.
   ```
   
   CI (after HDDS-11718):
   https://github.com/adoroszlai/ozone/actions/runs/12049809854


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to