tanyasethi-msft
commented
5 months ago Hi @JasonYeMSFT, Thanks for reporting this. The team is actively working on this issue and a fix will be available in the next release.
Open JasonYeMSFT opened 5 months ago
tanyasethi-msft
commented
5 months ago Hi @JasonYeMSFT, Thanks for reporting this. The team is actively working on this issue and a fix will be available in the next release.
tanyasethi-msft
commented
5 months ago Code Generator release: https://github.com/Azure/autorest.go/releases/tag/v4.0.0-preview.65
kaptinkoda
commented
5 months ago Running into the same issue in AzCopy v10.24.0. Error Message: Status: 400 The metadata specified is invalid. It has characters that are not permitted. I was able to copy using older version AzCopy v10.0.22631
tanyasethi-msft
commented
5 months ago Hi @kaptinkoda, this is not fixed yet. It will be available from AzCopy next release. This thread will be updated with the details.
tanyasethi-msft
commented
2 months ago This was fixed in go sdk - Storage - code generator update by tanyasethi-msft · Pull Request #22792 · Azure/azure-sdk-for-go (github.com) AzCopy next release in July 2024 will have this fix.
tanyasethi-msft
commented
2 months ago Next Azcopy release should fix this issue.
JasonYeMSFT
commented
2 months ago AzCopy 10.26.0 is released. Should we close this issue?
Which version of the AzCopy was used?
10.23.0
Which platform are you using? (ex: Windows, Mac, Linux)
Mac
What command did you run?
s2s Azure blob copy
What problem was encountered?
While reading the source, AzCopy incorrectly treat the object replication header as metadata, whose name doesn't comply to the rules of metadata names and cause the copy to fail.
How can we reproduce the problem in the simplest way?
Assign an object replication policy to a storage account. Go to the replicated source container. View properties of a blob on Portal and make sure there is an Object replication field. Use AzCopy to copy this blob to another storage account.
Have you found a mitigation/solution?
No