Open magneticore opened 1 week ago
I am having the same issue, this just started on 6/18
FYI looks like this was the breaking change: https://github.com/microsoft/azure-pipelines-tasks/commit/1741517c4b2439116703dc26e8513303ade77d93
Rolling back to version 2.238.1 worked for us
FYI looks like this was the breaking change: 1741517
Rolling back to version 2.238.1 worked for us
How do I do that in Azure DevOps?
FYI looks like this was the breaking change: 1741517 Rolling back to version 2.238.1 worked for us
How do I do that in Azure DevOps?
Had the same problem and didn't know that either so i tried this:
Seems to work for me now!
FYI looks like this was the breaking change: 1741517 Rolling back to version 2.238.1 worked for us
How do I do that in Azure DevOps?
Had the same problem and didn't know that either so i tried this:
Seems to work for me now!
I am really too dumb for this. I don't have a azure-pipeline.yml that I can modify? And I can't change the YAML on the DevOps-Page, just view it...
FYI looks like this was the breaking change: 1741517 Rolling back to version 2.238.1 worked for us
How do I do that in Azure DevOps?
Had the same problem and didn't know that either so i tried this:
Seems to work for me now!
I am really too dumb for this. I don't have a azure-pipeline.yml that I can modify? And I can't change the YAML on the DevOps-Page, just view it...
I suppose you have insignificant permissions then? As far as I know you should mostly be able to change the yaml of your pipeline either in the repository or by pressing the 'edit' button in devops. But I should mention I'm also quite new at all of this do I could be wrong.
Reverting the push task to 2.238.1 worked for me. Previously I've tried converting the service connection to use federated credentials, but that had no effect. The workaround only worked after reverting the conversion as well.
New issue checklist
Task name
Azure IoT Edge
Task version
2
Issue Description
Hello!
The Azure IoT Edge - Push module image task is failing.
For context: Our last successful push was on June 14 as part of the validation steps in our CI/CD pipeline. These steps execute on PR creation as a requirement for the PR submission. Unfortunately for debugging means that all the output of the run is deleted since is not yet part of one of our designated branches. "This run is scheduled to be cleaned up the next time the cleanup job executes"
Since Monday we get an authentication token error.
Also any new builds or pipeline runs even using PRs when the pipeline was green now return the following message:
2024-06-18T20:17:02.2873393Z ##[section]Starting: Azure IoT Edge - Push module image 2024-06-18T20:17:02.2879784Z ============================================================================== 2024-06-18T20:17:02.2879934Z Task : Azure IoT Edge 2024-06-18T20:17:02.2880004Z Description : Build and deploy an Azure IoT Edge image 2024-06-18T20:17:02.2880115Z Version : 2.241.1 2024-06-18T20:17:02.2880180Z Author : Microsoft Corporation 2024-06-18T20:17:02.2880435Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/azure-iot-edge 2024-06-18T20:17:02.2880796Z ============================================================================== 2024-06-18T20:17:02.8225767Z Pushing module images... 2024-06-18T20:17:02.8293944Z ##[error]Failed to fetch container registry authentication token, please check you container registry setting in build task. The username for container registry is 2024-06-18T20:17:03.0065404Z ##[section]Finishing: Azure IoT Edge - Push module image
Checking this repo for the error I noticed the missing value on the string for username.
"InvalidContainerRegistry": "Failed to fetch container registry authentication token, please check you container registry setting in build task. The username for container registry is %s"
Extra debugging steps:
I added a bash task before this one as a way to debug and the ACR information shows up including the username.
As a second debugging method I added a Docker login task for the same ACR, the result also succeeds.
The original run was on Ubuntu-latest I also tested with Ubuntu-20.04, the error is present in both.
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu-latest and Ubuntu-20.04
Relevant log output
Full task logs with system.debug enabled
Repro steps