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.

It looks like this bug appeared again.
The symptoms are exactly the same as below; the samba version is:
samba-4.2.3-6.el7
but it was reproduced also with
samba-4.2.2-1.el7
The last version where the issue is not appearing is:
samba-4.1.12-22.el7

See the original bug for more details and for the reproducer.

+++ This bug was initially created as a clone of Bug #1172089 +++

Description of problem:
samba join to samba domain doesn't work

Failed to join domain: Machine is a Domain Controller
:: [   FAIL   ] :: Command 'net join --domain QAB3QGC -U nbusr%nbusr123' (Expected 0, got 255)

It is a regression, the same use case passed with samba-4.1.12-3.el7

Version-Release number of selected component (if applicable):
samba-4.1.12-4.el7

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
Failed to join domain: Machine is a Domain Controller
:: [   FAIL   ] :: Command 'net join --domain QAB3QGC -U nbusr%nbusr123' (Expected 0, got 255)

Expected results:
Joined domain QAB3QGC.
:: [   PASS   ] :: Command 'net join --domain QAB3QGC -U nbusr%nbusr123' (Expected 0, got 0)

What is the output of 'testparm -s' on the machine.

Can you run 'net ads join' with -d10 and post the output?

QA_ACK+

You have a AD DC and the smb.conf doesn't have the realm set for the AD DC ...

Well, you are trying to join a PDC (NT4-style domain controller) do and AD DC. You can't join a domain controller as a member server ...

What are you trying to test?

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.

(In reply to Andreas Schneider from comment #8)
> What are you trying to test?

Actually freeradius and samba integration, but for the purpose of this test this join is not needed. It was just added there for no particular reason and since it started to fail I reported it. I thought it is a sane operation, especially as it was already once reported in bug 1172089. The test was already fixed. Thanks for clarifying this and sorry for the noise.