Closed PeterConijn closed 1 year ago
Update: reinstalled ALOps.ExternalDeployer; reset service. New error:
2022-12-15T08:47:11.0538960Z ##[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'." } }
If you upgraded to v21, you definitely need to re-install external deployer, because MIcrosoft broke stuff. We recently updated the external deployer.
We can't test all scenarios - and I have no idea how you install your services onprem. But I did get git feedback yesterday from one of the external deployer users:
In case helpful - to succeed with updated version for BC210 required me to : 1) specify instance parameters for Install-ALOpsExternalDeployer -ServerInstance 'BC210' -ListenPort 7210 2) remove PowerShell module folders from previously installed versions (otherwise got error from $CERFilePath in Install-ALOpsCertificate() returning array rather than single value file as required...) (for me older versions located in C:\Program Files\WindowsPowerShell\Modules\ALOps.ExternalDeployer) 3) to tidy - remove unwanted services e.g. Remove-ALOpsExternalDeployer -ServiceName 'ALOpsExternalDeployer$BC'
Hope that helps... 🤔
Not yet. Same OData error, but we will keep looking.
We haven't been able to solve this, but are trying to move to cloud deployment. I don't know if you want to keep this issue open or not for future developments.
I have been trying to repro, but I can't - and as long as I can't repro the problem, I have to conclude it's a personal issue which I can't help with .. . So either you come with a repro and I'll investigate, or you can close the issue.
Describe the bug Since we updatede our OnPrem databases from 19.0 to 21.2 earlier this week, the deployment pipeline keeps hanging on extensionDeploymentStatus. It works fine up until that point, but it keeps repeating that line until it times out.
When pasting the url in a browser (with the correct username/password) it does generate a result.
The line in question (truncated, full info in log)
[command]Invoke-RestMethod -Method Get -Uri 'http://dyslsrvvm0001:7848/[.......]/extensionDeploymentStatus'
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior I expected the deployment to complete as it has before the update.
Screenshots If applicable, add screenshots to help explain your problem. You can easily paste them in here.
Additional context The problem occurred after the update to BC21.2 from BC19.0. Any manual deployment from VSCode does work as expected.
The error I am receiving from page 2508 is "Extension management is not supported for your system configuration.", but there's nothing on Google that explains that in detail. I was assured that the ALOps.ExternalDeployer was installed correctly, but I wasn't there that day.