Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-8413

SystemStateInfoTest.ReadProcNetDev fails inside a Docker container

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • Impala 3.3.0
    • Impala 3.3.0
    • Backend
    • None
    • ghx-label-7

    Description

      SystemStateInfoTest.ReadProcNetDev fails consistently when executed inside a Docker container using test-with-docker.py (this is the container version that hosts the complete minicluster inside the container).

      The test seems to assume that by the time it runs, the number of transmitted and received bytes and packets will both be nonzero (excluding the loopback interface). However, this assumption fails inside the Docker container used by test-with-docker.py.

      I started a Docker-based run with test-with-docker.py, running only BE_TEST. As the tests were running, I jumped into the container when about 75% of the BE tests were already executed, and captured the contents of /proc/net/dev :

      $ docker ps
      
      CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS               NAMES
      
      0e967d480e8d        efd25829a079        "/mnt/base/entrypoin…"   17 minutes ago      Up 17 minutes                           i-20190414-111948-be-test
      
      $ docker exec -it i-20190414-111948-be-test /bin/bash
      
      impdev@i-20190414-111948:~/Impala$ cat /proc/net/dev
      
      Inter-|   Receive                                                |  Transmit
      
      face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
      
          lo: 232573986  353806    0    0    0     0          0         0 232573986  353806    0    0    0     0       0          0
      
        eth0:     828      10    0    0    0     0          0         0        0       0    0    0    0     0       0          0
      

      The layout is ugly, but it clearly shows that the number of transmitted anything for eth0 is still zero.

      Additionally, it would be useful if the test logged the contents of /proc/net/dev for failure cases.

      Attachments

        Activity

          People

            lv Lars Volker
            laszlog Laszlo Gaal
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: