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.
Bug 1677373 - bind-dyndb-ldap does not compile after bind 9.11 rebase
Summary: bind-dyndb-ldap does not compile after bind 9.11 rebase
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: bind-dyndb-ldap
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Alexander Bokovoy
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On: bind911_rebase_el7
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-14 16:29 UTC by Petr Menšík
Modified: 2019-08-06 13:04 UTC (History)
3 users (show)

Fixed In Version: bind-dyndb-ldap-11.1-6.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:04:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2195 0 None None None 2019-08-06 13:04:03 UTC

Comment 3 Nikhil Dehadrai 2019-06-12 08:24:46 UTC 
ipa-server-4.6.5-9.el7.x86_64
bind-dyndb-ldap-11.1-6.el7.x86_64


Verified the bug on the basis of following observations:
1. Installation of IPA-Master using '--setup-dns' is successful

2019-06-11T16:07:20+0000 [ipa_pytests.qe_class.QeHost.master.ParamikoTransport] INFO RUN ['/usr/sbin/ipa-server-install', '--setup-dns', '--forwarder', '10.11.5.19', '--domain', 'testrealm.test', '--realm', 'TESTREALM.TEST', '--admin-password', 'Secret123', '--ds-password', 'Secret123', '-U', '--reverse-zone', '150.0.10.in-addr.arpa.', '--allow-zone-overlap', '--setup-kra', '--domain-level=0']
2019-06-11T16:07:20+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG RUN ['/usr/sbin/ipa-server-install', '--setup-dns', '--forwarder', '10.11.5.19', '--domain', 'testrealm.test', '--realm', 'TESTREALM.TEST', '--admin-password', 'Secret123', '--ds-password', 'Secret123', '-U', '--reverse-zone', '150.0.10.in-addr.arpa.', '--allow-zone-overlap', '--setup-kra', '--domain-level=0']


2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG Setup complete
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG Next steps:
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 	1. You must make sure these network ports are open:
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 		TCP Ports:
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 		  * 80, 443: HTTP/HTTPS
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 		  * 389, 636: LDAP/LDAPS
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 		  * 88, 464: kerberos
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 		  * 53: bind
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 		UDP Ports:
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 		  * 88, 464: kerberos
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 		  * 53: bind
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 		  * 123: ntp
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 	2. You can now obtain a kerberos ticket using the command: 'kinit admin'
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 	   This ticket will allow you to use the IPA tools (e.g., ipa user-add)
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 	   and the web user interface.
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG 
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG Be sure to back up the CA certificates stored in /root/cacert.p12
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG These files are required to create replicas. The password for these
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG files is the Directory Manager password
2019-06-11T16:14:42+0000 [paramiko.transport] DEBUG [chan 14] EOF received (14)
2019-06-11T16:14:42+0000 [paramiko.transport] DEBUG [chan 14] EOF sent (14)
2019-06-11T16:14:42+0000 [ipa_pytests.qe_class.QeHost.master.cmd14] DEBUG Exit code: 0


2. Installation of IPA-Replica using '--setup-dns' is successful


Thus on the basis of above observations, marking the status of bug to 'VERIFIED'
Comment 6 errata-xmlrpc 2019-08-06 13:04:01 UTC 
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-2019:2195
Note You need to log in before you can comment on or make changes to this bug.