Bug 2024248

Summary: realmd logs are duplicated
Product: Red Hat Enterprise Linux 8 Reporter: Nikhil Suryawanshi <nsuryawa>
Component: realmdAssignee: Sumit Bose <sbose>
Status: CLOSED ERRATA QA Contact: shridhar <sgadekar>
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.5CC: sbose, sgadekar
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: realmd-0.16.3-24.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-10 15:29:25 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:

Description Nikhil Suryawanshi 2021-11-17 16:54:16 UTC
Description of problem:

realmd logs are duplicated at the timing of joining/unjoining AD and can be seen in the output of #journalctl --no-pager -u realmd



Version-Release number of selected component (if applicable):

RHEL 8.5

How reproducible:

Every time

Steps to Reproduce:

1. Join  RHEL system to AD using #realm command

2. Execute #journalctl --no-pager -u realmd



Actual results:

#journalctl --no-pager -u realmd
.
.
.
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global systemd[1]: Starting Realm and Domain Configuration...
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: Loaded settings from: /usr/lib/realmd/realmd-defaults.conf /usr/lib/realmd/realmd-distro.conf
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: holding daemon: startup
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: starting service
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: connected to bus
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: released daemon: startup
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global systemd[1]: Started Realm and Domain Configuration.
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: claimed name on bus: org.freedesktop.realmd
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: client using service: :1.5271
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: holding daemon: :1.5271
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: Using 'r6130493.1206539' operation for method 'Discover' invocation on 'org.freedesktop.realmd.Provider' interface
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: Registered cancellable for operation 'r6130493.1206539'
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]:  * Resolving: _ldap._tcp.gsslab1.idm.global
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]:  * Resolving: _ldap._tcp.gsslab1.idm.global
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: No DNS record of the requested type for “_ldap._tcp.gsslab1.idm.global”
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]:  * Resolving: gsslab1.idm.global
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]:  * Resolving: gsslab1.idm.global
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: Resolving gsslab1.idm.global failed: No DNS record of the requested type for “_kerberos._udp.gsslab1.idm.global”
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: Resolving gsslab1.idm.global failed: No DNS record of the requested type for “_kerberos._tcp.gsslab1.idm.global”


Expected results:

#journalctl --no-pager -u realmd
.
.
.
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global systemd[1]: Starting Realm and Domain Configuration...
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: Loaded settings from: /usr/lib/realmd/realmd-defaults.conf /usr/lib/realmd/realmd-distro.conf
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: holding daemon: startup
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: starting service
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: connected to bus
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: released daemon: startup
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global systemd[1]: Started Realm and Domain Configuration.
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: claimed name on bus: org.freedesktop.realmd
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: client using service: :1.5271
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: holding daemon: :1.5271
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: Using 'r6130493.1206539' operation for method 'Discover' invocation on 'org.freedesktop.realmd.Provider' interface
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: Registered cancellable for operation 'r6130493.1206539'
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]:  * Resolving: _ldap._tcp.gsslab1.idm.global
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: No DNS record of the requested type for “_ldap._tcp.gsslab1.idm.global”
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]:  * Resolving: gsslab1.idm.global
Nov 03 02:57:46 sssdclient2.gsslab1.idm.global realmd[1206542]: Resolving gsslab1.idm.global failed: No DNS record of the requested type for “_kerberos._tcp.gsslab1.idm.global”

Additional info:

Comment 6 shridhar 2022-01-17 15:07:15 UTC
[root@ci-vm-10-0-137-42 tmp.MTZHwXEYm7]# rpm -q realmd
realmd-0.16.3-24.el8.x86_64


::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::   Test
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [ 10:04:31 ] :: [  BEGIN   ] :: Join computer to AD :: actually running 'realm join --use-ldaps --membership-software=adcli --verbose ad.baseos.qe'
 * Resolving: _ldap._tcp.ad.baseos.qe
 * Performing LDAP DSE lookup on: 10.37.152.14
 * Successfully discovered: ad.baseos.qe
 * Required files: /usr/sbin/oddjobd, /usr/libexec/oddjob/mkhomedir, /usr/sbin/sssd, /usr/sbin/adcli
 * Joining using a truncated netbios name: CI-VM-10-0-137-
 * LANG=C /usr/sbin/adcli join --verbose --domain ad.baseos.qe --domain-realm AD.BASEOS.QE --use-ldaps --domain-controller 10.37.152.14 --computer-name CI-VM-10-0-137- --login-type user --login-ccache=/var/cache/realmd/realm-ad-kerberos-PYWFG1
 * Using domain name: ad.baseos.qe
 * Using computer account name: CI-VM-10-0-137-
 * Using domain realm: ad.baseos.qe
 * Sending NetLogon ping to domain controller: 10.37.152.14
 * Received NetLogon info from: sec-ad1.ad.baseos.qe
 * Using LDAPS to connect to 10.37.152.14
 * Wrote out krb5.conf snippet to /var/cache/realmd/adcli-krb5-Grimxp/krb5.d/adcli-krb5-conf-bmt1Cn
 * Using GSSAPI for SASL bind
 * Looked up short domain name: AD
 * Looked up domain SID: S-1-5-21-3917357665-4280980005-1639201238
 * Using fully qualified name: ci-vm-10-0-137-42.hosted.upshift.rdu2.redhat.com
 * Using domain name: ad.baseos.qe
 * Using computer account name: CI-VM-10-0-137-
 * Using domain realm: ad.baseos.qe
 * Enrolling computer name: CI-VM-10-0-137-
 * Generated 120 character computer password
 * Using keytab: FILE:/etc/krb5.keytab
 * A computer account for CI-VM-10-0-137-$ does not exist
 * Found well known computer container at: CN=Computers,DC=ad,DC=baseos,DC=qe
 * Calculated computer account: CN=CI-VM-10-0-137-,CN=Computers,DC=ad,DC=baseos,DC=qe
 * Encryption type [16] not permitted.
 * Encryption type [23] not permitted.
 * Encryption type [3] not permitted.
 * Encryption type [1] not permitted.
 * Created computer account: CN=CI-VM-10-0-137-,CN=Computers,DC=ad,DC=baseos,DC=qe
 * Sending NetLogon ping to domain controller: 10.37.152.14
 * Received NetLogon info from: sec-ad1.ad.baseos.qe
 * Set computer password
 * Retrieved kvno '2' for computer account in directory: CN=CI-VM-10-0-137-,CN=Computers,DC=ad,DC=baseos,DC=qe
 * Checking RestrictedKrbHost/ci-vm-10-0-137-42.hosted.upshift.rdu2.redhat.com
 *    Added RestrictedKrbHost/ci-vm-10-0-137-42.hosted.upshift.rdu2.redhat.com
 * Checking RestrictedKrbHost/CI-VM-10-0-137-
 *    Added RestrictedKrbHost/CI-VM-10-0-137-
 * Checking host/ci-vm-10-0-137-42.hosted.upshift.rdu2.redhat.com
 *    Added host/ci-vm-10-0-137-42.hosted.upshift.rdu2.redhat.com
 * Checking host/CI-VM-10-0-137-
 *    Added host/CI-VM-10-0-137-
 * Discovered which keytab salt to use
 * Added the entries to the keytab: CI-VM-10-0-137-$@AD.BASEOS.QE: FILE:/etc/krb5.keytab
 * Added the entries to the keytab: host/CI-VM-10-0-137-.QE: FILE:/etc/krb5.keytab
 * Added the entries to the keytab: host/ci-vm-10-0-137-42.hosted.upshift.rdu2.redhat.com.QE: FILE:/etc/krb5.keytab
 * Added the entries to the keytab: RestrictedKrbHost/CI-VM-10-0-137-.QE: FILE:/etc/krb5.keytab
 * Added the entries to the keytab: RestrictedKrbHost/ci-vm-10-0-137-42.hosted.upshift.rdu2.redhat.com.QE: FILE:/etc/krb5.keytab
 ! Failed to update Kerberos configuration, not fatal, please check manually: Setting attribute standard::type not supported
 * /usr/bin/systemctl enable sssd.service
 * /usr/bin/systemctl restart sssd.service
 * /usr/bin/sh -c /usr/bin/authselect select sssd with-mkhomedir --force && /usr/bin/systemctl enable oddjobd.service && /usr/bin/systemctl start oddjobd.service
Backup stored at /var/lib/authselect/backups/2022-01-17-15-04-43.HLNokW
Profile "sssd" was selected.
The following nsswitch maps are overwritten by the profile:
- passwd
- group
- netgroup
- automount
- services

Make sure that SSSD service is configured and enabled. See SSSD documentation for more information.
 
- with-mkhomedir is selected, make sure pam_oddjob_mkhomedir module
  is present and oddjobd service is enabled and active
  - systemctl enable --now oddjobd.service

Created symlink /etc/systemd/system/multi-user.target.wants/oddjobd.service → /usr/lib/systemd/system/oddjobd.service.
 * Successfully enrolled machine in realm


Above log output shows no lines are duplicated.
marking verified.

Comment 8 errata-xmlrpc 2022-05-10 15:29:25 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 (realmd 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/RHBA-2022:2088