Terraform ResourceNotFound Error While running Azure Pipeline

Question

Terraform ResourceNotFound Error While running Azure Pipeline

sai pavan 40

Mar 20, 2024, 3:47 PM

Hi Team,

I'm facing issue with Terraform init from azure pipeline

"Failed to get existing workspaces: containers.Client#ListBlobs: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="The specified resource does not exist.\nRequestId"

Can any one please help me out to reslove the issue.

terraform

2 answers

Your answer

Answer 1

Amrinder Singh 5,790 Microsoft Employee

Mar 20, 2024, 4:23 PM

Hi @Sai pavan - Thanks for reaching out on Q&A forum.

Based on the exception, it points that it is trying to perform the list blob operation however failing to find the resource. Some of the possible reasons could be:

Incorrect URL formation resulting into path not being located.

Anonymous access but container level not set correctly.

Can you please share the complete exception snippet along with the failed request ID if possible?

sai pavan 40 Reputation points

Mar 20, 2024, 4:42 PM

Hi Amrinder Singh,

This the error i got while running the pipeline

Error: Failed to get existing workspaces: containers.Client#ListBlobs: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="The specified resource does not exist.\nRequestId:1e11d7af-601e-006a-5ad9-7a86c8000000\nTime:2024-03-20T15:17:34.0438520Z"

RequestId:1e11d7af-601e-006a-5ad9-7a86c8000000
Amrinder Singh 5,790 Reputation points Microsoft Employee

Mar 20, 2024, 5:02 PM

This appears to be happening due to the second scenario more likely.

What it the access level set on the container? It is Private or Blob?

If private then, try flipping that one to Blob once and observe the behavior.

If it is set to Blob, then check the configuration on the account level if Public access is allowed from there or not. If not, enable and then test it out.

Here is the link to review:

https://learn.microsoft.com/en-us/azure/storage/blobs/anonymous-read-access-configure?tabs=portal#about-anonymous-read-access

If that works, then you need to pass appropriate auth ahead.

Hope this helps! Kindly let us know if the above helps or you need further assistance on this issue.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
sai pavan 40 Reputation points

Mar 20, 2024, 5:45 PM

I set the access level to container then the terraform init issue is resolved and facing another issue with terraform plan, I've check the blob state it is in available but error is showing it is in lock
Amrinder Singh 5,790 Reputation points Microsoft Employee

Mar 21, 2024, 3:55 PM

Hi @Sai pavan -

Previously, you were trying to make List Blob call via anonymous auth and setting the access level correctly, it worked.

Now, the operation you are trying is acquiring lease. If you will check the auth options available with this operation, it doesn't have option for anonymous auth, hence the failure.

https://learn.microsoft.com/en-us/rest/api/storageservices/lease-blob?tabs=microsoft-entra-id

I would recommend testing this by providing any other auth mechanism and validate it ahead.

Do let us know if you have any further queries. I’m happy to assist you further.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
sai pavan 40 Reputation points

Mar 27, 2024, 10:01 AM

Hi @Amrinder Singh ,

In storage account I manually done acquire lease/break lease after that I tried to run the azure pipeline, and still it is showing the same error, I think pipeline is unable to communicate with state file.
sai pavan 40 Reputation points

Apr 2, 2024, 1:08 AM

Any update for this issue @Amrinder Singh
Amrinder Singh 5,790 Reputation points Microsoft Employee

Apr 2, 2024, 6:28 AM

Hi @Sai pavan - Even if you break the lease, based on the message appearing, the Terraform will try to acquire the lease in order to proceed ahead.

So, in order to go through that step, it tries to perform the operation and need to have any of the valid auth mechanism. Since you aren't passing any auth, the call goes as anonymous and tends to fail.

Please try performing the operation via any of the supported auth such as Access Key, SAS token etc for isolation

Hope that helps!

Answer 2

Hello sai pavan,

Thank you for posting your query here!

Can you please try to navigate to the storage account, then to the container in the Azure portal that holds the state file. The blob will show as ‘Leased’ under the leased state column. Select the state file and hit the ‘break lease’ button.
User's image

The lease state on the state file blob should then show as ‘broken’, and you can kick off the next Terraform run.

Or using Terraform you can force the unlock, (get the LockID from the error) e.g.

terraform force-unlock <LockId>

Similar posts that might help: https://stackoverflow.com/questions/65595852/terraform-statefile-is-locked-how-do-i-unlock-it

https://stackoverflow.com/questions/64690427/error-locking-state-error-acquiring-the-state-lock-state-blob-is-already-locke

Do let us know if you have any further queries. I’m happy to assist you further.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Share via

Terraform ResourceNotFound Error While running Azure Pipeline

2 answers

Your answer