akrasnov-drv commented on issue #10616:
URL: https://github.com/apache/cloudstack/issues/10616#issuecomment-2821597205
No, it did not help, at least not fully.
I have a cluster with nodes and local storage working.
I added `local.storage.uuid=` to `/etc/cloudstack/agent/agent.properties`
with uuid of existing local pool and restarted agents.
Then I restarted management and found doubled storage for a server. Existing
virsh pool still matches `local.storage.uuid=`
So I decided to remove the extra one. But when I placed the extra one to
maintenance, virsh pool was rename (if not replaced) and does not match
`local.storage.uuid=` anymore.
Here is the relevant output, no other commands was executed in that shell
session:
```
root@host:~# virsh pool-list
Name State Autostart
------------------------------------------------------------
4798c891-2d66-35c8-b0e3-706fedb51483 active no
e6b7e1ea-9cfb-409a-8daf-fb7bdc124d2e active no
root@host:~# grep storage /etc/cloudstack/agent/agent.properties
local.storage.uuid=e6b7e1ea-9cfb-409a-8daf-fb7bdc124d2e
#### here I placed local storage for 53529f92-5fea-4ad0-b908-f0d95630ff3d
to maintenance
root@host:~# virsh pool-list
Name State Autostart
------------------------------------------------------------
4798c891-2d66-35c8-b0e3-706fedb51483 active no
53529f92-5fea-4ad0-b908-f0d95630ff3d active no
root@host:~# grep storage /etc/cloudstack/agent/agent.properties
local.storage.uuid=e6b7e1ea-9cfb-409a-8daf-fb7bdc124d2e
```
--
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]
