Markus Reiter

`core-agent` logs show: ``` Feb 22 23:03:41.621 ERROR core::volume::service: error: Storage Error: Volume Config for Resource id 94d6f5c7-9a07-4c27-9cdb-8b499783571b not committed to the store at control-plane/agents/core/src/volume/service.rs:59 in core::volume::service::destroy_volume with request: DestroyVolume...

```yaml --- spec: labels: local: "true" num_replicas: 2 operation: operation: Destroy size: 8589934592 status: Deleting uuid: 94d6f5c7-9a07-4c27-9cdb-8b499783571b topology: node_topology: explicit: allowed_nodes: - talos-cp-2 - talos-cp-3 - talos-cp-1 preferred_nodes: - talos-cp-1...

Also tried restarting `core-agent` now, nothing changed.

@tiagolobocastro, one of my nodes went into `NotReady`. After rebooting it, I have again one pod stuck in `ContainerCreating` with ``` Warning FailedAttachVolume 23s (x8 over 2m9s) attachdetach-controller AttachVolume.Attach failed...

@tiagolobocastro, I have again encountered a problem with one of my volumes after a node reboot. 1 replica is online, 1 is degraded, and the corresponding pod is showing: ```...

I forgot to mention: Even after the node with the degraded replica is rebooted, the volume's `rebuildProgress` is still stuck at 40.

@burrbull, this needs a rebase.

@burrbull, this needs a rebase.

@romixlab, any update on this?

Waiting for https://github.com/proxmoxer/proxmoxer/pull/86 so this can be integrated more natively.