Details

    Description

      We need to make sure that upgrades from 11.X.A to 11.Y.B (for Y >= 3) work seamlessly and automatically.

      Practically, the important cases are A=B=1 and A=B=2, with Y=X+1. Although, likely, allowing any natural numbers there will not require any additional code changes.

      CI should test that, we'll fix everything that makes these tests fail

      Attachments

        Issue Links

          Activity

            elenst Elena Stepanova added a comment - - edited

            In the old buildbot (if we still want to extend it):

            • for RPMs, we already have major-upgrade-server step which does that, although maybe we'll need to rename it to match the new vision. But of course it can't work seamlessly unless the old artificial limitation for doing that in RPMs is lifted or changed;
            • for DEBs, the step doing the same needs to be added (historically upgrade1/upgrade2 use a predefined old version), and hopefully it will work smoothly without code changes.

            In the new buildbot:

            The steps can of course be extended with additional checks which we want to run for such upgrades. They cannot be the same as in current minor upgrades (dependencies can change, so can plugin lists, requirements, etc.), but maybe a subset of those.

            elenst Elena Stepanova added a comment - - edited In the old buildbot (if we still want to extend it): for RPMs, we already have major-upgrade-server step which does that, although maybe we'll need to rename it to match the new vision. But of course it can't work seamlessly unless the old artificial limitation for doing that in RPMs is lifted or changed; for DEBs, the step doing the same needs to be added (historically upgrade1/upgrade2 use a predefined old version), and hopefully it will work smoothly without code changes. In the new buildbot: for RPMs, same as the old buildbot, the step is already in place https://buildbot.mariadb.org/#/builders/608/builds/411/steps/4/logs/stdio , but it also complies with the old limitations and removes the old server before installing the new one, which is not seamless; for DEBs, the step is also in place https://buildbot.mariadb.org/#/builders/597/builds/172/steps/3/logs/stdio , it doesn't seem to be working at the moment, but on unrelated infrastructural reasons. The steps can of course be extended with additional checks which we want to run for such upgrades. They cannot be the same as in current minor upgrades (dependencies can change, so can plugin lists, requirements, etc.), but maybe a subset of those.

            People

              elenst Elena Stepanova
              serg Sergei Golubchik
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.