Closed NAVFreak closed 1 year ago
404 not found basically means that the endpoint doesn't exist - so I assume that the automation API's are not installed?
This one fails - which basically means it couldn't find any extensions:
##[command]Invoke-RestMethod -Method Get -Uri 'https://dev***-customer.Partner365.com:7098/bc***0ws/api/microsoft/automation/v***.0/companies(4e***c8d34-d039-ed***-b497-6045bdab9f4f)/extensions'
Are you sure you re-installed the necessary extensions?
My guess - this extension is missing:
"id": "10cb69d9-bc8a-4d27-970a-9e110e9db2a5",
"name": "_Exclude_APIV2_",
"publisher": "Microsoft",
"version": "21.3.51409.51464",
"brief": "_Exclude_APIV2_",
"description": "_Exclude_APIV2_",
Oh! It was another team who did the upgrade so I'll have to verify this but now I got something to work on 😊
You were right, they hadn't updated/installed the excluded apps. But now my problem transfered into #592 instead. Must be related to the upgrade.
It might be because you opened the deployment page too soon.
I recommend to:
It sounds weird, but you have to know how the deploymentstatus-page works - it's actually reading a file on the serverinstance, which locks the file while it's writing to it, which could (not always) block the deployment process.. . The only way how to solve it is to restart the serverinstance, and deploy a new version of the app.. .
Wait what? Are you talking about the mime error in #592 that happens at the first patch call (Invoke-RestMethod -Method Patch ) ?
`
2023-02-01T20:37:55.2871720Z *** Get Extension status
2023-02-01T20:37:55.2886845Z ##[command]Invoke-RestMethod -Method Get -Uri 'https://dev***-CompanyName.partner365.com:7098/bc***0ws/api/microsoft/automation/v***.0/companies(4e***c8d34-d039-ed***-b497-6045bdab9f4f)/extensions'
2023-02-01T20:37:56.3640568Z ##[command]Invoke-RestMethod -Method Patch -Uri 'https://dev***-CompanyName.partner365.com:7098/bc***0ws/api/microsoft/automation/v***.0/companies(4e***c8d34-d039-ed***-b497-6045bdab9f4f)/extensionUpload(0)/content'
2023-02-01T20:37:57.3352447Z ##[error]{
"error": {
"code": "Unknown",
"message": "A supported MIME type could not be found that matches the content type of the response. None of the supported type(s) 'Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaType, Microsoft.OData.ODataMediaTyp...' matches the content type 'application/octet-stream'."
}
}
2023-02-01T20:37:57.3918632Z ##[section]Finishing: ALOps Extension API
`
That happens in ALOps Extension API so it out of our control (?).
No, not that, sorry .. . I haven't been able to repro that particular problem. Please look into:
Describe the bug I'm running ALOps Extension API from a release pipeline. Seems like some parts works and some don't. We upgraded to 21.0 and put everything on a new server and I reinstalled external developer.
the used yaml n/a - used released pipeline
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior Deploy apps
Screenshots![image](https://user-images.githubusercontent.com/34970096/214942820-050cccd6-2d06-4417-b9de-527d12757cff.png)