Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/140#issuecomment-89006232
Ok, check! I will add it like that.
Although you can never be sure log packets go out over the network because
if the storage is unavailable due to local
Github user wido commented on the pull request:
https://github.com/apache/cloudstack/pull/140#issuecomment-88928090
Yes, it is, but we should log somewhere. Now a machine just reboots. We
should send something to syslog prior to rebooting.
---
If your project is set up for it, you ca
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/140
---
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
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/140#issuecomment-8641
Looks OK to me, waiting for a dead NFS connection is a PITA.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user runseb commented on the pull request:
https://github.com/apache/cloudstack/pull/140#issuecomment-6601
pinging @llambiel and @pyr @wido LGTM.
---
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
GitHub user remibergsma opened a pull request:
https://github.com/apache/cloudstack/pull/140
reboot much faster in case of storage failure
When storage cannot be reached, it does not make sense to reboot as it will
try to flush buffers, umount NFS mounts, etc. This will not work and
