You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Fedora 34 I am trying to setup sssd-test-suite with AD and AD child for direct integration, I am running:
$ ./sssd-test-suite provision enroll child ad
This works fine, then I run and get this error about renaming:
$ ./sssd-test-suite provision enroll ad-child
...
<snip>
...
==> ad-child: Machine booted and ready!
==> ad-child: Setting hostname...
==> ad-child: Removing domain...
==> ad-child: Deleting the machine folder
Renaming the Windows guest failed. Most often this is because you've
specified a FQDN instead of just a host name.
Ensure the new guest name is properly formatted. Standard names may
contain letters (a-z, A-Z), numbers (0-9), and hyphens (-), but no
spaces or periods (.). The name may not consist entirely of digits.
[sssd-test-suite] [enroll] ERROR ShellCommandError: Command returned non-zero status code: 1
[sssd-test-suite] [enroll] [2/2] Enroll Machines (skipped on error)
[sssd-test-suite] [enroll] Finished with error ShellCommandError: Command returned non-zero status code: 1
[sssd-test-suite] The following command exited with: 1
[sssd-test-suite] [shell] Working directory: /home/justin/github/sssd-test-suite
[sssd-test-suite] [shell] Environment: VAGRANT_CWD='/home/justin/github/sssd-test-suite' SSSD_TEST_SUITE_CONFIG='/home/justin/github/sssd-test-suite/config.json'
[sssd-test-suite] [shell] Command: ['vagrant', 'up', 'ad-child']
I see the same error if I try running ./sssd-test-suite provision enroll client ad ad-child
The text was updated successfully, but these errors were encountered:
On Fedora 34 I am trying to setup sssd-test-suite with AD and AD child for direct integration, I am running:
This works fine, then I run and get this error about renaming:
I see the same error if I try running
./sssd-test-suite provision enroll client ad ad-child
The text was updated successfully, but these errors were encountered: