How to identify the source of a failed task that may be created while upgrading SDDC Manager
Article ID: 425322
Updated On:
Products
Issue/Introduction
This is to identify the source of a failed task that may be created while upgrading SDDC Manager.
The subtask details showed the following:
Description: Pre-validation [Validate Source.Validate Disk Space.Verify Inventory.Verify Active Workflows]
Progress Messages: Error occurred during Active workflow pre-validation check. Please ensure there are no workflows running during SoS operation, please note that executing SoS operation during a running workflows may yield un-expected errors/results because the system could be in transitional state. Re-trigger SoS operation with force flag set as true or wait for workflow completion. Found active workflow for LCM, Description: Acquired DEPLOYMENT level lock for upgrades.
Environment
SDDC Manager 5.2.0.0 to 5.2.2.0 upgrade
Cause
Create a VMware SDDC Manager Diagnostic bundle
Look in /var/log/vmware/vcf/sddc-support/vcf-sos-activity.log for an entry at the time that the failed task is created. The log entry will contain the username and clientIP that created the task.
INFO [vcf_sos] [apiutils.py::log_audit::462::MainThread] {'username': '<user>', 'clientIP': '<clientIP>', ' remoteIP': '<remoteIP>', 'userAgent': 'okhttp/2.7.5', 'api': '/v1/system/health-summary', 'httpMethod': 'POST', 'operation': 'Initiates Health Summary checks.', 'httpStatus': 202, 'timestamp': '<timestamp>Z'
Resolution
The upgrade completed successfully and no additional action is needed.
Additional Information
Feedback
