mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-05 03:27:07 +09:00
Myasnikov Daniil
bcdb82bf0c
The vminstance suite waits for each VMDisk's DataVolume to be Ready before anything consumes it. On `replicated` that works because the class binds Immediate; on the container lane's `local` class, which is WaitForFirstConsumer, CDI starts no importer for a disk nothing has consumed yet, so the DataVolume sits in PendingPopulation and the suite times out with no error anywhere. main makes the vm-disk chart request immediate binding for every source; the chart on this branch requests it only for uploads, and the lane must not change what it ships. So on the container lane, right after each VMDisk is applied, the suite waits up to 180s for CDI to create the DataVolume and its claim and annotates both with cdi.kubevirt.io/storage.bind.immediate.requested, the same request the chart already writes for uploads. Both, because the DataVolume decides what phase CDI reports and the claim is what the populator reads to start the import without a consumer. The QEMU lane annotates nothing. Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com> Assisted-by: LLM