RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
main.events_bugs                         [ fail ]

        Test ended at 2020-01-02 20:19:36

 

CURRENT_TEST: main.events_bugs

mysqltest: At line 1032: query 'CREATE EVENT e1 ON SCHEDULE AT '2020-01-01 00:00:00' DO SET @a = 1' succeeded - should have failed with errno 1290...

 

The result from queries just before the failure was:

< snip >

SET GLOBAL event_scheduler= OFF;

DROP EVENT bug28641;

Version-Release number of selected component (if applicable):mariadb-5.5.65-1.el7


How reproducible: 100%


Steps to Reproduce:
1. Attempt to rebuild in 2020
2.
3.

Actual results:
Test case expects dates before 2020

Expected results:
builds

Additional info:

https://jira.mariadb.org/browse/MDEV-21416

https://github.com/MariaDB/server/commit/3c94c5b8fab0c3bb0febe62d72b89bc8d51c3932

Thank you for the report.

Unfortunatelly, this is a recurring issue for MariaDB.

I'll try to add this fix next time we will make an update for MariaDB.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: mariadb security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4026