Precheck fails with "500 INTERNAL_SERVER_ERROR" during VCF Operations for Logs 9.0 to VCF Log Management 9.1 upgrade

Products

• VCF Operations

Issue/Introduction

• When attempting to upgrade VCF Operations for Logs from version 9.0.x to VCF Log Management 9.1, clicking the Run Prechecks button in the UI fails immediately.
• The task transitions to a failed or pending state, and the following error is displayed in the UI:

  Failed to start task (error may be truncated): Unexpected HTTP response (Reference ID: ) - Status: 500 INTERNAL_SERVER_ERROR, reason: No task definition found for component OPS_LOGS and action precheck., resolution: Verify the component supports the specified action and upgrade path.

  

• Additionally, the following error can be observed on the VCF Services platform in the sddc-upgrade-service pod logs:

  ERROR sddc-upgrade-service 26 [...] []  - No task-definition found for component=OPS_LOGS in catalog=9.1 (action=precheck, source=9.0)
  ERROR sddc-upgrade-service 26 [...] [] ######## - Handling unexpected Exception (Reference ID: ########): LcmRestClientException
  com.broadcom.vcf.lcm.errorframework.exception.LcmRestClientException: No task definition found for component OPS_LOGS & action precheck.
          at com.broadcom.vcf.lcm.errorframework.exception.LcmRestClientException.taskDefinitionNotFound(LcmRestClientException.java:121)
          at com.broadcom.vcf.lcm.sddc.upgrade.service.resolver.SddcUpgradeTaskDefResolver.lambda$getTaskName$4(SddcUpgradeTaskDefResolver.java:128)

Environment

• VCF Operations 9.1.x
• VCF Log Management 9.1.x

Cause

This is a known issue regarding how the UI displays pre-check results for this specific component.

 

VCF Log Management 9.1 introduces a new architecture, migrating from standalone virtual appliances to a containerized microservices architecture hosted on the VCF Services Runtime. Because of this structural change, the transition from 9.0 to 9.1 is an automated side-by-side deployment followed by a configuration migration, rather than a traditional patch.

 

Due to this workflow, the system performs all necessary health and environment validations in-line during the actual deployment phase. The backend lifecycle service does not support a standalone precheck action for this legacy upgrade path. However, the UI incorrectly exposes the "Run Prechecks" button after the deployment parameters are saved. Clicking it triggers an action the backend cannot process, resulting in the 500 INTERNAL_SERVER_ERROR.

Resolution

To successfully upgrade to VCF Log Management 9.1, you must bypass the precheck step:

1. Navigate back to the upgrade wizard and complete the initial configuration step.
2. Once the configuration parameters are saved, do not click the Run Prechecks button.
3. Proceed directly by clicking the UPGRADE button to initiate the upgrade process.

Additional Information

Log Management Detailed Design
Upgrade to Log Management 9.1