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.

The WAL journaling mode does not work in sqlite 3.6.20-1 available at RHEL 6. 

WAL Journaling mode is absolutely required for the Data Tiering feature of Red Hat Gluster Storage on RHEL 6

It is required to upgrade sqlite version on RHEL 6.7 to sqlite 3.7 and above, which supports WAL journaling mode

*** This bug has been marked as a duplicate of bug 1265399 ***

(In reply to Dan Lambright from comment #3)
> 
> *** This bug has been marked as a duplicate of bug 1265399 ***

Why was this BZ on RHEL6 closed as a DUPLICATE of an upstream bug?!

Re-opening this BZ, and changing the summary to reflect the objective of this BZ on RHEL6

We have a a software workaround for this problem described in 1265399. It solves the data base lock problem, but because it still uses the old sqlite without WAL, performance is poor. Also, my understanding is we will not be able to get the newer sqlite on RHEL6 in any circumstances. If you know differently, Mr Cyriac, I would be greatly interested in hearing that. This bug should not be the NEW state. I would say it is resolved as WONTFIX if its not a duplicate.