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.

This bug is created as a clone of upstream ticket:
https://pagure.io/bind-dyndb-ldap/issue/172

### Problem
#### What does not work as expected?
When `server_id` is not specified in the configuration file, bind-dyndb-ldap will crash when it's trying to parse the configuration:

```
named-pkcs11[19546]: cannot parse settings for 'named.conf for database dns-ldap': not found
named-pkcs11[19546]: dynamic database 'dns-ldap' configuration failed: not found
named-pkcs11[19546]: loading configuration: not found
named-pkcs11[19546]: exiting (due to fatal error)
```

This is most likely a regression caused by the API changes. The bug is *not* present for bind-dyndb-ldap-10.1-1.fc24.x86_64.

### Steps to Reproduce

* remove `server_id` from `/etc/named.conf`
* `systemctl restart named-pkcs11`

### Environment
* Plugin version: bind-dyndb-ldap-11.1-1.fc27.x86_64

* Version of BIND: bind-9.11.0-6.P2.fc25.x86_64

* Do you use bind-dyndb-ldap as part of FreeIPA installation? 
This issue happens when using bind-dyndb-ldap standalone, because FreeIPA does specify `server_id` in the default template.

### Workaround

* specify `server_Id "";` in `/etc/named.conf`
* `systemctl start named-pkcs11`

Fixed upstream

master

- https://pagure.io/bind-dyndb-ldap/c/41461fc444170ffd9b5459e2f0b2480f3288cc1d

ipa server version: ipa-server-4.5.0-9.el7.x86_64
bind-dyndb-ldap version: bind-dyndb-ldap-11.1-3.el7.x86_64

Tested the bug with following observations:
1. IPA upgrade from RHEL 7.2.z to RHEL 7.4 is successful.
2. IPA upgrade from RHEL 7.1.z to RHEL 7.4 FAILS.

Thus from above observation, changing the status of bug to "ASSIGNED".

The IPA upgrade from RHEL 7.1.z is a different issue, see bug 1447284.

This bug is fixed, otherwise the upgrade from 7.2.z would fail as well. I'm changing state back to ON_QA.

Based on observations in above comment#7 and Comment#10, marking the status of bug to "VERIFIED".

For the IPA upgrade issue wth RHEL 7.1.z to RHEL 7.4, a separate bug BZ#1447284 is logged.

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://access.redhat.com/errata/RHBA-2017:2120