prashanthr2 opened a new issue, #12690:
URL: https://github.com/apache/cloudstack/issues/12690
### problem
When a KVM-based NFS Primary Storage is taken out of Maintenance Mode, the
CloudStack management state transitions back to "Up," but the actual mount
point is not restored on the KVM hosts. This results in a silent failure where
the storage is logically available in the UI but physically inaccessible on the
hypervisor.
Below is the error seen in the KVM agent log
```
2026-02-23 14:09:31,922 INFO [kvm.storage.LibvirtStorageAdaptor]
(AgentRequest-Handler-3:[]) (logid:5f0c1bd2) Found existing defined storage
pool b96dc55f-7075-3183-bcef-a0100e328e88, using it.
2026-02-23 14:09:31,922 DEBUG [utils.script.Script]
(AgentRequest-Handler-3:[]) (logid:5f0c1bd2) Executing command [/bin/bash -c
mountpoint -q /mnt/b96dc55f-7075-3183-bcef-a0100e328e88 ].
2026-02-23 14:09:31,926 WARN [utils.script.Script]
(AgentRequest-Handler-3:[]) (logid:5f0c1bd2) Execution of process [49226] for
command [/bin/bash -c mountpoint -q /mnt/b96dc55f-7075-3183-bcef-a0100e328e88 ]
failed.
2026-02-23 14:09:31,926 DEBUG [utils.script.Script]
(AgentRequest-Handler-3:[]) (logid:5f0c1bd2) Exit value of process [49226] for
command [/bin/bash -c mountpoint -q /mnt/b96dc55f-7075-3183-bcef-a0100e328e88 ]
is [32].
2026-02-23 14:09:31,926 WARN [utils.script.Script]
(AgentRequest-Handler-3:[]) (logid:5f0c1bd2) Process [49226] for command
[/bin/bash -c mountpoint -q /mnt/b96dc55f-7075-3183-bcef-a0100e328e88 ]
encountered the error: [32].
2026-02-23 14:09:31,926 ERROR [kvm.storage.LibvirtStorageAdaptor]
(AgentRequest-Handler-3:[]) (logid:5f0c1bd2) libvirt failed to mount storage
pool b96dc55f-7075-3183-bcef-a0100e328e88 at
/mnt/b96dc55f-7075-3183-bcef-a0100e328e88
2026-02-23 14:09:31,928 DEBUG [cloud.agent.Agent]
(AgentRequest-Handler-3:[]) (logid:5f0c1bd2) Seq 1-2670916054007415034: { Ans:
, MgmtId: 32987999634307, via: 1, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.Answer":{"result":"false","details":"Failed to create
storage pool: libvirt failed to mount storage pool
b96dc55f-7075-3183-bcef-a0100e328e88 at
/mnt/b96dc55f-7075-3183-bcef-a0100e328e88","wait":"0","bypassHostMaintenance":"false"}}]
}
```
### versions
4.22
### The steps to reproduce the bug
1. Navigate to Infrastructure > Primary Storage.
2. Select an NFS Primary Storage and click Enable Maintenance Mode.
3. Wait for the storage state to transition to Maintenance.
4. Click Cancel Maintenance Mode.
5. Observe the status in the UI (it returns to Up) and check the mount
status on the KVM host via mount -l.
### What to do about it?
_No response_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
