| Summary: | Regression with jabberd 2.3.1 and postgresql | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Solomon Peachy <pizza> |
| Component: | jabberd | Assignee: | Adrian Reber <adrian> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | adrian, dmaphy |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-04 12:53:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Thanks for your testing and upstream bug report. I will apply the upstream patch soon. |
Description of problem: Jabberd 2.3.0 and newer introduced a regression when using a postgresql backend. Version-Release number of selected component (if applicable): jabberd-2.3.1-1 How reproducible: 100%. Upgrade an existing jabberd-2.2.17 installation (configured to use a postgresql backend) with the 2.3.1-1 rawhide package, and watch it break: (jabberd log) Dec 2 13:53:27 stuffed jabberd/sm[16886]: pgsql: sql insert failed: ERROR: value "140116104107814" is out of range for type integer (Database log) ERROR: value "140116104107814" is out of range for type integer at character 191 STATEMENT: INSERT INTO "status" ( "collection-owner", "object-sequence", "status", "show", "last-login", "xml", "last-logout" ) VALUES ( 'EMAILCUTOUT', nextval('object-sequence'), 'online', '', '140116104107814', 'NAD', '1' ); Both '140116104107814' and '140116104107539' are completely bogus values. In comparison, the values stored in the database for that user are '1386008295' and '1386010131', respectively. Upstream bug reported (and a possible fix identified) here: https://github.com/jabberd2/jabberd2/issues/48