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

Unable to use multiple Azure Profile Configuration using same subscription/credentials

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • _unsorted
    • Jenkins 2.32.3 on Windows 2012 R2.
      Azure VM Agents 0.4.3
      Azure Credentials 1.0

      When trying to use multiple Azure Profile Configurations that use the same Azure Credential/subscription, messages are found in AzureVMCloudVerificationTask logs indicating that that the process could not retrieve agent template. VM Agents are not stood up beyond the first defined Azure Profile Configuration in this scenario. It appears that the subscription ID is used as part of the agent template name, which in this scenario (more than one cloud configuration using same credentials) appears to cause an issue with it finding templates beyond the first define.

      Logs of AzureVMCloudVerificationTask when template can not be found.:
      Mar 21, 2017 7:21:42 PM INFO com.microsoft.azure.vmagent.AzureVMCloudVerificationTask executeAzureVMCloudVerificationTask: execute: verifying 1 template(s)
      Mar 21, 2017 7:21:42 PM INFO com.microsoft.azure.vmagent.AzureVMCloudVerificationTask executeAzureVMCloudVerificationTask: execute: verifying crousn2 in AzureVMAgents-ce514655-97cf-4a69-9173-554e1f246f9d
      Mar 21, 2017 7:21:42 PM INFO com.microsoft.azure.vmagent.AzureVMCloudVerificationTask executeAzureVMCloudVerificationTask: execute: could not retrieve agent template named crousn2 in AzureVMAgents-ce514655-97cf-4a69-9173-554e1f246f9d
      Mar 21, 2017 7:21:42 PM INFO com.microsoft.azure.vmagent.AzureVMCloudVerificationTask executeAzureVMCloudVerificationTask: execute: end
       

          [JENKINS-42991] Unable to use multiple Azure Profile Configuration using same subscription/credentials

          Claudiu Guiman added a comment -

          That's a design decision. You should group all templates in the same cloud definition. 
          Is this a bug for you or it's more of a feature request?

          Claudiu Guiman added a comment - That's a design decision. You should group all templates in the same cloud definition.  Is this a bug for you or it's more of a feature request?

          nathan crouse added a comment -

          If this is by design then this would become a feature request. There are scenario's (financial tracking is our need which we do by resource group) where cloud configurations (not necessarily just templates) might want to use different resource groups, but still be in the same subscription. In the current design I would need to create different subscriptions for each cloud configuration that is defined. Hopefully I'm not misunderstanding or misusing the design of the plugin.

          nathan crouse added a comment - If this is by design then this would become a feature request. There are scenario's (financial tracking is our need which we do by resource group) where cloud configurations (not necessarily just templates) might want to use different resource groups, but still be in the same subscription. In the current design I would need to create different subscriptions for each cloud configuration that is defined. Hopefully I'm not misunderstanding or misusing the design of the plugin.

          Claudiu Guiman added a comment -

          Your scenario is not currently covered. We'll consider your request and decide on how we'll implement it

          Claudiu Guiman added a comment - Your scenario is not currently covered. We'll consider your request and decide on how we'll implement it

            azure_devops Azure DevOps
            crousn1 nathan crouse
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: