Issue/Introduction

Source and classification

• Source: Site case from the veeam &Commvault使用说明 group.
• Classification: Wait-state or incomplete shutdown during Worker initialization.
• Confirmation basis: On June 24, 2026, the group confirmed that initialization includes a package-deletion command that waits and retries. After the recorded screen appears, the Worker can be shut down from ZSphere UI. The site confirmed this worked.
• Internal tracking: No specific Jira.

Issue metadata

• Issue ID: None.
• Component/product: ZSphere and Veeam Worker.
• Status: Effective site workaround available; unique cause and permanent fix unconfirmed.
• Priority/severity: General; blocks current Worker creation/initialization.
• Affected version: Not provided.
• First fixed version: None.
• Confirmation date: June 24, 2026.
• Last updated: September 4, 2026.

Problem description

After a Veeam Worker VM starts, it performs system preparation and package operations. In the site case, a package-deletion command did not finish immediately. The Worker remained on the initialization screen for a long time and did not shut down automatically as expected, making the creation process appear stuck.

The group instruction was:

When Veeam creates a Worker, one command removes software packages. Wait for the command to retry.
When this screen appears, shut down the Worker from the UI.

The site confirmed success. Because package name, exit code, and script log are unavailable, do not attribute every missing shutdown to the same command or defect. Confirm the same initialization stage and preserve task/log data first.

Symptoms

• The Worker VM starts but creation remains incomplete.
• Console remains at initialization/system preparation.
• Package deletion is running or waiting.
• The script might retry after waiting.
• The confirmed screen appears but no automatic shutdown occurs.
• Veeam or ZSphere continues to display the Worker status as Creating or Initializing, or the task does not progress.

Site screenshot

Impact

• Current Worker cannot finish creation/registration.
• Dependent new backup, recovery, or transfer cannot start.
• Other healthy Workers are usually unaffected.
• There is no evidence of damage to existing backups or business VM data.
• Forced shutdown during package processing might leave an incomplete Worker system that must be recreated.

Environment

• Product: ZSphere and Veeam integration.
• Product line: ZVF.
• Component: Veeam Worker initialization script and creation flow.
• Version: Not provided.
• Trigger: A package command waits/retries during initialization and shutdown does not occur after the specified stage.

Possible causes

This symptom can be caused by one or more of the following conditions:

• Package processing is still waiting/retrying and has not reached shutdown.
• Initialization ended but automatic shutdown did not complete.
• File-system, boot, or kernel errors are outside the confirmed branch.

Resolution

1. Confirm the current stage

1. Find the Worker task and record start time, state, and full errors.
2. Open console, confirm it responds, and record the screen.
3. Determine whether the current state is one of the following:

• The console shows a package-deletion or system-cleanup operation in progress.
• The relevant command is waiting or retrying.
• The script has ended and the site-confirmed initialization-completion screen is displayed, but the VM did not shut down automatically.

4. If console shows file-system, boot, kernel, or another explicit failure, do not shut down under this article; troubleshoot that error.

2. Wait for the package command to retry

1. Keep the VM running while the command runs/retries.
2. Do not send repeated interrupts, restart, or trigger creation again.
3. Watch for new output and automatic retry.
4. Check whether the creation task updates.
5. Save screenshots and task details while waiting.

The group confirmed retry after waiting but gave no fixed duration. Use console output and task timestamps, not a uniform minute threshold.

3. Shut down from the UI after the specified screen appears

When package processing ended, the confirmed screen appears, and shutdown still does not occur:

1. Confirm no command or installation output is active.
2. Select the Worker VM in ZSphere.
3. Use normal Stop or Shut down.
4. Wait for Stopped.
5. Return to Veeam/Worker creation and observe completion.
6. After correct recognition, run backup/recovery validation.

4. If the task remains incomplete after shutdown

If the Worker has shut down but the creation task does not resume:

1. Refresh the Worker and task states to determine whether only the page state has not updated.
2. Check registration and duplicate/residual records.
3. Inspect task and management-node logs to determine whether it waits for shutdown/callback or failed.
4. Do not immediately delete it; save VM UUID, task UUID, screenshot, and logs.
5. Only after explicit failure and no background activity, recreate per current documentation.
6. Stop repeated retries and contact development if the same point recurs.

5. Check before recreation

If the Worker must be recreated, first check the following:

1. Image/template is intact and version-compatible.
2. A usable static IP is configured; slow DHCP responses might cause a different type of creation timeout.
3. Host, compute, storage, and network meet requirements.
4. The previous task ended with no package/install/initialization task running.
5. No residual Worker conflicts by name, IP, or UUID.

6. Collect information

If the issue remains, collect the following information and contact engineering:

• Exact ZSphere, API Proxy, and Veeam versions.
• Worker name, VM UUID, and creation-task UUID.
• Complete creation-task details and failure time.
• Continuous screenshots of the Worker console from initialization start until it stalls.
• Complete output before and after the package-deletion command.
• Worker VM startup, shutdown, and manual-operation times.
• Worker state shown in Veeam and ZSphere after manual shutdown.
• Management node log, Worker initialization log, and Veeam task log.
• Whether the issue reproduces consistently and whether it stalls at the same command or screen each time.

Additional information

Precautions

• This is one site's effective method, not authorization to shut down every stalled Worker.
• Wait for package processing to end and the confirmed screen before normal UI shutdown.
• Do not shut down while output continues.
• Force-ending the Worker VM process with host commands is not recommended because it might damage the VM system state.
• No valid host, DHCP timeout, and missing post-initialization shutdown are different stages.
• Do not repeatedly delete/recreate before saving logs and details.

Fix status

• Current status: Site workaround available.
• Temporary handling: Wait for retry; after command completion and the specified screen, shut down normally in ZSphere UI.
• Permanent fix: Unconfirmed.
• Fixed version: None.
• Related patch/fix package: None.

Related information

• Original discussion: June 24, 2026.
• Source group: veeam &Commvault使用说明.
• Site result: Waiting for retry and UI shutdown at the specified screen worked.
• Recommended images: The stalled Worker initialization screen and the screen shown after the package-deletion command ends, where UI shutdown is allowed.