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

(AZCopy10) Source location no longer working #2611

Closed
2 tasks done
denyos opened this issue Jan 9, 2025 · 5 comments
Closed
2 tasks done

(AZCopy10) Source location no longer working #2611

denyos opened this issue Jan 9, 2025 · 5 comments
Labels

Comments

@denyos
Copy link

denyos commented Jan 9, 2025

Checklist

  • I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.
  • I have verified that this is happening in the latest available version of the package.

Chocolatey Version

2.4.1

Chocolatey License

None

Package Version

10.27.1

Current Behaviour

AzCopy10 is installed via chocolateyInstall.ps1

It is referencing a download location from azureedge that is no longer working:
https://azcopyvnext.azureedge.net/releases/release-10.27.1-20241113/azcopy_windows_amd64_10.27.1.zip

<Error>
<Code>PublicAccessNotPermitted</Code>
<Message>Public access is not permitted on this storage account. RequestId:ae528e71-b01e-0043-697a-620eb4000000 Time:2025-01-09T09:41:33.0974465Z</Message>
</Error>

Part of our azure pipeline in which we try to install AZCopy:

    azure-arm.image: Attempt to get headers for https://azcopyvnext.azureedge.net/releases/release-10.27.1-20241113/azcopy_windows_amd64_10.27.1.zip failed.
    azure-arm.image:   The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://azcopyvnext.azureedge.net/releases/release-10.27.1-20241113/azcopy_windows_amd64_10.27.1.zip'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (409) Conflict."
    azure-arm.image: Downloading azcopy10 64 bit
    azure-arm.image:   from 'https://azcopyvnext.azureedge.net/releases/release-10.27.1-20241113/azcopy_windows_amd64_10.27.1.zip'
    azure-arm.image: ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://azcopyvnext.azureedge.net/releases/release-10.27.1-20241113/azcopy_windows_amd64_10.27.1.zip'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (409) Conflict."
    azure-arm.image: This package is likely not broken for licensed users - see https://docs.chocolatey.org/en-us/features/private-cdn.
    azure-arm.image: The install of azcopy10 was NOT successful.

This seems to be caused by the migration of the CDN due to bankruptcy of Edgio.
https://learn.microsoft.com/en-us/azure/cdn/edgio-retirement-faq

Expected Behaviour

AZCopy is installed correctly

Steps To Reproduce

Run automatic/azcopy10/tools/chocolateyInstall.ps1

Environment

- Operating System: Windows 2019, Windows 2022, Windows 2025
- PowerShell Version: Latest
- Shell: Azure-Cli

Chocolatey Log

Not available due to being run on pipeline agent which get removed after each run. Relevant logs are placed in current behavior section.

Anything else?

No response

@denyos denyos added the Bug label Jan 9, 2025
Copy link

github-actions bot commented Jan 9, 2025

Thanks for raising this issue!

The packages within this repository are maintained by a small team of volunteer Community Maintainers, in their own time. Their time, like yours is important. Please help them by not wasting it.

This is a community repository where the expectation is that everybody will get involved by raising pull requests to fix problems they find. This will also allow that problem to be fixed more quickly as you don't have to wait for a member of the Community Maintainer Team to pick it up.

If you are unable to fix the issue yourself, the Community Maintainers Team will look at it when time allows. There are no service level agreements, nor should there be any expectation on when people can resolve issues in their own time.

A few dos and don'ts:

  • Do provide as much information as you can in any issue that you raise.
  • Don't complain that an issue has not yet been picked up or resolved. You are expected to help out in this community maintained repository. If you are unable to do so, don't complain when others don't adhere to your timelines. There is no SLA nor should you have any expectation of one.
  • Do read the CONTRIBUTING and COMMITTERS documentation before raising a pull request as it contains valuable information on what automation is used in this repository.
  • Do read the Code of Conduct.
  • Don't post your frustration in comments. The Community Maintainers Team are not a punching bag for your frustration. You will only end up banned from the repository.

Thank you.
(Automatically posted message)

@denyos
Copy link
Author

denyos commented Jan 9, 2025

Did some more investigation. New locations are:

https://aka.ms/downloadazcopy-v10-windows redirects to
https://azcopyvnext-awgzd8g7aagqhzhe.b02.azurefd.net/releases/release-10.27.1-20241113/azcopy_windows_amd64_10.27.1.zip

https://aka.ms/downloadazcopy-v10-windows-32bit redirects to
https://azcopyvnext-awgzd8g7aagqhzhe.b02.azurefd.net/releases/release-10.27.1-20241113/azcopy_windows_386_10.27.1.zip

As only the location has changed and not the version numbers of the tool, I'm not sure how to fix this.
Fixing the script in the choco lib requires a new version release, but 10.27.1 is already existing. Introducing a new version (10.27.2) breaks the relation with the AzCopy version, and making a 10.27.1.1 is breaking semver.

@denyos
Copy link
Author

denyos commented Jan 9, 2025

It seems that the fix is already on its way:
#2612

@corbob
Copy link
Contributor

corbob commented Jan 9, 2025

Thank you for raising the issue @denyos and @stephenmuss for being so quick with a PR. I'll take a look today and see what we can do to get it updated. As for versions, it'll likely be put out with a version fix notation: 10.27.1.20250109.

@corbob
Copy link
Contributor

corbob commented Jan 10, 2025

I've confirmed that the package has successfully pushed and is available on CCR.

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

No branches or pull requests

2 participants