verified with following data:
---------------------------------------------
previous version:
]# rpm -q adcli
adcli-0.8.2-3.el8.x86_64
]# man adcli |col -b| sed -n '/UPDATING THE MACHINE ACCOUNT PASSWORD AND OTHER ATTRIBUTES/,/TESTING IF THE MACHINE ACCOUNT PASSWORD IS VALID/p'|sed -n '/--add-samba-data/,/ --samba-data-tool/p'
--add-samba-data
After a successful join add the domain SID and the machine account password to the Samba specific
databases by calling Samba's net utility.
Please note that Samba's net requires some settings in smb.conf to create the database entries
correctly. Most important here is currently the workgroup option, see smb.conf(5) for details.
--samba-data-tool=/path/to/net
[root@ci-vm-10-0-138- tmp.jQicch9rqm]#
-------------------------------------
Latest version:
]# rpm -q adcli
adcli-0.8.2-4.el8.x86_64
[root@ci-vm-10-0-138- tmp.CF2qH3lanV]# man adcli |col -b| sed -n '/UPDATING THE MACHINE ACCOUNT PASSWORD AND OTHER ATTRIBUTES/,/TESTING IF THE MACHINE ACCOUNT PASSWORD IS VALID/p'|sed -n '/--add-samba-data/,/ --samba-data-tool/p'
--add-samba-data
After a successful join add the domain SID and the machine account password to the Samba specific
databases by calling Samba's net utility.
Please note that Samba's net requires some settings in smb.conf to create the database entries
correctly. Most important here is currently the workgroup option, see smb.conf(5) for details.
Note that if the machine account password is not older than 30 days, you have to pass
--computer-password-lifetime=0 to force the update.
--samba-data-tool=/path/to/net
[root@ci-vm-10-0-138- tmp.CF2qH3lanV]#
-------------------------------------------------------------------
Latest version contains updated line about machine account password lifetime.
Marking verified.
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-2020:1874