-
Notifications
You must be signed in to change notification settings - Fork 241
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
Publish-NavApp in a container hangs running PS7 (after a prev. publish failure) #3591
Comments
@freddydk I cannot proof this is a BCContainerHelper issue, but it took me hours already to explain this to myself. I cannot imagine how to explain this to anyone else not familiar with BCCH, PS, and BC. |
Currently on vacation - but you can try a few things. I will look closer at the issue when I am back |
Have some great days off! Removing the session did not work. I was aware of -usePwsh $true, using this for now as a workaround. |
I'm experiencing this too, including when using UnPublish-BcContainerApp. |
@epernst Welcome to the club, even if you didn't ask for it. Every second or third day, I see another issue with Invoke* or PS7 usage. The problem is, that different issues can be solved with different settings for UsePwsh. Scripts, peppered with workarounds for various problems, sometimes like this, sometimes like that. Different behaviors on different systems with containers for the same version, the patches, isolation and other stuff is identical. I am lost with all this, loosing hours and hours with troubleshooting for problems I cannot solve using a single way... |
@MODUSCarstenScholling I've just upgraded our onprem BC deployment Powershell scripts for v24. That was not too much fun. I thought I had to use PS7 for that, but a lot of the MS cmdlets failed, if I used PS7. Some, like all those from the web administration module, could not load using PS7 (depending on a module that cannot be used in PS7), while others just gave strange errors when called from PS7. Calling the same functions from PS5, worked fine, even if PS5 actually calls the PS7 version of the module. And as you write, I have also spent hours and hours debugging this. |
@freddydk Is there anything you can say about this issue? |
Publish-NavApp in a container hangs running PS7 (after a prev. publish failure)
Publish-NavApp in a container hangs running PS7. But this is dependent on other commands. I have added a script below to repro. It has to do with a failing publish of one app and a failing publish of another app depending on the previous failing app. But it is required to have the runtime creation. I have tried to reduce, but I failed.
The errors for the last app are never shown in the console. instead the command hangs for hours if not canceled and the error is pushed to the event log.
Due to the fact that we have 150 apps, not every combination work together. This is not known while we create runtime packages for every app and every supported platform. So there can be compiler errors due to obsoletions or similar stuff.
The result is shown in the table below. The process hangs always when usePwshForBc24 is false. But due to the other case with other issues #3575 and PowerShell/PowerShell#23982, we can not turn it on.
I have added the transcripts for every combination and the script to repro. If you need, I can provide
Scripts used to create container and cause the issue
The error or hang occurs when processing publishing of Tour Planning, after Packing Unit Mgt. failed already. The list of apps depends on each other.
Full output of scripts
CrashMe-Transcripts.zip
The text was updated successfully, but these errors were encountered: