This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2218973 - perl-DBD-Mysql is returning 0 in amavisd for some mysql columns.
Summary: perl-DBD-Mysql is returning 0 in amavisd for some mysql columns.
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: perl-DBD-MySQL
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: perl-maint-list
QA Contact: RHEL CS Apps Subsystem QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-30 18:22 UTC by Nathan Coulson
Modified: 2023-09-20 16:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-20 16:33:01 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
Patch from https://github.com/perl5-dbi/DBD-mysql/issues/78 for EL9 (949 bytes, patch)
2023-06-30 18:22 UTC, Nathan Coulson 		no flags Details | Diff
Patch from https://github.com/perl5-dbi/DBD-mysql/issues/78 for EL8 (949 bytes, patch)
2023-06-30 18:24 UTC, Nathan Coulson 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-5546 0 None Migrated None 2023-09-20 16:32:57 UTC
Red Hat Issue Tracker RHELPLAN-161372 0 None None None 2023-06-30 18:23:20 UTC

Description Nathan Coulson 2023-06-30 18:22:58 UTC 
Created attachment 1973447 [details]
Patch from https://github.com/perl5-dbi/DBD-mysql/issues/78 for EL9

Description of problem:
Cross Posting from https://bugzilla.redhat.com/show_bug.cgi?id=2218970, but RHEL 9.2 and 8.8 seem to be affected by https://github.com/perl5-dbi/DBD-mysql/issues/78.

In amavisd, When using a mariadb database for looking up the tagged threshold, it always returns 0 for values obtained from the database

Version-Release number of selected component (if applicable):
* EL9
** amavis 2.13.0-4.el9
** perl-DBD-MySQL 4.050-13
* EL8
** amavis 2.12.1-5.el8
** perl-DBD-MySQL 4.046-3

How reproducible:
Always


Steps to Reproduce:
1.Install Amavis
2. Configure @lookup_sql_dsn to point at a mysql database (Schema at https://github.com/srault95/amavisd-new/blob/master/README_FILES/README.sql-mysql)
3. Setup a policy with spam_tag level set to a value like 5,

Actual results:
Jun 27 13:43:25 aggelos-front4 amavis[5795]: (05795-01) spam-tag, <REDACTED> -> <REDACTED>, Yes, score=3.001 tagged_above=-100 required=0 tests=[ALL_TRUSTED=-1, BAYES_99=3.5, BAYES_999=0.5, TVD_SPACE_RATIO=0.001] autolearn=no autolearn_force=no
* required = 0, when it should be 5

Expected results:
Jun 27 15:10:43 aggelos-front4 amavis[147269]: (147269-01) spam-tag, <REDACTED> -> <REDACTED>, No, score=3.001 tagged_above=-100 required=5 tests=[ALL_TRUSTED=-1, BAYES_99=3.5, BAYES_999=0.5, TVD_SPACE_RATIO=0.001] autolearn=no autolearn_force=no


Additional info:
I believe this is due to https://github.com/perl5-dbi/DBD-mysql/issues/78, which seems to be committed to perl-DBD-MySQL master, but not in the 4.046 or 4.050 release

I patched the DBD-MySQL-4.0.50 (obtained from the ticket) provided by AlmaLinux 9 with the attached patch, and this gives me the expected results.
Comment 1 Nathan Coulson 2023-06-30 18:24:17 UTC 
Created attachment 1973448 [details]
Patch from https://github.com/perl5-dbi/DBD-mysql/issues/78 for EL8
Comment 2 Michal Josef Spacek 2023-07-24 19:21:01 UTC 
This fix is very problematic. When you read full thread in https://github.com/perl5-dbi/DBD-mysql/issues/78, you could see that fix will broke data in some situations. I thinks that this kind of changes must be clearly define in some new release, but fix of the old release isn't possible. I believe.
Comment 3 Michal Josef Spacek 2023-09-13 08:22:10 UTC 
We can't fix it now. Because of side effects.

We are in a situation where we don't have a precise reproducer for the issue. We have a plan to find it.
After this, we could talk about the issue more precisely.
Comment 4 RHEL Program Management 2023-09-20 16:30:45 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5 RHEL Program Management 2023-09-20 16:33:01 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.