Replies: 7 comments 3 replies
-
Can you share your lab deployment script here, please? I do not see these warnings and would like to understand which section of AL might cause them. |
Beta Was this translation helpful? Give feedback.
-
Do you run it in a cluster? If not, you can disable those checks with We need to check if the VMs are on some other cluster node in case AL is used on a cluster. For a quick fix in this case, you could set the warning action: $psdefaultparametervalues = @{
'*Cluster*:WarningAction' = 'SilentlyContinue'
} |
Beta Was this translation helpful? Give feedback.
-
Nope it's not a cluster; Thanks I'll disable those checks! |
Beta Was this translation helpful? Give feedback.
-
I hacked the module files to add:
in each cluster command that was being called, and that was the only thing that could silence it. (They do not honor setting the WarningAction via $psdefaultparameters ) |
Beta Was this translation helpful? Give feedback.
-
In case anyone else wants this, the following commit: is exactly what I changed to mute these warnings. I'm not sure why I started getting these and no one else did, so I don't know whether my changes would be generally useful. |
Beta Was this translation helpful? Give feedback.
-
@nyanhp has fixed this in the latest release 5.46.23 built last week. You can get it from GitHub or the PowerShell Gallery:
I guess it is time for a new release. |
Beta Was this translation helpful? Give feedback.
-
I'm using 5.46. It looks like this is a failovercluster change, its commands started dumping this warning each time they are called. Since AL calls these commands a lot, the output window has become a deluge of the above warning, swallowing all other output.
Does everyone else get this now too? Is there a known workaround?
Beta Was this translation helpful? Give feedback.
All reactions