robinmalik's Posts

Not yet, it was only brought to my attention this morning. Doing a little more checking/confirming and then I'll raise one tomorrow. Edit: Sadly, it was not that simple. I'm not able to replicate it working with PowerShell 7 now, erroring at the same point in deployment (so there must be more to it). I also forgot to say, it does start the VM, despite the error

We've hit this too with Start-VM as part of our "New VM" deployment process. Running vCenter 8.0 U2 (8.0.2.00000 (Build: 22385739) from 21 SEP 2023 with the latest versions of PowerCLI related modules at the time of writing. We patched ESXi to 8.0.2, 22380479 a few days ago, and the VM deployments we've tried since then have all failed at the point of power on with: PSMessageDetails : Exception : VMware.VimAutomation.Sdk.Types.V1.ErrorHandling.VimException.ViError: 08/11/2023 16:49:02 Start-VM One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> vmware.vapi.std.errors.InternalServerError: com.vmware.vapi.std.errors.internal_server_error {'messages': [com.vmware.vapi.std.localizable_message {'id': vapi.bindings.method.impl.unexpected, 'default_message': Provider method implementation threw unexpected exception: com.vmware.vapi.std.errors.InternalServerError, 'args': [com.vmware.vapi.std.errors.InternalServerError], 'params': , 'localized':}, com.vmware.vapi.std.localizable_message {'id': com.vmware.vapi.endpoint.badGateway, 'default_message': The endpoint, while acting as a gateway, received an invalid response from an upstream server it accessed while attempting to fulfill the request., 'args': [], 'params': , 'localized':}], 'data': , 'error_type': INTERNAL_SERVER_ERROR} at vmware.vapi.bindings.Stub.<InvokeMethodAsync>d__8`1.MoveNext() --- End of inner exception stack trace --- at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification) at vmware.cis.TasksStub.List(FilterSpec filterSpec, GetSpec resultSpec, Action`1 _progress, InvocationConfig _invocationConfig) at vmware.cis.TasksStub.List(FilterSpec filterSpec, GetSpec resultSpec) at VMware.VimAutomation.ViCore.Impl.V1.Service.CisTaskServiceImpl.<GetTasks>d__11.MoveNext() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at VMware.VimAutomation.ViCore.Impl.V1.Task.CisTaskServiceProvider.GetNotNullTasks(VimClient client, CisTaskService service, IEnumerable`1 ids) at VMware.VimAutomation.ViCore.Impl.V1.Task.CisTaskServiceProvider.<GetTasks>d__11.MoveNext() at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection) at VMware.VimAutomation.ViCore.Impl.V1.Task.CisTaskServiceProvider.GetTaskList(IEnumerable`1 uidList, IEnumerable`1 connectionUidList) at VMware.VimAutomation.Sdk.Impl.V1.Task.CoreTaskServiceImpl.GetTaskList(IEnumerable`1 uidList, IEnumerable`1 connectionUidList) at VMware.VimAutomation.ViCore.Impl.V1.Service.TaskServiceImpl.<GetTaskCore>d__8.MoveNext() at System.Linq.Buffer`1..ctor(IEnumerable`1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source) at VMware.VimAutomation.ViCore.Impl.V1.Service.TaskServiceImpl.GetTaskById(String uid, CmdletTaskInfoProvider cmdletTaskInfoProvider) at VMware.VimAutomation.ViCore.Impl.V1.Service.VmServiceImpl.StartVM(VirtualMachineInterop vm, Boolean isRequestedAsync) --- End of inner exception stack trace --- at VMware.VimAutomation.ViCore.Impl.V1.Service.VmServiceImpl.StartVM(VirtualMachineInterop vm, Boolean isRequestedAsync) at VMware.VimAutomation.ViCore.Util10Ps.BaseCmdlet.GenericServerCallHelper.PerformOperationOnObjects[T](List`1 objects, OperationHandler`1 operation, Boolean runAsynch) TargetObject : CategoryInfo : NotSpecified: (:) [Start-VM], ViError FullyQualifiedErrorId : Client20_VMServiceImpl_StartVM_ViError,VMware.VimAutomation.ViCore.Cmdlets.Commands.StartVM ErrorDetails : InvocationInfo : System.Management.Automation.InvocationInfo ScriptStackTrace : at <ScriptBlock>, F:\test\WebAutomatedManagement\Service\powershell\virtual-server-platform\new-vm.ps1: line 1207 at <ScriptBlock>, <No file>: line 1 PipelineIterationInfo : {} Having just done some testing from the command line (subtly different to how we drive deployments) I can replicate this error. It also triggers the same "One or more errors occurred" for Stop-VM. It could be PowerShell 5.1 related, as when I attempt the same Start/Stop commands against the same VM from PowerShell 7.3.9 it doesn't error. Just seeking someone locally for confirmation of the same experience.