[HDDS-11186] First container log missing from bundle

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0, 1.4.1
• Fix Version/s: 2.0.0, 1.4.1
• Component/s: docker-compose, test
• Labels: pull-request-available
• Target Version/s: 2.0.0, 1.4.1
• Assignee: Attila Doroszlai
• Reporter: Attila Doroszlai
• Created: 16/Jul/24 06:29
• Updated: 24/Jul/24 06:40
• Resolved: 17/Jul/24 11:23

Description

Logs for one of the containers is missing from the test artifact.

For example, docker-ozone-datanode-1.log and docker-ozonesecure-ha-datanode1-1.log here:

$ find 2024/07/12/32233/acceptance-s3a -name 'docker*' | sort
2024/07/12/32233/acceptance-s3a/ozone/s3a/docker-ozone-datanode-2.log
2024/07/12/32233/acceptance-s3a/ozone/s3a/docker-ozone-datanode-3.log
2024/07/12/32233/acceptance-s3a/ozone/s3a/docker-ozone-httpfs-1.log
2024/07/12/32233/acceptance-s3a/ozone/s3a/docker-ozone-om-1.log
2024/07/12/32233/acceptance-s3a/ozone/s3a/docker-ozone-recon-1.log
2024/07/12/32233/acceptance-s3a/ozone/s3a/docker-ozone-s3g-1.log
2024/07/12/32233/acceptance-s3a/ozone/s3a/docker-ozone-scm-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-datanode2-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-datanode3-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-httpfs-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-kdc-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-kms-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-om1-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-om2-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-om3-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-recon-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-s3g-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-scm1.org-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-scm2.org-1.log
2024/07/12/32233/acceptance-s3a/ozonesecure-ha/s3a/docker-ozonesecure-ha-scm3.org-1.log

This happens due to difference in output of Docker Compose v1 and v2:

• v1 prints two lines of header,
• v2 prints only one.

v1

$ docker-compose ps                                          
      Name                    Command               State                                            Ports                                          
----------------------------------------------------------------------------------------------------------------------------------------------------
ozone-datanode-1   /usr/local/bin/dumb-init - ...   Up      0.0.0.0:33548->19864/tcp,:::33548->19864/tcp, 0.0.0.0:33549->9882/tcp,:::33549->9882/tcp
ozone-datanode-2   /usr/local/bin/dumb-init - ...   Up      0.0.0.0:33550->19864/tcp,:::33550->19864/tcp, 0.0.0.0:33551->9882/tcp,:::33551->9882/tcp
ozone-datanode-3   /usr/local/bin/dumb-init - ...   Up      0.0.0.0:33546->19864/tcp,:::33546->19864/tcp, 0.0.0.0:33547->9882/tcp,:::33547->9882/tcp
ozone-httpfs-1     /usr/local/bin/dumb-init - ...   Up      0.0.0.0:14000->14000/tcp,:::14000->14000/tcp                                            
ozone-om-1         /usr/local/bin/dumb-init - ...   Up      0.0.0.0:9862->9862/tcp,:::9862->9862/tcp, 0.0.0.0:9874->9874/tcp,:::9874->9874/tcp      
ozone-recon-1      /usr/local/bin/dumb-init - ...   Up      0.0.0.0:9888->9888/tcp,:::9888->9888/tcp                                                
ozone-s3g-1        /usr/local/bin/dumb-init - ...   Up      0.0.0.0:9878->9878/tcp,:::9878->9878/tcp                                                
ozone-scm-1        /usr/local/bin/dumb-init - ...   Up      0.0.0.0:9860->9860/tcp,:::9860->9860/tcp, 0.0.0.0:9876->9876/tcp,:::9876->9876/tcp      

v2

$ docker compose ps
NAME                IMAGE                                  COMMAND                  SERVICE             CREATED             STATUS              PORTS
ozone-datanode-1    apache/ozone-runner:20240316-jdk17-1   "/usr/local/bin/dumb…"   datanode            25 seconds ago      Up 23 seconds       0.0.0.0:33549->9882/tcp, :::33549->9882/tcp, 0.0.0.0:33548->19864/tcp, :::33548->19864/tcp
ozone-datanode-2    apache/ozone-runner:20240316-jdk17-1   "/usr/local/bin/dumb…"   datanode            25 seconds ago      Up 22 seconds       0.0.0.0:33551->9882/tcp, :::33551->9882/tcp, 0.0.0.0:33550->19864/tcp, :::33550->19864/tcp
ozone-datanode-3    apache/ozone-runner:20240316-jdk17-1   "/usr/local/bin/dumb…"   datanode            25 seconds ago      Up 23 seconds       0.0.0.0:33547->9882/tcp, :::33547->9882/tcp, 0.0.0.0:33546->19864/tcp, :::33546->19864/tcp
ozone-httpfs-1      apache/ozone-runner:20240316-jdk17-1   "/usr/local/bin/dumb…"   httpfs              25 seconds ago      Up 23 seconds       0.0.0.0:14000->14000/tcp, :::14000->14000/tcp
ozone-om-1          apache/ozone-runner:20240316-jdk17-1   "/usr/local/bin/dumb…"   om                  25 seconds ago      Up 23 seconds       0.0.0.0:9862->9862/tcp, :::9862->9862/tcp, 0.0.0.0:9874->9874/tcp, :::9874->9874/tcp
ozone-recon-1       apache/ozone-runner:20240316-jdk17-1   "/usr/local/bin/dumb…"   recon               25 seconds ago      Up 23 seconds       0.0.0.0:9888->9888/tcp, :::9888->9888/tcp
ozone-s3g-1         apache/ozone-runner:20240316-jdk17-1   "/usr/local/bin/dumb…"   s3g                 25 seconds ago      Up 23 seconds       0.0.0.0:9878->9878/tcp, :::9878->9878/tcp
ozone-scm-1         apache/ozone-runner:20240316-jdk17-1   "/usr/local/bin/dumb…"   scm                 25 seconds ago      Up 23 seconds       0.0.0.0:9860->9860/tcp, :::9860->9860/tcp, 0.0.0.0:9876->9876/tcp, :::9876->9876/tcp

Issue Links

• links to: GitHub Pull Request #6952