Updated: Azure DevOps Server 2022.1 RTW now available

15 comments

Discussion is closed. Login to edit/delete existing comments.

• 

  Jonathan Gillette November 30, 2023 10:46 am 0

  collapse this comment copy link to this comment

  Updated our test TFS server to 2022.1 and it looks like it’s trying to update the agent to 3.225.2 (which on github says is a pre-release?), but fails. This could be something with our environment, but just seeing if anyone else has seen this as well.

  [2023-11-30 18:44:27Z INFO Agent] Refresh message received, kick-off selfupdate background process.
  [2023-11-30 18:44:27Z INFO SelfUpdater] Version ‘3.225.2’ of ‘agent’ package available in server.
  [2023-11-30 18:44:27Z INFO SelfUpdater] Current running agent version is 3.225.0
  [2023-11-30 18:44:27Z INFO SelfUpdater] An update is available.
  [2023-11-30 18:44:27Z INFO Terminal] WRITE LINE: Agent update in progress, do not shutdown agent.
  [2023-11-30 18:44:27Z INFO Terminal] WRITE LINE: Downloading 3.225.2 agent
  [2023-11-30 18:44:27Z INFO HostContext] Well known directory ‘Bin’: ‘C:\agents\A1\bin’
  [2023-11-30 18:44:27Z INFO HostContext] Well known directory ‘Root’: ‘C:\agents\A1’
  [2023-11-30 18:44:27Z INFO HostContext] Well known directory ‘Work’: ‘C:\agents\A1_work’
  [2023-11-30 18:44:27Z INFO SelfUpdater] Attempt 1: save latest agent into C:\agents\A1_work_update\agent1.zip.
  [2023-11-30 18:44:27Z INFO SelfUpdater] Download agent: begin download
  [2023-11-30 18:44:35Z INFO SelfUpdater] Download agent: finished download
  [2023-11-30 18:44:35Z WARN SelfUpdater] Unable to perform the necessary checksum validation since the target package hash is missed
  [2023-11-30 18:44:35Z INFO SelfUpdater] Attempt 2: save latest agent into C:\agents\A1_work_update\agent1.zip.
  [2023-11-30 18:44:35Z INFO SelfUpdater] Download agent: begin download
  [2023-11-30 18:44:43Z INFO SelfUpdater] Download agent: finished download
  [2023-11-30 18:44:43Z WARN SelfUpdater] Unable to perform the necessary checksum validation since the target package hash is missed
  [2023-11-30 18:44:43Z INFO SelfUpdater] Attempt 3: save latest agent into C:\agents\A1_work_update\agent1.zip.
  [2023-11-30 18:44:43Z INFO SelfUpdater] Download agent: begin download
  [2023-11-30 18:44:49Z INFO SelfUpdater] Download agent: finished download
  [2023-11-30 18:44:49Z WARN SelfUpdater] Unable to perform the necessary checksum validation since the target package hash is missed
  [2023-11-30 18:44:49Z INFO Agent] Ignore agent update exception. System.Threading.Tasks.TaskCanceledException: Agent package checksum validation failed.
  There are possible reasons why this happened:
  1) The agent package was compromised.
  2) The agent package was not fully downloaded or was corrupted during the download process.
  You can skip checksum validation for the agent package by setting the environment variable DISABLE_HASH_VALIDATION=true
  at Microsoft.VisualStudio.Services.Agent.Listener.SelfUpdater.DownloadLatestAgent(CancellationToken token) in D:\a\1\s\src\Agent.Listener\SelfUpdater.cs:line 375
  at Microsoft.VisualStudio.Services.Agent.Listener.SelfUpdater.SelfUpdate(AgentRefreshMessage updateMessage, IJobDispatcher jobDispatcher, Boolean restartInteractiveAgent, CancellationToken token) in D:\a\1\s\src\Agent.Listener\SelfUpdater.cs:line 82
  at Microsoft.VisualStudio.Services.Agent.Listener.Agent.RunAsync(AgentSettings settings, Boolean runOnce) in D:\a\1\s\src\Agent.Listener\Agent.cs:line 379
  [2023-11-30 18:44:49Z INFO Agent] Auto update task finished at backend, there is no available agent update needs to apply, continue message queue looping.

  • 

    Merlyn Oppenheim December 4, 2023 11:36 am 0

    collapse this comment copy link to this comment

    Hi Jonathan, thank you for the report. 3.225.2 is indeed the correct version for 2022.1 (we’ll update the tag). The error message indicates that “hashValue” is missing from the API response (https://[your server]/_apis/distributedtask/packages/agent?platform=win-x64). That shouldn’t be happening; we’re taking a look on our end to see how that could occur.

• 

  constantin munteanu December 4, 2023 5:56 am 0

  collapse this comment copy link to this comment

  was Maven 3.9.x compatibility issue fixed into 2021.1 RTW version?

  • 

    Gloridel Morales December 4, 2023 3:02 pm 0

    collapse this comment copy link to this comment

    Hi Constantin, this was not resolved with the final release of Azure DevOps Server 2022.1. As a workaround, you can continue using Maven 3.9.x with the property –

    Dmaven.resolver.transport=wagon

    . This change forces Maven to use Wagon Resolver Transport. Check out the documentation here for more details.

• 

  Tore Østergaard Jensen (TORE) December 5, 2023 11:38 pm 0

  collapse this comment copy link to this comment

  It would be sweet if the Feature Timeline could also be updated to indicate the features that are part of 2022.1:
  https://learn.microsoft.com/en-us/azure/devops/release-notes/features-timeline-released

  • 

    Tore Østergaard Jensen (TORE) December 8, 2023 12:23 am 0

    collapse this comment copy link to this comment

    Now we are on the subject, then I think that there are still changes marked with “Future” that is already in the product.

    E.g. the following from April 2018:
    https://learn.microsoft.com/en-us/azure/devops/release-notes/2018/apr-16-vsts#trigger-ci-builds-from-yaml

    Or this one from from September 2018
    https://learn.microsoft.com/en-us/azure/devops/release-notes/2018/sep-10-azure-devops-launch#configure-builds-using-yaml

    Or this one from October 2018
    https://learn.microsoft.com/en-us/azure/devops/release-notes/2018/sprint-142-update#use-yaml-template-expressions-inline

    I could go on – this is just the three oldest that I figure is already there.

    • 

      Gloridel Morales December 13, 2023 9:08 am 1

      collapse this comment copy link to this comment

      Hi Tore, features for 2022.1 are now identified in the Released Feature table. We will look into reviewing this next year and mark with the corresponding release for any features that we have missed.

• 

  Kohl, Franz December 7, 2023 7:15 am 1

  collapse this comment copy link to this comment

  I’ve updated our test Azure DevOps Server from 2022.0.1 + Patch 5 to 2022.1 – and found an option missing in the “Publish build artifacts” task, which is significant to some of our developers.

  On 2022.0.1 + Patch 5, in the “Publish build artifacts” task in the “Advanced” section, you can still find the option “File copy options” with the corresponding input field (plus the new checkmark option “Tar the artifact before uploading”).

  On 2022.1 (after the upgrade from 2022.0.1 + Patch 5), the option “File copy options” with the corresponding input field is completely missing! Only the new option “Tar the artifact before uploading” is available in the “Advanced” section.

  Both tasks have an identical Task version in the UI (1.*; no other available) and in the log (1.200.0).

  This is a showstopper for our upgrade plans, unfortunately. I’d appreciate it if you could commit this bug and provide a timeline for a fix/patch.

  TIA, Franz

  • 

    Gloridel Morales December 13, 2023 4:16 pm 1

    collapse this comment copy link to this comment

    Hi Franz, we thank you for reporting this. We opened a bug to investigate and address this issue.

    • 

      Kohl, Franz December 18, 2023 1:00 am 0

      collapse this comment copy link to this comment

      Hi Gloridel,

      Based on Merlyn’s suggestion (see below), I just filed a problem report for this.

      Please ensure that the bug you’ve already opened gets connected to the problem report to prevent duplicate efforts and communication.

      Thanks,
      Franz

  • 

    Merlyn Oppenheim December 14, 2023 10:45 am 1

    collapse this comment copy link to this comment

    Thank you for your report! We appreciate your feedback and want to resolve this issue as soon as possible. To help us do that, we need some more information from you. Please open a ticket on Developer Community here: https://developercommunity.visualstudio.com/AzureDevOpsServerTFS.
    Make sure to use “Report a Problem” and provide a clear title and description of the issue. You can also use the ticket to track the progress of the resolution. Once you have opened the ticket, please post the link to it here and we will follow up with you. We hope to hear from you soon!

    • 

      Kohl, Franz December 18, 2023 12:57 am 0

      collapse this comment copy link to this comment

      Hi Merlyn,

      I just filed this as a problem, as you suggested.

      Here is the link to the report:
      https://developercommunity.visualstudio.com/t/ADS-20221-RTW:-%E2%80%9CPublish-build-artifacts/10543525

      HTH,
      Franz

• 

  Dave Klostermann December 7, 2023 12:32 pm 0

  collapse this comment copy link to this comment

  Is there a workaround to be able to continue using older version of the agent on this ADO Server version? We have some software limitations that require us to be on Ubuntu 18/20 and use Agent 2.217.x. When we test the upgrade on our test instance, the upgrade works, but then we get errors in the pipeline saying that Agent version 3.22.2 is required.

  If that is a new requirement, we are stuck on the ADO Server 2022 version and can no longer upgrade.

  • 

    Michael Hauer December 11, 2023 3:34 am 0

    collapse this comment copy link to this comment

    Just out of curiosity: why is v3.x agent a problem for you? v3 is compatible with Ubuntu 18.x and 20.x.

• 

  Joona Tenhunen February 1, 2024 11:47 pm 0

  collapse this comment copy link to this comment

  After installing Azure DevOps Server 2022.1 Plans feature not working at all

  https://developercommunity.visualstudio.com/t/After-installing-Azure-DevOps-Server-202/10576764