This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am provisioning azure resources including an azure event hub using bicep, but all of a sudden, the pipeline started failing as the event hub provisioning was failing with a timeout error as it takes more than 10 mins to get provisioned, the bicep template for the event hub namespace has identity type set as system assigned, and once I removed the identity setting, it started working as expected. It is unclear on why this error occurred all of a sudden. It would be very helpful if I can get some clarity on this.
Hi, Tarun
Are you setting a role assignment at the same time?
Hi Tarun Jain ,
Just following up to see if the below answer helped. Please do consider clicking Accept Answer as accepted answers help community as well. Also, please click on Yes for the survey 'Was the answer helpful'
If you are deploying a Role Assignment at the same time, it could be because the role already exists.
https://github.com/Azure/bicep/discussions/11429
A workaround is to either generate a new name, or manually delete the Role Assignment (it will appear in the IAM blade, although the identity the role is tied to, will be unknown if your event grid resource has been deleted).
Hi Luke,
No, I am not assigning a role. Just creating the event hub namespace with identity set to system assigned.
Bicep Template:
resource eventHubNamespace 'Microsoft.EventHub/namespaces@2021-11-01' = {
name: hubNameSpaceName
location: location
sku: {
name: 'standard'
tier: 'standard'
capacity: 1
}
tags:tags
identity: {
type: 'SystemAssigned'
}
properties: {
minimumTlsVersion: '1.2'
isAutoInflateEnabled: false
maximumThroughputUnits: 0
}
}
Surprisingly, the same pipeline started working again since yesterday without any modification. It was working earlier as well but was giving a timeout error around new year days 28th Dec to 3rd Jan.
Hi, Tarun
I can't explain why it wasn't working, but was able to successfully deploy a namespace using your code, I just modified the API it was using to the current version and made sure the namespace name was 6 char as more and it deployed for me.
resource eventHubNamespace 'Microsoft.EventHub/namespaces@2023-01-01-preview' = {
name: 'seddsd'
location: 'australiaeast'
sku: {
name: 'standard'
tier: 'standard'
capacity: 1
}
identity: {
type: 'SystemAssigned'
}
properties: {
minimumTlsVersion: '1.2'
isAutoInflateEnabled: false
maximumThroughputUnits: 0
}
}