AdminHodor
commented
11 months ago Dear @ptrk-tr,
but looking into the pipeline log it's missing the entire *** Published App section. This give already some insight. So the App gets published, what we can see earlier in the log. Later in the process, we retrieve the app information from the NST, which in this case does NOT return any info.
What is printed in the "*** Published App section" is retrieved via the standard BC-Cmdlets.
$PublishedTenantApp = Get-NAVAppInfo -ServerInstance $ServerInstance `
-Name $AppInfo.Name `
-Publisher $AppInfo.Publisher `
-Version $AppInfo.Version `
-TenantSpecificProperties `
-Tenant $Tenant.IdThe variable "$AppInfo", parameters NAME,PUBLISHER and Version are fetched from the App.json (Manifest). The "Version" is a typed object, no trouble expected. The Name and Publisher are text fields and could have some encoding issues with special characters, although we would expect is this is an issue it would also manifest on your DEV/TEST environment.
Could you please check manually on the NST what BC return with the following command:
Get-NAVAppInfo -ServerInstance "API" -TenantSpecificProperties -Tenant "default"Then check if the forementioned app is listed, and if the NAME and PUBLISHER mentioned in the printout match those found in the App.JSON.
Kind regards,
ptrk-tr
waldo1001
Describe the bug Since around the 10th of November we are running into a weird behavior with our Production Release Pipeline, where the pipeline runs into error in the ALOps App Publish step. The error is "No published extensions match the specified parameter values.". The pipeline contains 4 tasks which are all ALOps App Publish tasks to publish to our BC22.1 DE OnPrem environment. The first app gets published like expected but on the second app the pipeline fails with the aforementioned error.
Additional Information: The VM is running Windows Server 2022 Datacenter Azure Edition, a list of installed Windows Updates can be found in the screenshot section.
The VM running the Dev/Staging environments is running Windows Server 2019 Datacenter.
DevOps Agent:
Looking into the extension management page in BC shows that the second app has been published in the erroring run (see screenshot below) but looking into the pipeline log it's missing the entire *** Published App section.
I've also tried re-running the pipeline and disabling Publish steps 1,2 and 4 so only App 3 would get published but with the same error.
I've had to redact the company identifying information but I hope nothing of value was lost by doing that ;).
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output (first app) Also the complete output is necessary for us to see what is going on. Also use backtics:
the output (2nd app)
Expected behavior I expected the pipeline to sync and install/upgrade the apps successfully.
Screenshots Extension Management in BC:
Installed Windows Updates since the error occuring:
Installed PowerShell Version:
Additional context This only happens in this particular Release Pipeline, our Release Pipelines for Dev/Staging work normally. The pipeline hasn't been touched (only now, when I tried running it on another Agent), so no changes there and at that time no changes were published by the ALOps extension, so I'm really confused as how this error came out of the blue.
As this is impacting our Production environment and making it basically impossible to push updates to that environment this is a rather pressing problem, so please forgive me for directly mentioning you @waldo1001 @AdminHodor.
If I can provide any more information for you, I'll be glad to help where I can since this is probably a b**** to reproduce, if at all possible.
Best regards.