Bug 1430755

Summary: net ads join can't create keytab when 'kerberos method' is set to use a keytab
Product: Red Hat Enterprise Linux 7 Reporter: ChunYu Wang <chunwang>
Component: sambaAssignee: Andreas Schneider <asn>
Status: CLOSED ERRATA QA Contact: Andrej Dzilský <adzilsky>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.4CC: adzilsky, asn, chunwang, dlavu, gdeschner, jarrpa, lslebodn, mniranja, rhack, yoyang
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: samba-4.6.0-5.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 18:21:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 3 Andreas Schneider 2017-03-10 10:31:37 UTC
I'm sorry, but I do not see how exactly this test calls 'net ads join' you need to provide more details. We also need to see the smb.conf and the default krb5.conf.

Comment 6 Andreas Schneider 2017-03-10 13:34:49 UTC
Can you run 'klist' after the kinit?

Comment 8 Andreas Schneider 2017-03-13 10:34:59 UTC
Can you run 'net ads join' with the option -d10 and upload the log level 10 output here?

To which Windows version do you try to join?


Thanks.

Comment 11 Andreas Schneider 2017-03-13 16:49:23 UTC
*** Bug 1431277 has been marked as a duplicate of this bug. ***

Comment 19 ChunYu Wang 2017-03-30 16:49:30 UTC
Test with same script logged in comment 0 shows this issue has been resolved on target samba version:

[root@hp-dl388g8-20 tools]# rpm -qa | grep samba-4
samba-4.6.0-5.el7.x86_64

[root@hp-dl388g8-20 tools]# uname -r
3.10.0-628.el7.x86_64
[root@hp-dl388g8-20 tools]# cat /etc/redhat-release 
Red Hat Enterprise Linux Workstation release 7.4 Beta (Maipo)

Thanks for your quick fix!

Comment 22 errata-xmlrpc 2017-08-01 18:21:34 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/RHSA-2017:1950