Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug with Gitlab Pipeline #26

Open
mbellahcene75 opened this issue Mar 31, 2022 · 1 comment
Open

Bug with Gitlab Pipeline #26

mbellahcene75 opened this issue Mar 31, 2022 · 1 comment

Comments

@mbellahcene75
Copy link

Hi
we have this error :
"credssp: Server did not response with a CredSSP token after step Credential exchange - actual ''", "unreachable": true
or
Server did not response with a CredSSP token after step Step 5. Delegate Credentials - actual ''

os serveur is windows 2019

when we use this type of Azure machine , no error : Standard_F8s_v2 ( VCPU = 8)

When we change the type machine Azure with : Standard_F16s_v2 or Standard_F32s_v2 ( VCPU = 16 or 32) --> ERROR CREEDSSP

if the server is windows 2012r2 whe have no problem
we have a fix --> change ansible_winrm_operation_timeout_sec 20 to 60 sec .
but its to long to execute ansible module action

thanks for you help

Ps sorry for my bad english.

@jborean93
Copy link
Owner

Hmm this is interesting, I'm unsure why setting ansible_winrm_operation_timeout_sec would affect this as it's used beyond authentication. It's also interesting that the machine type can also have a failure. The failure here is occurring right at the end of the CredSSP authentication which is when it sends your actual credentials to the host.

What I would do is check the Security event logs on the bad host and see the reason why it has rejected the the credentials. For example this is what I see when I manually send the wrong credentials.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants