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

'Off' is suddenly marked as an invalid value for '--public-access' #13373

Closed
HermanCordes opened this issue May 7, 2020 — with docs.microsoft.com · 4 comments · Fixed by #13496
Closed

'Off' is suddenly marked as an invalid value for '--public-access' #13373

HermanCordes opened this issue May 7, 2020 — with docs.microsoft.com · 4 comments · Fixed by #13496
Assignees
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage az storage
Milestone

Comments

Copy link

HermanCordes commented May 7, 2020

On every deployment we use the following Azure CLI script to create a container without public access:

az storage container create `
    --name $containerName `
    --account-key $accessKey `
    --account-name $storageAccountName `
    --public-access "off" `
    --subscription $subscriptionId `
    --fail-on-exist

Since today it fails with this error message:

The value for one of the HTTP headers is not in the correct format. ErrorCode: InvalidHeaderValue
<?xml version="1.0" encoding="utf-8"?><Error><Code>InvalidHeaderValue</Code><Message>The value for one of the HTTP headers is not in the correct format.
RequestId:XYZ
Time:2020-05-07T05:49:34.9297306Z</Message><HeaderName>x-ms-blob-public-access</HeaderName><HeaderValue>off</HeaderValue></Error>

It fails for multiple deployments through Azure DevOps hosted agents, but also when executed manually through Azure Cloud Shell. I don't see any notice that this value isn't supported anymore. What could be the issue?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels May 7, 2020
@yonzhan yonzhan added the Storage az storage label May 7, 2020
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label May 7, 2020
@yonzhan yonzhan added this to the S170 milestone May 7, 2020
@yonzhan
Copy link
Collaborator

yonzhan commented May 7, 2020

add to S170

@Juliehzl
Copy link
Contributor

Juliehzl commented May 8, 2020

@HermanCordes It should be a server error and it is fixed already.
Could you try again?

@xinredhat
Copy link

the issue still is there.
$ az storage container create -n $BLOB_CONTAINER --public-access off --account-name $AZURE_STORAGE_ACCOUNT_ID --account-key $ACCOUNT_KEY

 The value for one of the HTTP headers is not in the correct format. ErrorCode: InvalidHeaderValue
<?xml version="1.0" encoding="utf-8"?><Error><Code>InvalidHeaderValue</Code><Message>The value for one of the HTTP headers is not in the correct format.
RequestId:5454f952-b01e-006c-76ba-253fe5000000
Time:2020-05-09T04:26:58.2070734Z</Message><HeaderName>x-ms-blob-public-access</HeaderName><HeaderValue>off</HeaderValue></Error>

@HermanCordes
Copy link
Author

@Juliehzl I've confirmed the issue still exist today. I've tested on an Azure DevOps pipeline with the AzureCLI task running on an ubuntu-latest agent. See error message below.

##[error]The value for one of the HTTP headers is not in the correct format. ErrorCode: InvalidHeaderValue
##[error]InvalidHeaderValueThe value for one of the HTTP headers is not in the correct format.
##[error]RequestId:861f7107-101e-0011-6a56-275897000000
##[error]Time:2020-05-11T05:42:14.2663151Zx-ms-blob-public-accessoff
##[error]Script failed with exit code: 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage az storage
Projects
None yet
4 participants