Skip to content

Fix KVM incremental volume snapshot migration between secondary storages #16844

Fix KVM incremental volume snapshot migration between secondary storages

Fix KVM incremental volume snapshot migration between secondary storages #16844

Triggered via pull request March 13, 2026 12:09
Status Failure
Total duration 6m 45s
Artifacts

merge-conflict-checker.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
triage
error adding "status:has-conflicts": HttpError: Resource not accessible by integration
triage
Error: error adding "status:has-conflicts": HttpError: Resource not accessible by integration
triage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: eps1lon/actions-label-merge-conflict@v2.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/