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

[Question]: Azure DevOps Pipelines are failing at checkout task #4665

Closed
1 of 4 tasks
PhanindraReddyP opened this issue Feb 19, 2024 · 3 comments
Closed
1 of 4 tasks

Comments

@PhanindraReddyP
Copy link

Describe your question

Azure Pipelines are failing at default checkout task in all the agents in one of our self hosted agent machines with error "fatal: Cannot prompt because terminal prompts have been disabled."
We have another machine with couple of agents, and the pipelines are working fine there.

Versions

Version Dev19.M233.1 (AzureDevOps_M233_20240212.1)

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Operation system

No response

Version controll system

Git

Azure DevOps Server Version (if applicable)

No response

@aleksandrlevochkin
Copy link
Contributor

Hi @PhanindraReddyP this error may indicate an issue with authentication. Could you please verify that the tokens used on that machine are not expired/revoked.

@kirill-ivlev
Copy link
Contributor

Hi @PhanindraReddyP, unfortunately we didn't get any updates from your side,
Please feel free to re-open this issue if it is still bothering you.

@PhanindraReddyP
Copy link
Author

Hello @kirill-ivlev and @aleksandrlevochkin, I would like to re-open this case as we are facing this issue again
Aleksandr, it is not about the token, because it works when we try to clone in a different folder or different machine with the token.
Initially the error occurred in Feb 2024 and suddenly it got resolved somehow we dont know how.
But the same error coming up now. We tried the work arounds like changing the logon from the agent service properties from Network Service to Local Account and from Local account to Network Service.

Any help to resolve this would be greatly appreciated.

Thanks in advance.

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

No branches or pull requests

3 participants