Closed tomaxsas closed 2 months ago
Narrowed down only to container apps jobs. Using API 'Microsoft.App/jobs@2024-03-01'
Same issue here... I use a similar logic to set this value from the output of a different deployment, I have not done any changes in months to this template and I receive the same error, what changed?
@tomaxsas @Erick151 Can you please email the resource IDs of your jobs to acasupport@ microsoft.com? Thanks!
I have already opened case, support verified, still looking for root cause.
If you’re able to, please send an email anyway and someone on the Container Apps jobs team can investigate also. Please include the resource ID and timeframe in which the error occurred. Thanks.
Thank you for reporting - we have found a potential regression. We are investigating and will update this thread with an ETA for the fix.
UPDATE:
The regression impacts some Container App Jobs deployments through bicep/ARM templates that use language expressions for referencing resources. This regression impacts deployments on East Aia, West Central US and West US 2.
We are rolling out a fix. We estimate the fix to be fully rolled out in 24 hours.
FIXED
The fix has been deployed to the impacted regions.
For anyone else who comes across this thread, this same issue is affecting the West Europe region.
Yes, @vinisoto can you please review the issue again, I have indeed confirmed the issue has been fixed on the regions you specified... However I am also using the EastUS2 region and facing the problem still.
I see another comment mentioning the failure on west Europe, I have not tested other regions but can fully confirm same original issue on EastUS2
This issue is a: (mark with an x)
Issue description
Started to get error: InvalidEnvironmentId\n\t\tMessage: EnvironmentId '[reference(resourceId('Microsoft.Resources/deployments', 'container-app-environment'), '2022-09-01').outputs.id.value] No code changes were done, on CI started to appear 1.5 Days ago
Steps to reproduce
Expected behavior [What you expected to happen.]
Deployment succeeded
Actual behavior [What actually happened.]
Deployment fails with error InvalidEnvironmentId\n\t\tMessage: EnvironmentId '[reference(resourceId('Microsoft.Resources/deployments', 'container-app-environment'), '2022-09-01').outputs.id.value]
Additional context
CLI