We had a service connection certificate expire last week so we created a new service connection and since then the deploy stage in our yaml pipeline will not run, the UI reports a status of cancelled and when I go into the logs this is all I see:
I've enabled system diagnostics which yielded nothing.
Has anyone encountered this before?
I've tried deleting and creating the service connection but that has not worked
after raging at the screen for a while, I remembered that I have a library that pulls in secrets from the key vault. The library was still using the original service connection (that was deleted). I updated the library to use the new service connection, re-authorised and the build then ran and deployed successfully.
An error message would of obviously been a massive help, its pretty bad that no logs appear in the build at all.
Related
I am pushing an ADF factory to another environment via a CICD Pipeline and YAML Config file in Azure Devops. I can successfully deploy but one of my linked services becomes a "bad resource" although it works in the master branch when I published it.
Furthermore I cannot delete this in the target data factory nor can I edit it. Getting the bad resource error. I suspect I need to edit something in the ARM file but I don't really understand this error nor can I find much information on similar.
{"stack":"Error: Error: Unable to save [SERVICENAME]. Bad resource\n at Rl.<anonymous> (https://adf.azure.com/app.06b0e174dd8e6fa8.js:1:11274843)\n at Generator.next (<anonymous>)\n at https://adf.azure.com/main.d1fe4ec6f69aa72f.js:1:66326\n at new c
That when I deploy my ADF to a new environment it succeeds with connections intact or at least that I can fix/edit.
EDIT: Even when I recreate the Linked Service I get the same error.
The answer to this is to store all of your connection credentials as secrets in Azure Keyvault then reference that. I am unclear why using the parameters in a linked service do not transfer into the ARM template and this cause it to be a "bad resource" but the Keyvault method translates into ARM correctly and the problem doesn't persist.
The developer who installed my Azure devops Git environment left a few months ago. My new developer doesn't really understand this environment.
We were using it already for several weeks, but yesterday I received an error message:
If I understood what my ex developer said, is that he placed an Agent in me remote desktop connected to my server which I have to activate (run as administrator) in order to deploy the Azure devOps releases.
But this time there is a "getaddrinfo ENOTFOUND" error which I don't understand an my new developer neither.
To narrow down the issue, please follow the items below:
Set variable system.debug to True in your pipeline, and click the error in your screenshot to check the detailed error log.
Go to the FTP service connection you are using in your pipeline, update the username and password, or create a new service connection to make sure your FTP server is connected.
I am just new to Azure Cloud and Devops, so forgive me if I may forget some critical info here.
So during creation of tasks for the release and selecting subscriptions, I get an error when trying to authorize the subscription (which I suspect is because of insufficient permissions associated to my account), so I go to advanced options to select the managed identity authentication.
After which no error shows now. So I set all remaining items and assign Deploy Azure App Service task. However during the running of the agent I get an error during Deploy Azure App Service step.
Error: Failed to get resource ID for resource type 'Microsoft.Web/Sites' and resource name 'sample-vue'. Error: Could not fetch access token for Managed Service Principal. Please configure Managed Service Identity (MSI) for virtual machine 'https://aka.ms/azure-msi-docs'. Status code: 400, status message: Bad Request
I have already set my azure app service to have a system assigned managed identity, but still this error occurs. I can't find any answer, online, with regards to the error above so hoping that someone could help explain to me the problem and how to possibly fix it. My hunch now is that I may have some insufficient permissions, but I don't know what it may be.
Please try the following items:
Remove and re-add the service connection in DevOps.
Check the rights of the account on Azure subscription. Please verify if the account has at least contributor access on Azure subscriptions. Check https://learn.microsoft.com/en-us/azure/billing/billing-add-change-azure-subscription-administrator
In VSTS Build definition, .Net Core Publish task started failing suddenly with below error.
Unable to load the service index for source
https://microsoft.pkgs.visualstudio.com/_packaging/Universal.Store/nuget/v3/index.json.
Response status code does not indicate success: 401 (Unauthorized).
The same build agent is working for the above package for the same step. It started failing suddenly from October 1st.
You most likely have an expired Personal Access Token in the .NET Core publish step. Check if that step is using any Service Endpoints and verify that any tokens in those endpoints are not expired.
I am deploying an application from DevOps Services to Bluemix. I got a 500 Error: Failed to establish a backside connection from the deployment. I've never gotten this error before. The log button on the DevOps Services runbar is grayed out, so I'm not sure where to look on the DevOps Services side for more information. The application is created in Bluemix, but when I try to look in logs on the Bluemix side, there are no logs since the application isn't started, so I'm also not sure how to debug on the Bluemix side.
The application I forked is alchemyapplication. It uses the python buildpack. The project owner told me they got the deploy to work. I am seeing some recent commits, so it is possible there were some changes that went in since that broke this. Any help on where to begin looking to debug is appreciated.
by any chance , the application has any database dependency ? Recently I faced this issue where my database instance was not valid and the front end application throw this error of "Failed to establish a backside connection"