Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.5, 10.6
    • None
    • Upgrades
    • Linux, n.a.

    Description

      The Utility mariadb_upgrade does NOT upgrade but prints message:

      mariadb-upgrade --user=root
      This installation of MariaDB is already upgraded to 10.6.7-MariaDB.
      There is no need to run mysql_upgrade again for 10.6.9-MariaDB.
      You can use --force if you still want to run mysql_upgrade

      This by itself is not a real problem and can be solved by --force. But we have cases were it is NOT true!!!

      10.4.13 still works OK 10.5.17 ff does NOT so it must be introduced in 10.5

      See also next bug.

      Attachments

        Issue Links

          Activity

            Thanks for opening this ticket Oli. I will start taking a look at this.

            But we have cases were it is NOT true!!!

            Do you mean cases where --force does not run mysql_upgrade successfully? Can you specify where this would be not true?

            robinnew Robin Newhouse added a comment - Thanks for opening this ticket Oli. I will start taking a look at this. But we have cases were it is NOT true!!! Do you mean cases where --force does not run mysql_upgrade successfully? Can you specify where this would be not true?

            I meant: The message "there is no need to run mysql_upgade again" is NOT true. We had some cases where a forced mysql_upgrade was taking nearly an hour (zillions of tables)!

            So in my opinion it should behave something like this:

            if server_version == dd_version
            do nothing and exit
            if server_version != dd_version
            check if there is something to upgrade
            if there is something to upgrade
            do upgrade and change the mysql_upgrade_info file
            else
            silently change the mysql_upgrade_info file
            print message upgrade done.

            oli Oli Sennhauser added a comment - I meant: The message "there is no need to run mysql_upgade again" is NOT true. We had some cases where a forced mysql_upgrade was taking nearly an hour (zillions of tables)! So in my opinion it should behave something like this: if server_version == dd_version do nothing and exit if server_version != dd_version check if there is something to upgrade if there is something to upgrade do upgrade and change the mysql_upgrade_info file else silently change the mysql_upgrade_info file print message upgrade done.

            People

              Unassigned Unassigned
              oli Oli Sennhauser
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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