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]: ##[error]Failed to download or parse release-index.json with error: {} #20362

Closed
4 of 7 tasks
ktran1005 opened this issue Aug 28, 2024 · 3 comments
Closed
4 of 7 tasks
Labels
Area: ABTT Akvelon Build Tasks Team area of work bug stale

Comments

@ktran1005
Copy link

ktran1005 commented Aug 28, 2024

New issue checklist

Task name

UseDotNet@2

Task version

No response

Issue Description

I am facing this error ( ##[error]Failed to download or parse release-index.json with error: {} ) in one of my Azure pipelines. It did not happen often. I wonder if anyone knows how to fix this issue?

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)

Azure DevOps Server Version (if applicable)

Azure DevOps Server 2022

Operation system

Windows 11

Relevant log output

##[error]Failed to download or parse release-index.json with error: {}

Full task logs with system.debug enabled

 [REPLACE THIS WITH YOUR INFORMATION] 

Repro steps

No response

@ktran1005 ktran1005 added the bug label Aug 28, 2024
@v-schhabra v-schhabra added Area: ABTT Akvelon Build Tasks Team area of work and removed Area: Release labels Aug 29, 2024
@DenisNikulin5
Copy link
Contributor

Hi @ktran1005
It's either a network error or an error on dotnet blob storage side.

How often do you face the issue?

@ktran1005
Copy link
Author

ktran1005 commented Aug 30, 2024

Hi @DenisNikulin5,

I have a pipeline that’s scheduled to run every night. The last time my pipeline failed due to this error was last Wed and couple times last month. I think it didn’t happen a lot but sometimes it does happen randomly . I saw some people suggested to rerun the pipeline to fix this issue. Do you think that’s the only solution? Thanks

Copy link

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: ABTT Akvelon Build Tasks Team area of work bug stale
Projects
None yet
Development

No branches or pull requests

3 participants