Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionKonstantin Shalygin
2022-07-19 08:10:22 UTC
Description of problem:
ctdb should have dependency for package "samba-winbind-clients", for properly working "49.winbind" script
Version-Release number of selected component (if applicable): 4.16.2
How reproducible:
Steps to Reproduce:
1. Install Samba & CTDB
2. Configure Samba & CTDB
3. Enable ctdb scripts:
ctdb event script enable 10.interface
ctdb event script enable 49.winbind
ctdb event script enable 50.samba
4. systemctl start ctdb
Actual results:
CTDB dead loop
Jul 18 22:56:45 ctdb-test1.domain.local ctdbd[4037]: ctdb_recheck_persistent_health: OK[0] FAIL[0]
Jul 18 22:56:45 ctdb-test1.domain.local ctdbd[4037]: Running the "startup" event.
Jul 18 22:56:47 ctdb-test1.domain.local ctdb-eventd[4039]: 49.winbind: Redirecting to /bin/systemctl start winbind.service
Jul 18 22:56:50 ctdb-test1.domain.local ctdb-eventd[4039]: 50.samba: Redirecting to /bin/systemctl start smb.service
Jul 18 22:56:50 ctdb-test1.domain.local ctdbd[4037]: startup event OK - enabling monitoring
Jul 18 22:56:50 ctdb-test1.domain.local ctdbd[4037]: Set runstate to RUNNING (5)
Jul 18 22:56:52 ctdb-test1.domain.local ctdb-eventd[4039]: 49.winbind: ERROR: wbinfo -p returned error
Jul 18 22:56:52 ctdb-test1.domain.local ctdb-eventd[4039]: 49.winbind: /etc/ctdb/events/legacy/49.winbind.script: line 47: wbinfo: command not found
Jul 18 22:56:52 ctdb-test1.domain.local ctdb-eventd[4039]: monitor event failed
Jul 18 22:56:54 ctdb-test1.domain.local ctdb-eventd[4039]: 49.winbind: ERROR: wbinfo -p returned error
Jul 18 22:56:54 ctdb-test1.domain.local ctdb-eventd[4039]: 49.winbind: /etc/ctdb/events/legacy/49.winbind.script: line 47: wbinfo: command not found
Jul 18 22:56:54 ctdb-test1.domain.local ctdb-eventd[4039]: monitor event failed
Jul 18 22:56:58 ctdb-test1.domain.local ctdb-eventd[4039]: 49.winbind: ERROR: wbinfo -p returned error
Jul 18 22:56:58 ctdb-test1.domain.local ctdb-eventd[4039]: 49.winbind: /etc/ctdb/events/legacy/49.winbind.script: line 47: wbinfo: command not found
Jul 18 22:56:58 ctdb-test1.domain.local ctdb-eventd[4039]: monitor event failed
Expected results:
CTDB cluster started & up
Additional info:
dnf install samba-winbind-clients resolves this problem
Comment 1Guenther Deschner
2022-07-27 09:47:42 UTC
Hi Konstantin,
if we start adding this dependency, we would need to add a whole list of other dependencies as well. For example the 50.samba script requires at least testparm, 00.ctdb requires tdbtool/tdbdump, etc. We would need to create a dependency to samba-client-tools, tdb-tools and many other packages then for ctdb - which we tend to avoid.
As long as we don't enable any event scripts (as you did for the reproducer) during package install, I believe we should not add all the potential dependencies to ctdb right now.
Comment 2Konstantin Shalygin
2022-07-27 09:57:42 UTC
Hi Guenther,
I, As an administrator, when I install packages expect them to work. After all, when you install the "grep" package, you expect it to work, and you don’t go to install "glibc" after this, right? Can't determine, why ctdb is an exclusion.
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 (Low: samba security, bug fix, and enhancement update), 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/RHSA-2023:2987