Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
After updating the secret key generated from Azure and updating in Redhat Openshift - PVCs are not mounted to an existing pod which was working earlier
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 38%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESN%3C/text%3E%3C/svg%3E)
Sharan Noronha
0
Reputation points
HI,
I reently noticed that i was getting Error 401 while some of my PODS that were running and connected to Azure-disks are failing.
Hence, i re-generated a fresh set of keys and updated the secret in my Redhat openshift cluster for azure-credentials matching the same id . after updating , all my pods that are using PV that are connected with Azure-Disks are not being able to mount.
appreciate immeidate support or guidance
Azure Virtual Machines
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 6%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJH%3C/text%3E%3C/svg%3E)
Jilakara Hemalatha 5 Reputation points Microsoft External Staff Moderator2025-08-11T02:37:23.4166667+00:00 To assist in troubleshooting the issue, please provide the following information:
- What specific error messages are you seeing when you try to mount the PVCs?
- Did you restart any pods or controllers after updating the secret?
- Were there any other configuration changes besides regenerating and updating the secret?
- What version of OpenShift and Kubernetes are you currently running?
- Have you created a new pod with a new PVC and tried mounting the Azure Disk in that pod? If yes, did it work successfully?
- Is the service principal or managed identity associated with the new credentials still active and has the required permissions in Azure?
Sign in to comment
Sign in to answer