Lifecycle Manager repository for VxRail cluster does not get updated with the latest versions.
Article ID: 377143
Updated On:
Products
Issue/Introduction
When editing the LCM image for a VxRail-based cluster, the system may fetch an older firmware and hardware update instead of the latest one.
Starting with VxRail 7.x, VxRail clusters support integration with vLCM. When you run vLCM on a VxRail cluster, vLCM interacts with Dell EMC’s VxRail Manager to retrieve necessary firmware and driver information.
Each cluster has its own VxRail Manager, which is the control point for managing that specific cluster's hardware and software lifecycle (including firmware, drivers, and VMware components like ESXi).
Each VxRail Manager connects to its own repository, which contains the validated software, firmware, and driver packages specific to that cluster's hardware and VMware components.
If you have Cluster A and Cluster B in the same vCenter Server, they will have separate VxRail Managers:
- Cluster A’s VxRail Manager will connect to its dedicated repository for updates specific to the hardware in Cluster A.
- Cluster B’s VxRail Manager will do the same, but with a repository tailored to Cluster B's hardware.
Environment
VxRail based clusters
VMware vCenter Server 7.x and 8.x
Cause
When modifying the LCM image for the non-functional cluster, the system might pull older firmware and hardware updates instead of retrieving the most recent ones.
It appears that while the functional cluster correctly retrieves the latest version (7.0.482-28332330), the problematic cluster continues to pull an outdated version (7.0.411-27847552) despite already being on the latest software release. This suggests an inconsistency in fetching the most recent firmware and hardware updates for the affected cluster.
Under /var/log/vmware/vmware-updatemgr/vum-server/hsm-service.log , we notice the following snippets for vxrail-cluster-cX (problematic cluster):
HsmService:YYYY-MM-DD 16:02:32,847[Dummy-9]hsmService:758 [INFO] Hsm service result: {'output': '[{"name": "vxrail-cluster-cX", "description": "", "version": "7.0.411-27847552", "supportedReleases": [{"release": "7.0.3", "manifest": "vxr-hspmf-70411-27847552-c8", "manifestVersion": "7.0.411-27847552"}]}]', 'error': None}
HsmService:YYYY-MM-DD 16:08:59,719[Dummy-11]hsmService:793 [INFO] Running command from C++: packages list
HsmService:YYYY-MM-DD 16:08:59,719[Dummy-11]hsmService:746 [INFO] Running command packages list
HsmService:YYYY-MM-DD 16:08:59,720[Dummy-11]hsmService:245 [INFO] Got operation arguments: _OptArgsHolder(host_id=None, package=None, release=None, task_id=None, version=None)
HsmService:YYYY-MM-DD 16:08:59,720[Dummy-11]hsmService:255 [INFO] Initiating executor
HsmService:YYYY-MM-DD 16:08:59,720[Dummy-11]hsmService:478 [INFO] Got network location: vxrail-vcentercluster1.com
HsmService:YYYY-MM-DD 16:08:59,720[Dummy-11]hsmService:503 [INFO] Extracted hostname: vxrail-vxrail-vcentercluster1, port: 443
HsmService:YYYY-MM-DD 16:08:59,736[Dummy-11]hsmService:270 [INFO] Successfully initiated executor
HsmService:YYYY-MM-DD 16:09:00,920[Dummy-11]hsmService:323 [INFO] Retrieved all packages: [PackageInfo(name='vxrail-cluster-cX', description='', version='7.0.411-27847552', supported_releases=[SupportedReleaseManifest(release='7.0.3', manifest='vxr-hspmf-70411-27847552-cX', manifest_version='7.0.411-27847552')])]
HsmService:YYYY-MM-DD 16:09:00,920[Dummy-11]hsmService:758 [INFO] Hsm service result: {'output': '[{"name": "vxrail-cluster-cX", "description": "", "version": "7.0.411-27847552", "supportedReleases": [{"release": "7.0.3", "manifest": "vxr-hspmf-70411-27847552-cX", "manifestVersion": "7.0.411-27847552"}]}]', 'error': None}
Whereas for the vxrail-cluster-cY (working cluster), we notice the following snippets:
[PackageInfo(name='vxrail-cluster-cY', description='', version='7.0.482-28332330', supported_releases=[SupportedReleaseManifest(release='7.0.3', manifest='vxr-hspmf-70482-28332330-cY', manifest_version='7.0.482-28332330')])]
HsmService:YYYY-MM-DD 16:09:27,222[Dummy-12]hsmService:758 [INFO] Hsm service result: {'output': '[{"name": "vxrail-hsp-cluster-cY", "description": "", "version": "7.0.482-28332330"}]', 'error': None}
Resolution
The VxRail cluster is expected to retrieve version 7.0.482-28332330, but it is pulling an outdated version 7.0.411-27847552. Since this issue appears isolated from vCenter, Dell support should be involved to investigate the VxRail Manager or associated repositories for potential misconfigurations or discrepancies.
Feedback
