How to fix container does not exist in azure functions?

gandharv30 21

I have created an azure functions app with blob storage trigger. Now in my storage account, there is container 'test1' in which their is a folder 'my-directory' which I am tracking. I tested the code on my local machine, the function fires whenever a file is uploaded to blob storage mentioned above. But when I am running this on azure portal, the function does not fires at all when a file is uploaded to blob storage and shows the following two statements in the logs

Function 'pii' will wait 2000 ms before polling queue 'azure-webjobs-blobtrigger-dqml1'.
Container 'test1' does not exist.

I tried to these paths in function.json:-
"path": "test1/{name}.csv"
"path": "test1/my-directory/{name}.csv"

PS: I am using a free trial account!

Krish G 2,331 Reputation points

2020-08-28T18:53:15.703+00:00

Would you mind sharing your code snippet, specially the part where you have declared annotation for blob trigger/binding. Also, when you said it's working in local machine, is it with the same storage account as your deployed function or local storage emulator?
gandharv30 21 Reputation points

2020-08-28T19:05:47.82+00:00

Yes, sure @KrishnenduGhosh-MSFT . Hope you can help me out
Here is my functions, json:

*****> {

"scriptFile": "init.py",
"bindings": [
{
"name": "myblob",
"type": "blobTrigger",
"direction": "in",
"path": "test1/{name}.csv",
"connection": "AzureWebJobsStorage"
}
]
}**

And here is my local.settings.json
{
"IsEncrypted": false,
"Values": {
"AzureWebJobsStorage": "hidden"
}
}

Yes its working on the local machine with the same storage account.Also to tell you that account has dqml, a storage acc, dqml1 a functions app and dqml, an azure ml service
gandharv30 21 Reputation points

2020-08-28T19:14:42.853+00:00

Update : Also getting this in logs
Singleton lock acquired (dqml1/WebJobs.Internal.Blobs.Listener)
Also the public access level of the container is private, if that helps
@KrishnenduGhosh-MSFT
Krish G 2,331 Reputation points

2020-08-28T19:16:20.67+00:00

Can you also quickly check the App Setting of the Function App in Azure portal and confirm "AzureWebJobsStorage" entry is present with correct connection string? Just to eliminate any low-hanging fruits first.
gandharv30 21 Reputation points

2020-08-28T19:27:44.767+00:00

The two are different, I will check with this updated string and will let you know. Thanks @KrishnenduGhosh-MSFT
gandharv30 21 Reputation points

2020-08-28T19:35:30.66+00:00

I copied the connection string from the congig tab but now it does seem to work not ven on my local machine .Atleast earlier it was coorectly identifying changes ie file uploaded to the test1 container .
@KrishnenduGhosh-MSFT
Krish G 2,331 Reputation points

2020-08-28T19:37:11.003+00:00

Sorry could not follow you.
gandharv30 21 Reputation points

2020-08-28T19:45:07.147+00:00

I am saying that the connection string which I was using earlier was generated by these steps ie
Navigating to SETTINGS > Access keys inmy storage account's menu blade to see connection strings.
With this string everything was working as it should on my local machine.
The other connection string which i tried on your suggestion from the app settings of the function app is not working at all ie the now its not detecting any change in blob store when I upload a file to it on my local machine
@KrishnenduGhosh-MSFT
Krish G 2,331 Reputation points

2020-08-28T19:50:35.14+00:00

Are you seeing any error now while local debugging? Also, I am curious to know since now both your deployed function and local debugging pointing to the same storage account, when you upload to the blob container of this updated storage, either of the functions (deployed or local) will win to detect the change. So check if your deployed function won over you local debugging since both are now competing over the same resource.
gandharv30 21 Reputation points

2020-08-28T19:55:38.287+00:00

Still getting the same error : Container does not exist
@KrishnenduGhosh-MSFT
Shall I change back the conn_string to the precious one, at least in that case it was working on my local machine
Now it's now working at all!
Krish G 2,331 Reputation points

2020-08-28T20:05:58.793+00:00

Does the updated storage really have the container "test1" at all? Can you check from storage explorer? It's quite obvious from the error that the container "test1" does not exist in the storage account the function is connecting to. Please feel free to clarify if you have any confusion or not much familiar with Azure environment.
gandharv30 21 Reputation points

2020-08-28T20:12:58.28+00:00

Yes it does, I am pretty sure about it. For now, can you tell will the conn_string of storage account work in AzureWebJobsStorage in local.settings.json?
Also, since I do not have access to all the features of the portal, one thing I'd like to mention is that the logs in the monitor section under the code+test tab of functions tab only show connected.
They do not show any kinds of errors or any changes at all?Do you think this could be the cause??
@KrishnenduGhosh-MSFT
Krish G 2,331 Reputation points

2020-08-28T20:21:02.1+00:00

Yes, you can continue with the storage account which was working previously in your local settings. But I am sure the one which is configured in Azure portal does not have the required container. Please check with someone in your team who has access.
Until we can verify things are in place to be sure, it's difficult to troubleshoot. And do you have access to app insights by any chance to see logs?
gandharv30 21 Reputation points

2020-08-28T20:52:30.703+00:00

Thanks for your help @KrishnenduGhosh-MSFT .Figured out the problem. You were correct all this time. The two storage accounts are different. I cross-checked it via the account name parameter in conn_string.
Thanks a ton for being patient with me!
Krish G 2,331 Reputation points

2020-08-28T21:07:02.103+00:00

Glad that you could solve the problem :). I have posted the summary as the Answer below. Please consider "Accept" (you will find that option in answer) to help someone who might come across similar issue and find this thread by searching.

Accepted answer

Krish G 2,331 Reputation points

2020-08-28T21:03:07.577+00:00

@gandharv30 , as we troubleshooted the issue over the comment section, I am summarizing the root cause as answer.
The function app in the Azure was pointing to a different storage account than the one you were using for local debugging. The storage account used for the deployed function does not have the container "test1" created which is why you see the error "Container 'test1' does not exist" in the deployed function, but for local debugging it works fine which is pointing to the storage account having the container "test1" as expected.
Please sign in to rate this answer.

3 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to fix container does not exist in azure functions?

0 additional answers

Your answer