-
Notifications
You must be signed in to change notification settings - Fork 15
Description
ad-child provision enrollment fails because it's still loading the "Group Policy Client", once that is loaded if you execute again the command it finishes correctly.
How to reproduce:
$ ./sssd-test-suite up client ad ad-child
$ ./sssd-test-suite provision enroll client ad ad-child
It fails with the following error:
fatal: [client]: FAILED! => {"changed": true, "cmd": "current_hostname=hostname\nhostname 'child.client.vm' || exit $?\necho vagrant | realm join child.ad.vm || exit $?\nhostname $current_hostname || exit $?\ntouch /etc/sssd/ad_child_enrolled || exit $?\n", "delta": "0:00:00.014015", "end": "2020-06-08 08:41:40.222281", "msg": "non-zero return code", "rc": 1, "start": "2020-06-08 08:41:40.208266", "stderr": "realm: Cannot join this realm", "stderr_lines": ["realm: Cannot join this realm"], "stdout": "", "stdout_lines": []}
In this moment if you open a rdesktop session with ad-child you'll find that "Group Policy Client" is still loading and it's not possible to login. Once that is loaded execute again:
$ ./sssd-test-suite provision enroll client ad ad-child
This time it succeeds.
Setup:
- Last master branch (7d2273a)
- Lenovo T490s with Fedora 32