Заметки в базе знаний VMware по платформе vSphere 7.0 Update 3

Выпущено много новых заметок в базе знаний по проблемам, планам, принятым решениям по платформе VMware vSphere 7.0 Update 3 (либо описывается текущая проблема во всех версиях):

  • vSphere 7.0 Update 3 Critical Known Issues and Workarounds (86287)
  • vSphere 7.0 Update 3 Known Issues and Workarounds (86281)
  • vSphere Back-in-time release upgrade restriction (67077)
  • Virtual machine hardware versions (1003746)
  • Build numbers and versions of VMware vCenter Server (2143838)
  • Removal of Windows Update published PVSCSI driver version 1.3.18.0 (86053)
  • Understanding vSAN on-disk format versions and compatibility (2148493)
  • Interactive/Scripted ISO upgrade to 7.0 U3 failed with message about live VIB installation (85859)
  • ToolsRamdisk option is not available with ESXi 7.0.x releases (83782)
  • Failed to create a new Virtual Machine with virtual Trusted Platform Module (vTPM) device (85974)
  • /etc/hosts and /etc/resolv.conf do not support direct update from 7.0 U3. The content of the files are saved to configstore. They can only be updated by public cli or API (86015)
  • «Authentication failed, Lifecycle Manager server could not be contacted», Access to Lifecycle Manager fails in vCenter 7.0 Update 3 when logged in with an Active Directory account (85962)
  • Intermittent 100% CPU Usage spikes on hosts with AMD EPYC Zen3 (Milan) CPUs (85071)
  • HPE Serviceguard for Linux Clustering (SGLX) with shared disks on VMware vSphere 7.x: Guidelines for supported configuration (Partner Verified and Supported) (85910)
  • Intel VMD is support plus additional support for RAID 1 for boot volumes (85889)
  • Backup speed are slow over NBD transport mode for VMs on high-latency storage (83401)
  • Intel NVM update tools do not work on Intel 1G igbn adapters (85983)
  • DRS Advanced option «MaxMemMBHeadroomPerHost» for Memory Headroom (86013)
  • vSphere Lifecycle Manager can show non-compliant status after rollup Remediation, new cluster creation or transition from Baseline-managed cluster to Image-managed cluster for few upgrade paths due to i40en/i40enu driver name change (85982)
  • «vSAN network alarm ‘RDMA Configuration Health'» warning is seen in vSAN over RDMA cluster when using async Intel icen driver (85947)
  • vSAN Health Service — vSAN HCL Health – NVMe device can be identified (85782)
  • vSAN Health Service — vSAN Network Health – Hosts with LACP issues (85886)
  • vSAN Health Service — vSAN Network Health – Hosts with duplicate IP addresses (85883)
  • vSAN Health Service — vSAN HCL Health – NVMe device is VMware certified (85852)
  • Unable to change vSAN File service configuration after creation (80028)
  • vSAN iSCSI first-time enablement with CHAP authentication fails with an internal error (86019)
  • vSphere Support for Intel’s Optane Persistent Memory (PMEM) (67645)
  • vCenter Server /storage/log filling up due to localhost_access.log and catalina.log in sso and lookupsvc log directories (85475)
  • «Error in method invocation Exception occurred while unzipping patch script, please retry after sometime» while patching VC 7.x (85797)
  • Clearing BACKUP_STORES certificates in the VCSA via shell script (82560)
  • File-based Backups via SFTP in vCenter 7.0 Update 2d failing with «General system error reported by backup server.» (85966)
  • WCP service fails to start in vCenter Server 7.x (82507)
  • Enabling and disabling vSAN over RDMA with unsupported driver/firmware versions for Intel E810* family NIC may lead to vSAN core dumps or ESXi Host PSOD (86077)
  • VMkernel might shut down virtual machines due to a vCPU timer issue (86075)
  • vCenter has a large number of localhost_access log files generated under /storage/log/vmware/eam/web/ (85249)
  • ESXi host fails with a backtrace NMI IPI: Panic requested by another PCPU (86100)
  • Workaround Instructions for CVE-2021-22048 (86292)
  • Guest OS Customization for Rocky Linux is not fully supported (86163)
  • vCenter upgrade from 7.0 update 2 to update 3.0 fails with could not find function «archive_build_segment_list» in file «/opt/vmware/vpostgres/13/lib/pg_addons.so» (86073)

Заметки в базе знаний VMware по платформе vSphere 7.0 Update 3: 2 комментария

  1. https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3a-release-notes.html#resolvedissues
    In the vSphere Client, when you log in with an Active Directory account, you might see an authentication error when you click the Lifecycle Manager icon
    In some cases, when you log in to a vCenter Server system by using an Active Directory account, you might see an authentication error when you click the Lifecycle Manager icon. In the vSphere Client, you see the error Authentication failed, Lifecycle Manager server could not be contacted. The issue does not occur when you use a vCenter Single Sign-On internal account or the default admin account administrator@vsphere.local.

    This issue is resolved in this release.

Добавить комментарий

Ваш адрес email не будет опубликован.