Bug 1458913

Description of problem:

The RHEL 7.4 beta includes gssproxy-0.7.0-3.el7, which includes the ability to have multiple configuration files.

Unfortunately, this version of gssproxy will also silently die at startup if the same section is defined more than once in any configuration file.

To make this worse, gssproxy-0.7.0-3.el7 includes a new /etc/gssproxy/99-nfs-client.conf file, which includes a [service/nfs-client] section definition.

This means that for any site that is already using gssproxy on NFSv4 clients, and has thus already has a [service/nfs-client] section in /etc/gssproxy.conf, upgrading to gssproxy-0.7.0-3.el7 will cause gssproxy to stop working on that host.

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

gssproxy-0.7.0-3.el7

How reproducible:

Replicate the contents of /etc/gssproxy/99-nfs-client.conf in the /etc/gssproxy.conf file.

Actual results:

gssproxy will silently die at startup without logging any error message whatsoever, even if debugging is enabled.

Expected results:

gssproxy should emit a warning that it is ignoring the duplicate [service/nfs-client] section definition, but still start up successfully.

Additional info:

While permitting multiple gssproxy configuration files is a welcome feature, the presence of multiple configuration files increases the chances of gssproxy encountering duplicate section definitions.

For that reason, gssproxy *must* cope reasonably when it encounters duplicate section definition. And "silently dying without logging anything whatsoever" is not a reasonable way to cope with duplicate section definitions.