Hello vCD Fans! 😉
After updating the vCD from version 9 to 10, I can no longer log into the vCD via Powercli.
There is an error message regarding the http request.
Possibly this error is caused by a new certificate of the new vCD appliance (presumption).
Is there a way "in words of the Linux user" to delete the Powershell KnowHost if available?
With other systems, the new host key also had to be accepted again, so that secure communication is possible again.
vCD | 10.1.2 |
pwsh | rhel7@PowerShell 7.2.0-preview.5 |
VMware.VimAutomation.Cloud | 12.0.0.15940183 |
Connect-CIServer -Server vcd.myserver.net -User vcd-api -Password *************
Connect-CIServer: 4/21/2021 11:48:52 AM Connect-CIServer Exception of type 'VMware.VimAutomation.Cloud.Views.Http.HttpUnsuccessfulRequestException' was thrown.
$error[0] | fl * -Force
PSMessageDetails :
Exception : VMware.VimAutomation.Cloud.Types.V1.CIException: 4/21/2021 11:50:55 AM Connect-CIServer Exception of type 'VMware.VimAutomation.Cloud.Views.Http.HttpUnsuccessfulRequestException' was thrown.
---> VMware.VimAutomation.Cloud.Views.Exceptions.CloudException: Exception of type 'VMware.VimAutomation.Cloud.Views.Http.HttpUnsuccessfulRequestException' was thrown.
---> VMware.VimAutomation.Cloud.Views.Http.HttpUnsuccessfulRequestException: Exception of type 'VMware.VimAutomation.Cloud.Views.Http.HttpUnsuccessfulRequestException' was thrown.
at VMware.VimAutomation.Cloud.Views.Http.HttpExtensions.EnsureSuccessfulResponse(HttpResponseMessage responseMessage)
at VMware.VimAutomation.Cloud.Views.Http.RestClient.Execute(HttpRequestMessage request)
at VMware.VimAutomation.Cloud.Views.Http.RestClient.Execute(Uri uri, HttpMethod method, Object value, IDictionary`2 requestHeaders)
at VMware.VimAutomation.Cloud.Views.Http.RestClient.Execute[T](Uri uri, HttpMethod method, IDictionary`2 requestHeaders, Object value)
at VMware.VimAutomation.Cloud.Views.Http.RestClient.Get[T](Uri uri)
at VMware.VimAutomation.Cloud.Views.CloudClient.GetView(Uri href)
--- End of inner exception stack trace ---
at VMware.VimAutomation.Cloud.Views.CloudClient.GetView(Uri href)
at VMware.VimAutomation.Cloud.Views.CloudClient.GetView(String href)
at VMware.VimAutomation.Cloud.Views.CloudClient.GetView[T](String href)
at VMware.VimAutomation.Cloud.Impl.V1.Service.ConnectivityServiceImpl.OnConnectCloudServer()
at VMware.VimAutomation.Cloud.Impl.V1.Service.ConnectivityServiceImpl.ConnectCloudServer(String serverName, String protocol, Int32 port, String organization, String username, String password,
IServerCertificateValidationHandler certificateValidator)
--- End of inner exception stack trace ---
at VMware.VimAutomation.Cloud.Impl.V1.Service.ConnectivityServiceImpl.ConnectCloudServer(String serverName, String protocol, Int32 port, String organization, String username, String password,
IServerCertificateValidationHandler certificateValidator)
at VMware.VimAutomation.Cloud.Impl.V1.Service.ClientManagerImpl.ConnectCloudServer(String serverUrl, String protocol, Int32 port, String organization, String username, String password, IServerCertificateValidationHandler
certificateValidator)
at VMware.VimAutomation.Cloud.Commands.Cmdlets.ConnectCIServer.ProcessRecordErrorHandled()
TargetObject :
CategoryInfo : NotSpecified: (:) [Connect-CIServer], CIException
FullyQualifiedErrorId : Cloud_ConnectivityServiceImpl_ConnectCloudServer_ConnectError,VMware.VimAutomation.Cloud.Commands.Cmdlets.ConnectCIServer
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {0, 1}
I am thankfull for every opinion
Many thanks...
moellerjot
Reinstalling all Powershell Modules resolves the issue.
get-module via powershell
Script 7.0.2.17839075 VMware.Vim
Script 12.3.0.17839331 VMware.VimAutomation.Cis.Core
Script 11.0.0.10379994 VMware.VimAutomation.Cloud
Script 12.3.0.17838947 VMware.VimAutomation.Common
Script 12.3.0.17839688 VMware.VimAutomation.Core
Script 12.2.0.17531155 VMware.VimAutomation.Sdk
Script 12.3.0.17855705 VMware.VimAutomation.Storage
Script 12.3.0.17856667 VMware.VimAutomation.Vds
Reinstalling all Powershell Modules resolves the issue.
get-module via powershell
Script 7.0.2.17839075 VMware.Vim
Script 12.3.0.17839331 VMware.VimAutomation.Cis.Core
Script 11.0.0.10379994 VMware.VimAutomation.Cloud
Script 12.3.0.17838947 VMware.VimAutomation.Common
Script 12.3.0.17839688 VMware.VimAutomation.Core
Script 12.2.0.17531155 VMware.VimAutomation.Sdk
Script 12.3.0.17855705 VMware.VimAutomation.Storage
Script 12.3.0.17856667 VMware.VimAutomation.Vds