Решено не подходит логин в SSO

  • Автор темы Автор темы Nick
  • Дата начала Дата начала
  • Теги Теги
    vcsa 6.5

Nick

Случайный прохожий
Доброго времени суток! Планирую обновить vcenter server appliance 6.5 до vcenter server appliance 7.0.3. На этапе проверки условий и учетных данных в самом начале получаю ошибку что неверно указан пароль в SSO учетки administrator@vsphere.local. Пароль верный указываю 100%, я свободно могу авторизоваться этой же учеткой при входе на vcenter. Подскажите что можно проверить...
Ошибки с лога:
2021-12-13T09:12:20.044Z - error: Failed to login to 172.X.X.X:443 as : ServerFaultCode: Cannot complete login due to an incorrect user name or password.
2021-12-13T09:13:06.499Z - error: Login failed for source VC: Cannot complete login due to an incorrect user name or password.
Еще вопрос версия 7.0.3 содержит ли исправения от CVE-2021-44228 ?
 
Последнее редактирование:
Это помогло, но теперь у меня другой затык - зависает установщик vcenter на 80% с надписью:

Upgrade - Stage 1: Deploy vCenter Server​

Waiting for RPM installation to start. This may take several minutes...
А что в логе инсталлятора ? Он должен предлагать скачать лог с ошибками...
 
Там такое
2021-12-15T12:51:54.960Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: The object 'vim.VirtualMachine:148' has already been deleted or has not been completely created
2021-12-15T12:51:54.960Z - debug: Failed to get fileTransferInfo:ServerFaultCode: The object 'vim.VirtualMachine:148' has already been deleted or has not been completely created
 
А новый вцентр запустился ? Можно ли на него зайти ?
 
А новый вцентр запустился ? Можно ли на него зайти ?
Он почему то не пинговался. Разобрался с этим настроив dns суффикс и поменяв Ip,
Теперь когда захожу на новый vcsa на втором этапе вижу массу алармов:

Warning
Integrated Windows Authentication will be deprecated in vSphere 7.0. Support for IWA continues to be available in vSphere 7.0 and will be phased out in a future release. Learn more

Warning
This ESXi host [//X.X.X.X:443] is managed by vCenter Server [Y.Y.Y.Y].
Resolution
Make sure the cluster where this ESXi host resides is not set to Fully Automated DRS for the duration of the upgrade process.

Warning
SSL Trust certificate does not match the current MACHINE_SSL_CERT for one of the service registrations
Resolution
Please read KB79741 for more information. https://kb.vmware.com/s/article/79741

Warning
This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server. Extensions: VR Management (by VMware, Inc.) on http://vcenter.domen.local:80/|https://X.X.X.X:8043, Site Recovery Manager (by VMware, Inc.) on https://X.X.X.X:9086/vcdr/vmomi/sdk,
Resolution
Please ensure extensions are compatible with the new vCenter Server and re-register extensions with the new vCenter Server after upgrade. Please refer to the vSphere documentation on extensions, and the upgrade and interoperability guides.

Warning
Files that cannot be used with Lifecycle Manager 7.0.3 will not be copied from the source. These files include VM guest OS patch baselines, host upgrade baselines and files, and ESXi 6.0 and lower version host patches baselines.
Resolution
Please review VMware Lifecycle Manager 7.0.3 Documentation for details

Warning
The vSphere Update Manager specific proxy settings is deprecated from vSphere 7.0 GA. The Lifecycle Manager service will now use the proxy settings configured at VMware vCenter Server Appliance (VCSA) Interface.
Resolution
Please log in to the vCenter Server Appliance Management Interface to view and configure proxy settings. Refer to VMware Lifecycle Manager 7.0.3 release notes for details.

Warning
During the setup stage of the upgrade process the network settings of the source appliance are transferred to the new appliance. The source network settings might be invalid in the new subnet, and the upgraded appliance might become unusable due to communication or certificate issues.
Resolution
To ensure seamless upgrade, exit the wizard by clicking Cancel, and either reconfigure the network settings of the new appliance or redeploy the new appliance in the same subnet as the source appliance. If you want to proceed and the source appliance uses a static IP address, verify that the new upgraded appliance can send packets with the source network settings in the new subnet. If you want to proceed and the source appliance uses a DHCP IP address, in case you experience certificate issues after the upgrade, log in to the appliance management interface to regenerate the appliance certificates.
 
Все успешно обновился. Спасибо всем за советы.
 
Назад
Верх