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

plugins.cracklib_password_check and plugins.two_password_validations fail in buildbot on p8-trusty-bintar[-debug]

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.1(EOL)
    • N/A
    • Tests
    • None

    Description

      Tests fail due to the missing libcrack.so.2:

      http://buildbot.askmonty.org/buildbot/builders/p8-trusty-bintar-debug/builds/534/steps/test/logs/stdio

      plugins.two_password_validations         w1 [ fail ]
              Test ended at 2015-07-17 21:51:47
       
      CURRENT_TEST: plugins.two_password_validations
      mysqltest: At line 19: query 'install soname "cracklib_password_check"' failed: 1126: Can't open shared library '/var/lib/buildbot/maria-slave/power8-vlp04-bintar-debug/build/mysql-test/var/1/plugins/cracklib_password_check.so' (errno: 0, libcrack.so.2: cannot open shared object file: No such file or directory)
       
      The result from queries just before the failure was:
      install soname "simple_password_check";
      grant select on *.* to Fff_fff1 identified by '1fff_ffF';
      drop user Fff_fff1;
      install soname "cracklib_password_check";
       
       - saving '/var/lib/buildbot/maria-slave/power8-vlp04-bintar-debug/build/mysql-test/var/1/log/plugins.two_password_validations/' to '/var/lib/buildbot/maria-slave/power8-vlp04-bintar-debug/build/mysql-test/var/log/plugins.two_password_validations/'

      Attachments

        Issue Links

          Activity

            People

              svoj Sergey Vojtovich
              elenst Elena Stepanova
              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.