Skip to content

[BUG]: Auto Degradation of Azure Self-Hosted Agent from v4.253 to v4.252 upon upgrading. #5152

Open
@pratiksoni1408

Description

@pratiksoni1408

What happened?

Performing a manual download from https://github.com/microsoft/azure-pipelines-agent/releases for Azure Self-Hosted Agent v4.253.0 Windowsx64.

Configured the agent v4.253 in my Azure DevOps Organization (ADO Services). It shows the correct latest version in Azure DevOps UI for my newly configured agent.

However, old agents are not getting upgraded from v4.252 to v4.253 in ADO UI when I hit "Update All Agents". Additionally, when clicking on update all agents it downgrades the latest version to v4.252 for my new agent.

Powershell command line logs:

Downgrading agent to a lower version. This is usually due to a rollback of the currently published agent for a bug fix. To disable this behavior, set environment variable AZP_AGENT_DOWNGRADE_DISABLED=true before launching your agent.
Agent update in progress, do not shutdown agent.
Downloading 4.252.0 agent
Waiting for current job finish running.
Generate and execute update script.
Agent will exit shortly for update, should back online within 10 seconds.

There's an ongoing bug in v4.253 that is forcing it to lower down to the version v4.252.

Requesting to fix the bug sooner so that we see the new agent version in place.

Versions

Azure Self-Hosted Agent reporting on v4.253 / Windows.

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Windows

Version controll system

No response

Relevant log output

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions