Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/1451
many people thought that changing router.aggregation.command.each.timeout
in global setting will increase the timeout. Actually it is not, at least for
KVM.
for KVM hypervisors, we need to put
router.aggregation.command.each.timeout=??? in agent.properties and restart
cloudstack-agent.
This PR increases the minimal timeout to 120 seconds which is helpful but
does not really fix the issue.
I think it is better to add host-level setting for each host in the future,
like we did for domain/account, zone/cluster.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
