Skip to content

fix: flush the extracted image and retry a ZFS timeout before importing a VM disk - #224

Closed
MickLesk wants to merge 1 commit into
mainfrom
fix/vm-import-zfs-timeout
Closed

MickLesk wants to merge 1 commit into
mainfrom
fix/vm-import-zfs-timeout

Conversation

@MickLesk

@MickLesk MickLesk commented Nov 10, 2026 •

Copy link
Copy Markdown
Member

✍️ Description

On ZFS the volume create for qm disk import waited behind the writes the extraction had just made and failed with "got timeout" (#18580, and earlier opnsense #14127). vm_import_disk now syncs the image first and retries up to two times when qm reports got timeout, so every VM script gets it.

🔗 Related Issue

Fixes community-scripts/ProxmoxVE#18580

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected (Proxmox VE and/or Incus, as applicable).
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.
  • API.txt regenerated – If a function signature or behavior changed, API.txt was updated to match.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • ✨ New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing behavior in a way that may require updates in every downstream script.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, docs/, CONTRIBUTING.md, or other docs.

🤖 AI Assistance (X in brackets)

If you used an AI tool (GitHub Copilot, Claude, ChatGPT, etc.) to write or generate any code in this PR, you must confirm compliance below.
Select exactly one option.

  • No AI used – Code was written without AI assistance.
  • AI was used – The output has been reviewed and corrected, and I take responsibility for it matching this repo's conventions.

…ng a VM disk

On ZFS the volume create for qm disk import waited behind the writes the extraction had just made and failed with "got timeout" (#18580, and earlier opnsense #14127). vm_import_disk now syncs the image first and retries up to two times when qm reports got timeout, so every VM script gets it.
@github-actions

Copy link
Copy Markdown
Contributor

Try this branch

The engine and the scripts resolve independently, so a production script can
be run against the engine from this PR by setting one variable:

COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/community-scripts/core/fix/vm-import-zfs-timeout \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)"

Swap ct/debian.sh for whatever exercises the change.

This PR touches pve/, so it needs a Proxmox VE host.

Run a script from a fork as well
curl -fsSL https://raw.githubusercontent.com/community-scripts/core/fix/vm-import-zfs-timeout/tools/run.sh |
  bash -s -- https://raw.githubusercontent.com/YOU/DevScripts/your-branch ct/debian.sh \
             https://raw.githubusercontent.com/community-scripts/core/fix/vm-import-zfs-timeout

Note that run.sh is reached through a pipe, so the script it starts inherits
an exhausted stdin. Whiptail is fine — it opens /dev/tty — but a plain read
would see EOF. The single-variable form above does not have that problem.

Useful flags while testing

dev_mode=net logs every engine fetch with status and duration, which is the
quickest way to confirm the branch is really being used. dev_mode=keep stops a
failed build from deleting the container along with the evidence.

@MickLesk MickLesk closed this Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[HAOS VM] Pending writes after image extraction cause ZFS disk import timeout

1 participant