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:

In RHEL 6 this was in httpd.conf by default:

#
# WebDAV module configuration section.
#
<IfModule mod_dav_fs.c>
 # Location of the WEBDav lock database.
 DAVLockDB /var/lib/dav/lockdb
</IfModule>

this section is missing in RHEL 7 httpd.conf by default. Thus you get:

A lock database was not specified with the DAVLockDB directive. One must be specified to use the locking functionality.

in the httpd error log when you try to use WebDAV locking.

Version-Release number of selected component (if applicable):

httpd-2.4.6-18.el7

How reproducible:

Always

Steps to Reproduce:
1. install httpd
2. enable WebDAV
3. try to us something that needs WebDAV locking, see error in httpd log files

Actual results:

WebDAV locking fails to work

Expected results:

WebDAV locking works by default (like it did in RHEL 6)

Additional info:

We should patch this upstream to make the default path hard-coded in mod_dav_fs, or at least a config-time option for that.

Created attachment 1003779 [details]
proposed patch

Add davlockdb to config.layout.

Ah sorry I thought this had already gone out in 7.1.x, my mistake. It's not letting me reopen it, grrr.

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, 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://rhn.redhat.com/errata/RHBA-2015-2194.html