Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-34733

main.mysqld--help-aria test failure: feedback plugin: failed to retrieve the MAC address

Details

    Description

      While testing latest MariaDB 11.4.3 I ran into this MTR failure which seems like some kind of regression:

      main.mysqld--help-aria                   w2 [ fail ]
              Test ended at 2024-08-09 17:00:48
       
      CURRENT_TEST: main.mysqld--help-aria
      --- /tmp/build/source/mysql-test/main/mysqld--help-aria.result	2024-06-06 20:49:59.511836568 +0000
      +++ /tmp/build/source/mysql-test/main/mysqld--help-aria.reject	2024-08-09 17:00:48.426958935 +0000
      @@ -1,9 +1,12 @@
       flush tables;
      +[ERROR] feedback plugin: failed to retrieve the MAC address
       #
       # Check that we don't write any data to wrong or not existing datadir
       #
      +[ERROR] feedback plugin: failed to retrieve the MAC address
       [Warning] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some options may be missing from the help text
       #
       # Check with existing directory
       #
      +[ERROR] feedback plugin: failed to retrieve the MAC address
       [Warning] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some options may be missing from the help text
       
      Result length mismatch
      

      I will add further details later after more testing.

      Attachments

        Issue Links

          Activity

            I fails because my testing environment has only loopback interface which has MAC addres 00:00:00:00:00:00.

            13:34:51.770461 socket(AF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
            13:34:51.770509 ioctl(3, SIOCGIFCONF, {ifc_len=1280 /* 32 * sizeof(struct ifreq) */ => 80 /* 2 * sizeof(struct ifreq) */, ifc_buf=[{ifr_name="lo", ifr_addr={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("127.0.0.1")}}, {ifr_name="lo", ifr_addr={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("10.0.0.1")}}]}) = 0
            13:34:51.770555 ioctl(3, SIOCGIFHWADDR, {ifr_name="lo", ifr_hwaddr={sa_family=ARPHRD_LOOPBACK, sa_data=00:00:00:00:00:00}}) = 0
            13:34:51.770592 ioctl(3, SIOCGIFHWADDR, {ifr_name="lo", ifr_hwaddr={sa_family=ARPHRD_LOOPBACK, sa_data=00:00:00:00:00:00}}) = 0
            13:34:51.770626 close(3)                = 0
            13:34:51.770672 write(2, "2024-12-09 13:34:51 0 [ERROR] fe"..., 82) = 82
            

            The algorithm searches the first non-zero MAC address, which is not available in my case.

            arkamar Petr Vaněk added a comment - I fails because my testing environment has only loopback interface which has MAC addres 00:00:00:00:00:00 . 13:34:51.770461 socket(AF_INET, SOCK_DGRAM, IPPROTO_IP) = 3 13:34:51.770509 ioctl(3, SIOCGIFCONF, {ifc_len=1280 /* 32 * sizeof(struct ifreq) */ => 80 /* 2 * sizeof(struct ifreq) */, ifc_buf=[{ifr_name="lo", ifr_addr={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("127.0.0.1")}}, {ifr_name="lo", ifr_addr={sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("10.0.0.1")}}]}) = 0 13:34:51.770555 ioctl(3, SIOCGIFHWADDR, {ifr_name="lo", ifr_hwaddr={sa_family=ARPHRD_LOOPBACK, sa_data=00:00:00:00:00:00}}) = 0 13:34:51.770592 ioctl(3, SIOCGIFHWADDR, {ifr_name="lo", ifr_hwaddr={sa_family=ARPHRD_LOOPBACK, sa_data=00:00:00:00:00:00}}) = 0 13:34:51.770626 close(3) = 0 13:34:51.770672 write(2, "2024-12-09 13:34:51 0 [ERROR] fe"..., 82) = 82 The algorithm searches the first non-zero MAC address, which is not available in my case.

            I just uploaded 11.4.4 to Debian unstable and multiple builds are failing on this..

            otto Otto Kekäläinen added a comment - I just uploaded 11.4.4 to Debian unstable and multiple builds are failing on this..
            otto Otto Kekäläinen added a comment - I fully disabled this test in Debian now: https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/867f7bce8a9138e1e06dc3a36a935fc397ede504

            I confirm this was passing in https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=amd64&ver=1%3A11.4.5-2%7Eexp1&stamp=1740281411&raw=0

            main.mysqld--help-aria                   w1 [ pass ]    393
            

            I will re-enable the tests and monitor if it shows up sporadically again.

            otto Otto Kekäläinen added a comment - I confirm this was passing in https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=amd64&ver=1%3A11.4.5-2%7Eexp1&stamp=1740281411&raw=0 main.mysqld--help-aria w1 [ pass ] 393 I will re-enable the tests and monitor if it shows up sporadically again.

            Test is now failing on Debian builders on a different error:

            main.mysqld--help-aria                   w1 [ fail ]
                    Test ended at 2025-04-23 00:23:57
             
            CURRENT_TEST: main.mysqld--help-aria
            --- /build/reproducible-path/mariadb-11.8.1/mysql-test/main/mysqld--help-aria.result	2025-02-12 10:13:21.000000000 +0000
            +++ /build/reproducible-path/mariadb-11.8.1/mysql-test/main/mysqld--help-aria.reject	2025-04-23 00:23:56.870451295 +0000
            @@ -1,12 +1,9 @@
             flush tables;
            -[Warning] --table-cache is deprecated and will be removed in a future release. Please use --table-open-cache instead.
             #
             # Check that we don't write any data to wrong or not existing datadir
             #
            -[Warning] --table-cache is deprecated and will be removed in a future release. Please use --table-open-cache instead.
             [Warning] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some options may be missing from the help text
             #
             # Check with existing directory
             #
            -[Warning] --table-cache is deprecated and will be removed in a future release. Please use --table-open-cache instead.
             [Warning] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some options may be missing from the help text
             
            Result length mismatch
            

            Example of full log at https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=all&ver=1%3A11.8.1-3&stamp=1745367981&raw=0

            Filed new issue MDEV-36668

            otto Otto Kekäläinen added a comment - Test is now failing on Debian builders on a different error: main.mysqld--help-aria w1 [ fail ] Test ended at 2025-04-23 00:23:57   CURRENT_TEST: main.mysqld--help-aria --- /build/reproducible-path/mariadb-11.8.1/mysql-test/main/mysqld--help-aria.result 2025-02-12 10:13:21.000000000 +0000 +++ /build/reproducible-path/mariadb-11.8.1/mysql-test/main/mysqld--help-aria.reject 2025-04-23 00:23:56.870451295 +0000 @@ -1,12 +1,9 @@ flush tables; -[Warning] --table-cache is deprecated and will be removed in a future release. Please use --table-open-cache instead. # # Check that we don't write any data to wrong or not existing datadir # -[Warning] --table-cache is deprecated and will be removed in a future release. Please use --table-open-cache instead. [Warning] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some options may be missing from the help text # # Check with existing directory # -[Warning] --table-cache is deprecated and will be removed in a future release. Please use --table-open-cache instead. [Warning] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some options may be missing from the help text   Result length mismatch Example of full log at https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=all&ver=1%3A11.8.1-3&stamp=1745367981&raw=0 Filed new issue MDEV-36668

            People

              serg Sergei Golubchik
              otto Otto Kekäläinen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.