Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-54885

Azure VM Plugin: 1: The storage account name already exists. Use a different name.

    Details

    • Type: Task
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: azure-vm-agents-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.138.1
      Azure VM Agents plugin : 0.7.3
      Jenkins server in a docker container on Ubuntu server, also hosted in MS Azure.

    • Similar Issues:
    • Released As:
      0.7.5

      Description

      We were using  a Storage Account which had issue and we changed our configuration Storage Account Name to use "Create New" this morning.

      It worked fine to start with but later when we changed the "Max Jenkins Agents Limit" from 10 to 50, there was no more agents coming up after first 10 and logs showed the following error:

      "The storage account name already exists. Use a different name. Nov 27, 2018 8:37:35 AM INFO com.microsoft.azure.vmagent.AzureVMCloud provision AzureVMCloud: provision: template sshfs has just verified failed"

      We changed the config and used "Storage Account Name" > "Use Existing" and chose one from the available lists.
      Click the "Verify Template"
      and see this error:
      "The following errors occurred while validating the template.
      1: The storage account name already exists. Use a different name."

      Is it trying to create the storage account ? while I am expecting it to just "use existing"
      We have three different cloud configs and I even created a new one, same issue with all.
      I can not say if this is new or we just started to face it, but for some time our autoscaling had been working all fine.

      It is worth mentioning that we made changes this morning since no VM was coming up and there were errors like:
      Failed to create storage account with account name ..
      Status code 429, {"error":{"code":"TooManyRequests","message":"The request is being throttled."}}

        Attachments

          Issue Links

            Activity

            Hide
            jieshe Jie Shen added a comment -

            Jack Chen, it is caused by inconsistent  results from API side. I have created an issue on github repo azure-rest-api-specs . And I think the root cause of this issue may on the service side changes.

            Show
            jieshe Jie Shen added a comment - Jack Chen , it is caused by inconsistent  results from API side. I have created an issue on github repo azure-rest-api-specs  . And I think the root cause of this issue may on the service side changes.
            Hide
            olblak Olivier Vernin added a comment -

            I confirm that the fix is deployed and working on ci.jenkins.io

            Show
            olblak Olivier Vernin added a comment - I confirm that the fix is deployed and working on ci.jenkins.io
            Hide
            psftw Peter Salvatore added a comment -

            Upgraded to 0.7.5 and we are back in business.  Thank you so much Jie Shen !

            Show
            psftw Peter Salvatore added a comment - Upgraded to 0.7.5 and we are back in business.  Thank you so much Jie Shen !
            Hide
            faizan Muhammad Faizan ul haq added a comment -

            Thanks for promot fix but the pain we went through was big and we are kind of ended up in "trust" thing on this plugin.

            Since the API changes can cause plugin to malfunction, could you please set regression tests to run periodically to catch if API changes are causing issues to an existing plugin.

            Any such measures are appreciated. 

            Show
            faizan Muhammad Faizan ul haq added a comment - Thanks for promot fix but the pain we went through was big and we are kind of ended up in "trust" thing on this plugin. Since the API changes can cause plugin to malfunction, could you please set regression tests to run periodically to catch if API changes are causing issues to an existing plugin. Any such measures are appreciated. 
            Hide
            jieshe Jie Shen added a comment -

            Muhammad Faizan ul haq, indeed it is a bug from service side instead of API changes caused this issue. But I will make some effort to try to get alerts from our plugins before users report  issues, thanks. 

            Show
            jieshe Jie Shen added a comment - Muhammad Faizan ul haq , indeed it is a bug from service side instead of API changes caused this issue. But I will make some effort to try to get alerts from our plugins before users report  issues, thanks. 

              People

              • Assignee:
                jieshe Jie Shen
                Reporter:
                faizan Muhammad Faizan ul haq
              • Votes:
                8 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: