'CustomScriptExtension', and type handler version '2.0' could not be found in the extension repository."

[cloudmelon]

I did as mentioned in the documentation
{
"name": "config-app",
"type": "extensions",
"location": "[resourceGroup().location]",
"apiVersion": "2015-06-15",
"dependsOn": [
"[concat('Microsoft.Compute/virtualMachines/', concat(variables('vmName'),copyindex()))]"
],
"tags": {
"displayName": "config-app"
},
"properties": {
"publisher": "Microsoft.Azure.Extensions",
"type": "CustomScript",
"typeHandlerVersion": "2.0", ========> version
"autoUpgradeMinorVersion": true,
"settings": {
},
"protectedSettings": {
"commandToExecute": "sh hello.sh ",
"fileUris": ["https://github.com/MyProject/Archive/MyPythonScript.py"
]
}
}
}

What i did as the following :

But My api version is "apiVersion": "2017-03-30",

I have error as the following :
{
"error": {
"code": "ArtifactNotFound",
"message": "Extension with publisher 'Microsoft.Compute', type 'CustomScriptExtension', and type handler version '2.0' could not be found in the extension repository."
}
}

But I do found the custom extension for linux vm in GitHub :
https://github.com/Azure/custom-script-extension-linux
They have version 2.0. Can't understand why they don't exist in the extension repository. I tried also the api version mentionned in the doc, it doesn't working. I think it has nothing to do with api-version but about if archifact existing in the extension repostory, please update the documentation about this issue. Thanks

Here is the Url : https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/custom-script-linux

Azure documentation issue guidance

Thanks for opening an issue in the Azure technical documentation repository.

We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.

Creating an issue

We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.

You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

• The relevant Azure service or technology.
• A link to the published documentation article that you have feedback about.
• Clear, specific feedback that the author can act on.

Pull requests and article contributions

If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

• Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
• Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.

Tech support and product feedback

If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

• If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

• Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

[mimckitt]

Thanks for the feedback! We are currently investigating and will update you shortly.

[mimckitt]

Thanks @cloudmelon. I have assigned to the author to review and update the doc as appropriate.

@danielsollondon can you take a look?

[JoolsJops]

Hi,

Has this been resolved?

[cloudmelon]

I am still waiting... Melony

…

On 26 Oct 2018, at 22:24, JoolsJops ***@***.***> wrote: Hi, Has this been resolved? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[majorvin]

@cloudmelon I had the same problem but I noticed one thing that did work for me.
Make sure that
publisher is set to Microsoft.Azure.Extensions VS Microsoft.Computes and
type is set to CustomScript VS CustomScriptExtension

[cloudmelon]

I am not sure if it is the same extension ( need confirmation ), I resolve this actually by keeping CustomScriptExtension but downgrade the version to 1.8 or 1.5 and it went smoothly… Thanks @majorvin

…

On 29 Oct 2018, at 23:11, majorvin ***@***.***> wrote: @cloudmelon <https://github.com/cloudmelon> I had the same problem but I noticed one thing that did work for me. Make sure that publisher is set to Microsoft.Azure.Extensions VS Microsoft.Computer and type is set to CustomScript VS CustomScriptExtension — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10862 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEaE-F0BNtu9HR7J6BIrEn-33ggB69feks5up3z5gaJpZM4U5wyL>.

[SR-P]

Hi,

Can I get the complete code of this.

[adeelilyas]

Change Publisher and Type as @majorvin said. It worked for me. reference

$vmss = Get-AzureRmVmss -ResourceGroupName $ResourceGroupName -VMScaleSetName $vmssResource.Name $vmss = Add-AzureRMVmssExtension -VirtualMachineScaleSet $vmss
-Name "customscript" -Publisher "Microsoft.Azure.Extensions"
-Type "CustomScript" -TypeHandlerVersion 2.0
-Setting $settings -AutoUpgradeMinorVersion $true

[craigcaseyMSFT]

It looks like this issue no longer exists, so I am closing this. Thanks!

[jstapelfeldt]

Hi, I am experiencing this behaviour again.

I've set up a linux vm scale set (using terraform) successfully with 2 extensions.

resource "azurerm_virtual_machine_scale_set_extension" "myextension" {
  count                        = length(var.regions[var.environment])
  name                         = "myextension"
  virtual_machine_scale_set_id = azurerm_linux_virtual_machine_scale_set.vmss[count.index].id
  publisher                    = "Microsoft.Azure.KeyVault"
  type                         = "KeyVaultForLinux"
  type_handler_version         = "2.0"
  auto_upgrade_minor_version   = true
  settings = jsonencode(
    {
      "secretsManagementSettings" : {
        "pollingIntervalInS" : "3600",
        "certificateStoreName" : "",
        "linkOnRenewal" : false,
        "certificateStoreLocation" : "<destination>",
        "requireInitialSync" : false,
        "observedCertificates" : ["<URL/path>"]
      }
    }
  )
}

resource "azurerm_virtual_machine_scale_set_extension" "certificate-management-extension" {
  count                        = length(var.regions[var.environment])
  name                         = "certificate-management-extension"
  virtual_machine_scale_set_id = azurerm_linux_virtual_machine_scale_set.vmss[count.index].id
  publisher                    = "Microsoft.Azure.Extensions"
  type                         = "CustomScript"
  type_handler_version         = "2.0"
  auto_upgrade_minor_version   = true
  provision_after_extensions   = [azurerm_virtual_machine_scale_set_extension.myextension[count.index].name]
  settings = jsonencode(
    {
      "script" : "${data.local_file.cert-management-script.content_base64}"
    }
  )
}

data "local_file" "cert-management-script" {
  filename = "certificate-management.sh"
}

Now to the problem: When I try to set up a third extension, very similarly to the certificate-management-extension, I run into following exception when deploying the infrastructure to Azure:

Error: creating Extension "third-extension" (Virtual Machine Scale Set "vmss" / Resource Group "rg"): compute.VirtualMachineScaleSetExtensionsClient#CreateOrUpdate: Failure sending request: StatusCode=404 -- Original Error: Code="ArtifactVersionNotFound" Message="No version found in the artifact repository that satisfies the requested version '2.0' for VM extension with publisher 'Microsoft.Azure.Extensions' and type 'CustomScript'."

I have also referenced extension 1 and 2 as dependencies, so they are executed in order. The third extension does not use the script block, it uses the commandToExecute instead:

settings = jsonencode(
    {
      "commandToExecute" : "echo Hello"
    }
  )

Any ideas why this is happening?

[lulzzz]

same issues as @jaydrue

[mikeolasz]

Same as @jaydrue and @lulzzz

[mikeolasz]

I found this in the documentation: https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/custom-script-windows#extension-schema
The second note in this section mentions that only one type of an extension can be installed during a deployment.
The error message although should be more informative.