Details

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

    Description

      Our kb on timezones for Windows does not provide a solution for 10.6+ because the MySQL timezones are incompatible (Offset is a keyword in MariaDB only).

      Because we now have a mirror service can we generate the timezones sql files here for distribution.

      Suggestion:

      A cron job that runs:

      $ docker pull docker.io/library/mariadb:10.6
      $ docker run --rm docker.io/library/mariadb:10.6 mariadb-tzinfo-to-sql /usr/share/zoneinfo > zoneinfo.sql
      

      The mariadb image is semi frequently updated as its ubuntu base image is also updated, hence bringing with it updated /usr/share/zoneinfo. Also as we do releases and the mariadb-tzinfo-to-sql changes we get that change automatically.

      Attachments

        Issue Links

          Activity

            danblack Daniel Black added a comment - https://gitlab.com/mariadb/sysadmin/-/merge_requests/29

            Thanks danblack. This has been merged and rewritten a bit (improve logging mechanism and error handling mainly and adapt PATH for production).
            A routine has been deployed on the mirror machine and zoneinfo.sql is now generated everyday in /zoneinfo/zoneinfo.zip. I need to sync now with dbart in order to decide how we can push this on osuosl and netcologne (and every mirror will pull from there).

            faust Faustin Lammler added a comment - Thanks danblack . This has been merged and rewritten a bit (improve logging mechanism and error handling mainly and adapt PATH for production). A routine has been deployed on the mirror machine and zoneinfo.sql is now generated everyday in /zoneinfo/zoneinfo.zip. I need to sync now with dbart in order to decide how we can push this on osuosl and netcologne (and every mirror will pull from there).
            faust Faustin Lammler added a comment - - edited

            danblack the zoneinfo file is now replicated on the fi mirror (under our control), this is the only mirror serving the file until we put it on netcologne and osuosl with dbart.
            https://mirror.mariadb.org/zoneinfo/zoneinfo.zip?mirrorlist

            Next time the docker container is updated, I would like to verify that the whole process is working good. I switch the script to using podman instead of docker and I hit a nice bug in conman, so I have added another check. You can probably have a look when you have time, it's almost finished I guess:
            https://gitlab.com/mariadb/sysadmin/-/blob/deploy-tzdata/ansible/zoneinfo/generate_zoneinfo.sh

            faust Faustin Lammler added a comment - - edited danblack the zoneinfo file is now replicated on the fi mirror (under our control), this is the only mirror serving the file until we put it on netcologne and osuosl with dbart. https://mirror.mariadb.org/zoneinfo/zoneinfo.zip?mirrorlist Next time the docker container is updated, I would like to verify that the whole process is working good. I switch the script to using podman instead of docker and I hit a nice bug in conman, so I have added another check . You can probably have a look when you have time, it's almost finished I guess: https://gitlab.com/mariadb/sysadmin/-/blob/deploy-tzdata/ansible/zoneinfo/generate_zoneinfo.sh
            danblack Daniel Black added a comment -

            Looks good. Thanks.

            Welcome to the use of podman too. (I was too, just had docker=podman alias, and a newer version that avoided the bug).

            It occurred to me maybe zonedata_old.zip is a better filename for the old version.

            Production scripts in home directories doesn't look great either.

            I'm really happy we have a solution now.

            danblack Daniel Black added a comment - Looks good. Thanks. Welcome to the use of podman too. (I was too, just had docker=podman alias, and a newer version that avoided the bug). It occurred to me maybe zonedata_old.zip is a better filename for the old version. Production scripts in home directories doesn't look great either. I'm really happy we have a solution now.

            > It occurred to me maybe zonedata_old.zip is a better filename for the old version.

            You mean zoneinfo_old.zip, should we keep it then?
            It's not the case for the moment.

            > Production scripts in home directories doesn't look great either.

            Yep, fully agree on that, it's already on my TODO list to add a proper sync user for the mirror machine but it will have to wait a bit since it depends on other task.

            faust Faustin Lammler added a comment - > It occurred to me maybe zonedata_old.zip is a better filename for the old version. You mean zoneinfo_old.zip, should we keep it then? It's not the case for the moment. > Production scripts in home directories doesn't look great either. Yep, fully agree on that, it's already on my TODO list to add a proper sync user for the mirror machine but it will have to wait a bit since it depends on other task.

            People

              faust Faustin Lammler
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 0.75d
                  0.75d