Error while creating HCI VM Image : Internal error occurred: failed calling webhook "createupdatevalidationwebhook.infrastructure.azstackhci.microsoft.com": could not get REST client: unable to load root certificates: unable to parse bytes as PEM block

Aishwarya Upadhye 66 Reputation points
2023-10-11T07:44:30.1133333+00:00

Hi team ,

While Uploading the VM image on Azure Stack HCI we are getting following error :

nack.util.CLIError: Deployment failed. Correlation ID: cd401873-b24d-495f-ac31-bf9501a5e763. Internal error occurred: failed calling webhook "createupdatevalidationwebhook.infrastructure.azstackhci.microsoft.com": could not get REST client: unable to load root certificates: unable to parse bytes as PEM block

 

cli.azure.cli.core.azclierror: Deployment failed. Correlation ID: cd401873-b24d-495f-ac31-bf9501a5e763. Internal error occurred: failed calling webhook "createupdatevalidationwebhook.infrastructure.azstackhci.microsoft.com": could not get REST client: unable to load root certificates: unable to parse bytes as PEM block
az_command_data_logger: Deployment failed. Correlation ID: cd401873-b24d-495f-ac31-bf9501a5e763. Internal error occurred: failed calling webhook "createupdatevalidationwebhook.infrastructure.azstackhci.microsoft.com": could not get REST client: unable to load root certificates: unable to parse bytes as PEM block.

Please find the Screenshot attached .Would like to know how the error occurred and how we can solve the error.

Thanks,

Aishwarya Upadhye.User's image

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
335 questions
Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,811 questions
{count} votes

4 answers

Sort by: Most helpful
  1. Trent Helms - MSFT 2,541 Reputation points Microsoft Employee
    2023-10-11T12:40:16.3966667+00:00

    Hi,

    I have seen this error in a different context, but the cause was related to the certificate which was selected was incorrect. Knowing this, I would check if you have any custom certs within your cert stores, remove them and try again to see if the issue persists.

    Hope this helps!

    1 person found this answer helpful.

  2. Samuele Provvedi 150 Reputation points
    2024-01-17T13:57:22.5933333+00:00

    i've the same issues, i check the certificate in ashci , I didn't find anything strange This is a bug

    0 comments No comments

  3. Michael Anthony 0 Reputation points
    2024-09-11T23:01:19.5333333+00:00

    I see this hasn't been updated since January. Has anyone found a root cause and resolution to this issue? I am experiencing the exact same behavior.

    0 comments No comments

  4. Samuele Provvedi 150 Reputation points
    2024-09-19T13:00:37.7966667+00:00

    I’ve fix this when i upadate extension and cluster. In my case. But i don’t know the cause. For me is a bug

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.