-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AzureIoTEdge Task fails with a cryptic error #14929
Comments
I was getting the same error on Ubuntu-20.04 using [email protected] I found this bulletpoint in the News section of the Readme for the azure-iot-cli-extension,
Adding the
|
Hello @YarekTyshchenko and @rsmit3, thank you for letting us know about this issue. We are aware of this error and have deployed a hotfix to the DevOps Task that will be effective next week. Meanwhile, the solution provided by @rsmit3 is a good work around, and you can reference this Github issue here to track our bugfix progress. Thank you so much! |
@YarekTyshchenko @rsmit3 , the hotfix is now live. Please let us know if you are still running into this issue. If not, please feel free to close this Github issue. Let us know if you need anything else, thank you! |
@cindydeng1998, you mentioned that a hotfix is now live, but it does not seem that all Azure DevOps instances are receiving the hotfix. The latest version of the AzureIoTEdgeV2 task at this time is version 2.4.8. When, I attempt to run a"Deploy to IoT Edge devices" task against this version, everything works fine as expected.
However, when using a completely separate instance of Azure DevOps with the same exact codebase and deployment template, I noticed that this instance does not pull version 2.4.8, it instead pulls in version 2.4.7 and results in the exact same error mentioned in the original issue:
As such, it seems that this issue is very much related to a discrepancy in the 2.4.7 and 2.4.8 versions of the AzureIoTEdgeV2 task. When I attempt to configure the task version to use the latest release, I am only given the option to select "2.*". I have even tried removing and recreating steps but still end up getting the broken 2.4.7 version upon successive runs. How exactly can I ensure that my Azure DevOps instance is receiving the 2.4.8 hotfix? |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Type: Bug
Enter Task Name: AzureIoTEdge
Environment
Server - Azure Pipelines
Agent - Hosted or Private: Hosted
Issue Description
Deploy command fails:
A bash task was ran before the AzureIoTEdge Task that installed iotedgedev, because of a previous issue #14167. The script is just
pip install -U iotedgedev
Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
The text was updated successfully, but these errors were encountered: