Type handler version '1210.12' could not be found in the extension repository

[tfnaylor]

This issue seems to have reappeared suddenly today. There is an earlier (July-August) issue that was closed when it was resolved. We have tried US West and North Europe data centers and it is the same in both.

This is breaking a critical demo application for one of our customers so we are requesting attention on this ASAP.

[MarianoMunoz]

I am also suddenly experiencing this error with the chef extension when deploying my ubuntu (14.04.2-LTS) VMs with Azure Resource Manager. This was working without issue yesterday. I have the extension set to a type of "LinuxChefClient", with the typeHandlerVersion set to "1210.12".

I do not see that the extension version has changed or was deprecated in the change log or release notes.

I receive the following error:
{"error":{"code":"ArtifactNotFound","message":"Extension with publisher 'Chef.Bootstrap.WindowsAzure', type 'LinuxChefClient', and type handler version '1210.12' could not be found in the extension repository."}}

Any help with this issue would be appreciated. My deployment pipeline is currently blocked due to this unexpected issue.

[siddheshwar-more]

@tfnaylor @MarianoMunoz

We are verifying this issue with the help of https://github.com/Azure/azure-quickstart-templates/tree/master/chef-json-parameters-ubuntu-vm

I'll post update here. Thanks!

[aarsan]

I got this as well in the 'Central US' region, today.

[siddheshwar-more]

Hello
@tfnaylor @MarianoMunoz

We have verified this issue with template and template parameter files. And its working fine for us.

We used _azure-xplat-cli_ with below commands -

azure config mode arm
azure login 
azure location list
azure group create <resource_group_name> <location> -f <above-template-file-path> -d <deployment-name> -e <above-template-file-params-file-path>

Could you please try with above shared template and let us know?
Or please share your template files and CLI tool(i.e Azure PowerShell or Azure-xplat-cli)) details.

Thank you!

[siddheshwar-more]

^ @aarsan

[aarsan]

Just attempted to deploy again and received the following error:

{"error":{"code":"ArtifactNotFound","message":"Extension with publisher 'Chef.Bootstrap.WindowsAzure', type 'LinuxChefClient', and type handler version '1210.12' could not be found in the extension repository."}}

I am using the Python SDK, which is also what I used last night (which worked then).

[siddheshwar-more]

@aarsan
Could you please share the python script that you are using? So we can try at our end quickly.

[aarsan]

This sounds more like an Azure problem than an extension problem. I'm assuming Azure uses name resolution to find the location of the extensions and that part seems to be not working from all locations. Because it works for you doesn't mean it should work for everyone. I just changed the API version to '2015-05-01-preview' from '2015-06-15' and it still doesn't work. I will downgrade my extension version to see if that makes a difference.

[aarsan]

If I change it to '1207.12', it works. So, something is definitely wrong with '1210.12'. I will continue to try for the next few days and update this ticket.

[tfnaylor]

We are using Azure Resource Manager to deploy our templates. The same template was working fine the day before yesterday and nothing changed on our side.

I am surprised we are going through this again. The exact same thing happened in July and someone on your side figured out that it had to do with your Azure account having special privileges for this particular resource so you don't see the problem. I guarantee you that this has nothing to do with our templates or our approach to deploying them - the problem is in Azure and you guys fixed it in August so you just need to take the same approach now. Please review the issue (now closed) from the previous occurrence of this problem.

[tfnaylor]

Here is a link to the previous (closed) occurrence of this issue. Note that NimishaS ultimately acknowledged the issue on your side and fixed it. Please consult her on this.

#54

[MarianoMunoz]

I created a deployment using the same template you linked - https://github.com/Azure/azure-quickstart-templates/tree/master/chef-json-parameters-ubuntu-vm

I can confirm that I received the same error as before:
Status: NotFound
Type: Microsoft.Compute/virtualMachines/extensions
Resource: cheftest/LinuxChefExtension
StatusMessage:
{"error":{"code":"ArtifactNotFound","message":"Extension with publisher 'Chef.Bootstrap.WindowsAzure', type 'LinuxChefClient', and type handler version '1210.12' could not be found in the extension repository."}}

I get the same error using different subscriptions and accounts.

The deployment is created, but fails at the step where the chef client would be installed. It appears the extension is not available when azure attempts to fetch it from the repository.

[MarianoMunoz]

@aarsan
I can confirm that changing the version from '1210.12' to '1207.12' works on my side as well.

@siddheshwar-more
It appears that we have simply lost access to the latest extension in the repository. There was a fix that I needed in 1210.12 for my deployments.

What guarantee do we have in the future that releases/builds won't suddenly be removed from the azure extension repository? Should I instead be opening an Azure support ticket for these types of issues, since it affects the Azure platform as well?

[aarsan]

Please post an update to this problem.

[siddheshwar-more]

@aarsan
Yes, we are working with Azure team.
Thanks

[aarsan]

Thanks!

[NimishaS]

@tfnaylor, @aarsan, @MarianoMunoz, azure seems to have difficulty in handling the cases where we republish an internal extension more than once. We had published linux extension 1210.12.4.1001 recently to support centos where we republished internal extension more than once for testing.
Right now we have published linux extension 1210.12.4.2000 to fix this issue. Please verify.

[tfnaylor]

I am still getting the same error:
ArtifactNotFound : Extension with publisher 'Chef.Bootstrap.WindowsAzure', type 'LinuxChefClient', and type handler version '1210.12' could not be found in the extension repository.

This is causing serious problems for me with my customer right now...

[MarianoMunoz]

I received the following error when using "1210.12.4.2000" as the typeHandler version:
{"error":{"code":"InvalidParameter","target":"typeHandlerVersion","message":"The value of parameter typeHandlerVersion is invalid."}}

I also retried with the value "1210.12" to recheck and got the following:
{"error":{"code":"ArtifactNotFound","message":"Extension with publisher 'Chef.Bootstrap.WindowsAzure', type 'LinuxChefClient', and type handler version '1210.12' could not be found in the extension repository."}}

[NimishaS]

I have deleted extension 1210.12.4.1001 which was causing the issue. Last time this had fixed the issue.
I would request you to try once again. If this doesn't work then we'll take more assistance from Azure team.

[tfnaylor]

I still get the same failure:
ArtifactNotFound : Extension with publisher 'Chef.Bootstrap.WindowsAzure', type 'LinuxChefClient', and type handler version '1210.12' could not be found in the extension repository.

[MarianoMunoz]

@NimishaS Thank You. I have successfully deployed to Azure Resource Manager using typeHandler "1210.12".

It may have taken a while for the version to propagate through the azure systems, because I initially got a failure as well, but the following deployments worked without issue.

[tfnaylor]

Working for me as well - thank you.

Are you guys working to make sure this kind of thing doesn't happen in the future? Obviously it is very disruptive and in my particular case it could drive my customer to want to avoid Chef in their solution.

[aarsan]

To add to @tfnaylor , we are heavily investing in this extension rather than bootstrapping our nodes from the front door. It is extremely disruptive to our production and development environments. I appreciate all your hard work but without this service being reliable, we will have to avoid it.