Question 38740 in Ubuntu Question posted in
The official Ubuntu documentation can be found here.

"Resource file has already set" warning in Azure Devops, and variables unavailable – Ubuntu

Today, the Deployment jobs in our Azure Devops pipelines are all showing the warning:

##[warning]Resource file has already set to: D:a_tasksAzureKeyVault_1e244d.........1.212.0node_modulesazure-pipelines-tasks-azure-arm-rest-v2module.json

Additionally, variables passed into the jobs are being passed as empty strings, resulting in failures. – This seems to be resolved as of 3rd November.

Needless to say, we have re-run our pipelines multiple times to no avail, and have reviewed the Azure Devops status page – which shows no issues.

The pipelines were all working normally yesterday (1st November).

The warnings seem to appear for any deployment job referencing a variable group linked to a key vault, e.g.

  - deployment: MyDeployment
    pool:
      vmImage: ubuntu-20.04
    variables:
    - group: MyKeyVaultLinkedVariableGroup
Tags:

4

Answers


  1. Chosen as BEST ANSWER
    0

    This seems to be an Azure Key Vault issue.

    https://portal.azure.com/?quickstart=true#view/Microsoft_Azure_Health/AzureHealthBrowseBlade/~/serviceIssues

    Screenshot from Azure Portal


  2. 0

    Hi have you tried to use - task: AzureKeyVault@2 or latest Key Vautl task with version to retrieve the secret instead of setting with variable groups?

    And if you are using local self hosted agent, you could refer to local agent folder and delete the key vault tool files and run the key vault task to download the key vault tool again.

    =============================================================

    Updated 11/14

    Please check the Github ticket for Warnings about resource file already set for the latest release version of KeyVault for the fix that will be rolled out.

    ================================================================

    Update 12/2

    quick update

    Azure KV version 213 (both task and variable group) which fixes the
    warning issue, has been rolled out to south Brazil and EUS2 region for
    now. There is a slight delay, but version 213 will be rolled out to
    all regions and users by end of December 1st week.

    Login or Signup to reply.
  3. 0

    At least what i can tell now is that some versions of the Agent (2.206.1 – 2.213.2) is still downloading the AzureKeyVault Task with Version 1.212.0 which is causing these Warnings to appear. Therefore thats an issue of the AzureKeyVault Task and AzureAgents in common.

    related to the Github entry (here) this is already solved, but it might take a while to get rolled out to the agents out there. Also you can force an Update of Agents in the

    Project Settings -> Agent Pools -> Select the Pool -> Agents Tab

    either by clicking "Update All Agents" or by clicking the three dot menu on an agent and update this agent itself.
    This might lead that self hosted agents are not correctly restarted and need to get started manually, how to do that:

    https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/v2-linux?view=azure-devops#how-do-i-restart-the-agent

    with version 2.213 this issue should be fixed, according to the github entry but this sometimes is not the case.

    Updates will follow if there are any changes on the github entry later on

    Update 2022.11.25:
    In Most regions the Azure Agents are already rolled out but the AzureKeyVault Task is still on 1.212, according to the github issue the rollouts of this task to other regions will happen until the 1st week of December.

    Login or Signup to reply.
  4. 0

    I tried navigating to project settings –> Service connection

    enter image description here

    enter image description here

    and deleted the service connection and the issue got resolved

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search