Re: ALARM - ACS reboots host servers!!!
ues. You might think we could >>> just stop the affected VMs, but NFS tends to make things that touch it >>> go into D state, even with 'intr' and other parameters, which affects >>> libvirt and the agent. >>> >>> We could perhaps open a feature request to disable all HA and just >>> leave things as-is, disallowing operations when there are outages. If >>> that sounds useful you can create the feature request on >>> https://issues.apache.org/jira. >>> >>> >>> On Mon, Mar 3, 2014 at 5:37 AM, Andrei Mikhailovsky >>> wrote: >>>> >>>> Koushik, I understand that and I will put the storage into the >>>> maintenance mode next time. However, things happen and servers crash from >>>> time to time, which is not the reason to reboot all host servers, even >>>> those >>>> which do not have any running vms with volumes on the nfs storage. The >>>> bloody agent just rebooted every single host server regardless if they were >>>> running vms with volumes on the rebooted nfs server. 95% of my vms are >>>> running from ceph and those should have never been effected in the first >>>> place. >>>> - Original Message - >>>> >>>> From: "Koushik Das" >>>> To: "" >>>> Cc: d...@cloudstack.apache.org >>>> Sent: Monday, 3 March, 2014 5:55:34 AM >>>> Subject: Re: ALARM - ACS reboots host servers!!! >>>> >>>> The primary storage needs to be put in maintenance before doing any >>>> upgrade/reboot as mentioned in the previous mails. >>>> >>>> -Koushik >>>> >>>> On 03-Mar-2014, at 6:07 AM, Marcus wrote: >>>> >>>>> Also, please note that in the bug you referenced it doesn't have a >>>>> problem with the reboot being triggered, but with the fact that reboot >>>>> never completes due to hanging NFS mount (which is why the reboot >>>>> occurs, inaccessible primary storage). >>>>> >>>>> On Sun, Mar 2, 2014 at 5:26 PM, Marcus wrote: >>>>>> >>>>>> Or do you mean you have multiple primary storages and this one was not >>>>>> in use and put into maintenance? >>>>>> >>>>>> On Sun, Mar 2, 2014 at 5:25 PM, Marcus wrote: >>>>>>> >>>>>>> I'm not sure I understand. How do you expect to reboot your primary >>>>>>> storage while vms are running? It sounds like the host is being >>>>>>> fenced since it cannot contact the resources it depends on. >>>>>>> >>>>>>> On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: >>>>>>>> >>>>>>>> On 02.03.2014 21:17, Andrei Mikhailovsky wrote: >>>>>>>>> >>>>>>>>> Hello guys, >>>>>>>>> >>>>>>>>> >>>>>>>>> I've recently came across the bug CLOUDSTACK-5429 which has rebooted >>>>>>>>> all of my host servers without properly shutting down the guest vms. >>>>>>>>> I've simply upgraded and rebooted one of the nfs primary storage >>>>>>>>> servers and a few minutes later, to my horror, i've found out that >>>>>>>>> all >>>>>>>>> of my host servers have been rebooted. Is it just me thinking so, or >>>>>>>>> is this bug should be fixed ASAP and should be a blocker for any new >>>>>>>>> ACS release. I mean not only does it cause downtime, but also >>>>>>>>> possible >>>>>>>>> data loss and server corruption. >>>>>>>> >>>>>>>> >>>>>>>> Hi Andrei, >>>>>>>> >>>>>>>> Do you have HA enabled and did you put that primary storage in >>>>>>>> maintenance >>>>>>>> mode before rebooting it? >>>>>>>> It's my understanding that ACS relies on the shared storage to >>>>>>>> perform HA so >>>>>>>> if the storage goes it's expected to go berserk. I've noticed similar >>>>>>>> behaviour in Xenserver pools without ACS. >>>>>>>> I'd imagine a "cure" for this would be to use network distributed >>>>>>>> "filesystems" like GlusterFS or CEPH. >>>>>>>> >>>>>>>> Lucian >>>>>>>> >>>>>>>> -- >>>>>>>> Sent from the Delta quadrant using Borg technology! >>>>>>>> >>>>>>>> Nux! >>>>>>>> www.nux.ro >>>> >>>> >>
Re: ALARM - ACS reboots host servers!!!
s storage. The >>> bloody agent just rebooted every single host server regardless if they were >>> running vms with volumes on the rebooted nfs server. 95% of my vms are >>> running from ceph and those should have never been effected in the first >>> place. >>> - Original Message - >>> >>> From: "Koushik Das" >>> To: "" >>> Cc: d...@cloudstack.apache.org >>> Sent: Monday, 3 March, 2014 5:55:34 AM >>> Subject: Re: ALARM - ACS reboots host servers!!! >>> >>> The primary storage needs to be put in maintenance before doing any >>> upgrade/reboot as mentioned in the previous mails. >>> >>> -Koushik >>> >>> On 03-Mar-2014, at 6:07 AM, Marcus wrote: >>> >>>> Also, please note that in the bug you referenced it doesn't have a >>>> problem with the reboot being triggered, but with the fact that reboot >>>> never completes due to hanging NFS mount (which is why the reboot >>>> occurs, inaccessible primary storage). >>>> >>>> On Sun, Mar 2, 2014 at 5:26 PM, Marcus wrote: >>>>> >>>>> Or do you mean you have multiple primary storages and this one was not >>>>> in use and put into maintenance? >>>>> >>>>> On Sun, Mar 2, 2014 at 5:25 PM, Marcus wrote: >>>>>> >>>>>> I'm not sure I understand. How do you expect to reboot your primary >>>>>> storage while vms are running? It sounds like the host is being >>>>>> fenced since it cannot contact the resources it depends on. >>>>>> >>>>>> On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: >>>>>>> >>>>>>> On 02.03.2014 21:17, Andrei Mikhailovsky wrote: >>>>>>>> >>>>>>>> Hello guys, >>>>>>>> >>>>>>>> >>>>>>>> I've recently came across the bug CLOUDSTACK-5429 which has rebooted >>>>>>>> all of my host servers without properly shutting down the guest vms. >>>>>>>> I've simply upgraded and rebooted one of the nfs primary storage >>>>>>>> servers and a few minutes later, to my horror, i've found out that >>>>>>>> all >>>>>>>> of my host servers have been rebooted. Is it just me thinking so, or >>>>>>>> is this bug should be fixed ASAP and should be a blocker for any new >>>>>>>> ACS release. I mean not only does it cause downtime, but also >>>>>>>> possible >>>>>>>> data loss and server corruption. >>>>>>> >>>>>>> >>>>>>> Hi Andrei, >>>>>>> >>>>>>> Do you have HA enabled and did you put that primary storage in >>>>>>> maintenance >>>>>>> mode before rebooting it? >>>>>>> It's my understanding that ACS relies on the shared storage to >>>>>>> perform HA so >>>>>>> if the storage goes it's expected to go berserk. I've noticed similar >>>>>>> behaviour in Xenserver pools without ACS. >>>>>>> I'd imagine a "cure" for this would be to use network distributed >>>>>>> "filesystems" like GlusterFS or CEPH. >>>>>>> >>>>>>> Lucian >>>>>>> >>>>>>> -- >>>>>>> Sent from the Delta quadrant using Borg technology! >>>>>>> >>>>>>> Nux! >>>>>>> www.nux.ro >>> >>> >
Re: ALARM - ACS reboots host servers!!!
On 04.03.2014 12:55, Andrei Mikhailovsky wrote: Regarding having nfs and ceph storage in different clusters - sounds like a good idea for majority of cases, however, my setup will not allow me to do that just yet. I am using ceph for my root and data volumes and NFS for backup volumes. Having tiered storage is one of the stronger features that have drawn me towards Cloudstack, it should work better. I do plan to have a second, slower tier for backups and other more passive applications. I do currently need the backup volumes as snapshotting with KVM is somewhat broken / not fully working in 4.2.1. It has been improved from version 4.2.0 as it was completely broken. I am waiting for 4.3.0 where, hopefully, I would be able to keep snapshots on the primary storage (currently this feature is broken) which will make the snapshots with KVM usable. KVM volume snapshots worked well in 4.2.1 AFAIK and they still work well in 4.3, but VM snapshots are still not supported and I don't think they will be any time soon. We might get somewhere with it if we opt for LVM thin storage and snapshots, that'd be cool. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: ALARM - ACS reboots host servers!!!
I agree with France, sounds like a more sensible idea and killing hosts left, right and centre with live vms. I now understand the reasons behind killing the troubled host server, however, this should be done without killing live vms with fully working volumes. Regarding having nfs and ceph storage in different clusters - sounds like a good idea for majority of cases, however, my setup will not allow me to do that just yet. I am using ceph for my root and data volumes and NFS for backup volumes. I do currently need the backup volumes as snapshotting with KVM is somewhat broken / not fully working in 4.2.1. It has been improved from version 4.2.0 as it was completely broken. I am waiting for 4.3.0 where, hopefully, I would be able to keep snapshots on the primary storage (currently this feature is broken) which will make the snapshots with KVM usable. Cheers for your help guys - Original Message - From: "France" To: users@cloudstack.apache.org, d...@cloudstack.apache.org Sent: Tuesday, 4 March, 2014 10:34:36 AM Subject: Re: ALARM - ACS reboots host servers!!! Hi Marcus and others. There is no need to kill of the entire hypervisor, if one of the primary storages fail. You just need to kill the VMs and probably disable SR on XenServer, because all other SRs and VMs have no problems. if you kill those, then you can safely start them elsewhere. On XenServer 6.2 you call destroy the VMs which lost access to NFS without any problems. If you really want to still kill the entire host and it's VMs in one go, I would suggest live migrating the VMs which have had not lost their storage off first, and then kill those VMs on a stale NFS by doing hard reboot. Additional time, while migrating working VMs, would even give some grace time for NFS to maybe recover. :-) Hard reboot to recover from D state of NFS client can also be avoided by using soft mount options. I run a bunch of Pacemaker/Corosync/Cman/Heartbeat/etc clusters and we don't just kill whole nodes but fence services from specific nodes. STONITH is implemented only when the node looses the quorum. Regards, F. On 3/3/14 5:35 PM, Marcus wrote: > It's the standard clustering problem. Any software that does any sort > of avtive clustering is going to fence nodes that have problems, or > should if it cares about your data. If the risk of losing a host due > to a storage pool outage is too great, you could perhaps look at > rearranging your pool-to-host correlations (certain hosts run vms from > certain pools) via clusters. Note that if you register a storage pool > with a cluster, it will register the pool with libvirt when the pool > is not in maintenance, which, when the storage pool goes down will > cause problems for the host even if no VMs from that storage are > running (fetching storage stats for example will cause agent threads > to hang if its NFS), so you'd need to put ceph in its own cluster and > NFS in its own cluster. > > It's far more dangerous to leave a host in an unknown/bad state. If a > host loses contact with one of your storage nodes, with HA, cloudstack > will want to start the affected VMs elsewhere. If it does so, and your > original host wakes up from it's NFS hang, you suddenly have a VM > running in two locations, corruption ensues. You might think we could > just stop the affected VMs, but NFS tends to make things that touch it > go into D state, even with 'intr' and other parameters, which affects > libvirt and the agent. > > We could perhaps open a feature request to disable all HA and just > leave things as-is, disallowing operations when there are outages. If > that sounds useful you can create the feature request on > https://issues.apache.org/jira. > > > On Mon, Mar 3, 2014 at 5:37 AM, Andrei Mikhailovsky > wrote: >> Koushik, I understand that and I will put the storage into the maintenance >> mode next time. However, things happen and servers crash from time to time, >> which is not the reason to reboot all host servers, even those which do not >> have any running vms with volumes on the nfs storage. The bloody agent just >> rebooted every single host server regardless if they were running vms with >> volumes on the rebooted nfs server. 95% of my vms are running from ceph and >> those should have never been effected in the first place. >> ----- Original Message - >> >> From: "Koushik Das" >> To: "" >> Cc: d...@cloudstack.apache.org >> Sent: Monday, 3 March, 2014 5:55:34 AM >> Subject: Re: ALARM - ACS reboots host servers!!! >> >> The primary storage needs to be put in maintenance before doing any >> upgrade/reboot as mentioned in the previous mails. >>
Re: ALARM - ACS reboots host servers!!!
Hi Marcus and others. There is no need to kill of the entire hypervisor, if one of the primary storages fail. You just need to kill the VMs and probably disable SR on XenServer, because all other SRs and VMs have no problems. if you kill those, then you can safely start them elsewhere. On XenServer 6.2 you call destroy the VMs which lost access to NFS without any problems. If you really want to still kill the entire host and it's VMs in one go, I would suggest live migrating the VMs which have had not lost their storage off first, and then kill those VMs on a stale NFS by doing hard reboot. Additional time, while migrating working VMs, would even give some grace time for NFS to maybe recover. :-) Hard reboot to recover from D state of NFS client can also be avoided by using soft mount options. I run a bunch of Pacemaker/Corosync/Cman/Heartbeat/etc clusters and we don't just kill whole nodes but fence services from specific nodes. STONITH is implemented only when the node looses the quorum. Regards, F. On 3/3/14 5:35 PM, Marcus wrote: It's the standard clustering problem. Any software that does any sort of avtive clustering is going to fence nodes that have problems, or should if it cares about your data. If the risk of losing a host due to a storage pool outage is too great, you could perhaps look at rearranging your pool-to-host correlations (certain hosts run vms from certain pools) via clusters. Note that if you register a storage pool with a cluster, it will register the pool with libvirt when the pool is not in maintenance, which, when the storage pool goes down will cause problems for the host even if no VMs from that storage are running (fetching storage stats for example will cause agent threads to hang if its NFS), so you'd need to put ceph in its own cluster and NFS in its own cluster. It's far more dangerous to leave a host in an unknown/bad state. If a host loses contact with one of your storage nodes, with HA, cloudstack will want to start the affected VMs elsewhere. If it does so, and your original host wakes up from it's NFS hang, you suddenly have a VM running in two locations, corruption ensues. You might think we could just stop the affected VMs, but NFS tends to make things that touch it go into D state, even with 'intr' and other parameters, which affects libvirt and the agent. We could perhaps open a feature request to disable all HA and just leave things as-is, disallowing operations when there are outages. If that sounds useful you can create the feature request on https://issues.apache.org/jira. On Mon, Mar 3, 2014 at 5:37 AM, Andrei Mikhailovsky wrote: Koushik, I understand that and I will put the storage into the maintenance mode next time. However, things happen and servers crash from time to time, which is not the reason to reboot all host servers, even those which do not have any running vms with volumes on the nfs storage. The bloody agent just rebooted every single host server regardless if they were running vms with volumes on the rebooted nfs server. 95% of my vms are running from ceph and those should have never been effected in the first place. - Original Message - From: "Koushik Das" To: "" Cc: d...@cloudstack.apache.org Sent: Monday, 3 March, 2014 5:55:34 AM Subject: Re: ALARM - ACS reboots host servers!!! The primary storage needs to be put in maintenance before doing any upgrade/reboot as mentioned in the previous mails. -Koushik On 03-Mar-2014, at 6:07 AM, Marcus wrote: Also, please note that in the bug you referenced it doesn't have a problem with the reboot being triggered, but with the fact that reboot never completes due to hanging NFS mount (which is why the reboot occurs, inaccessible primary storage). On Sun, Mar 2, 2014 at 5:26 PM, Marcus wrote: Or do you mean you have multiple primary storages and this one was not in use and put into maintenance? On Sun, Mar 2, 2014 at 5:25 PM, Marcus wrote: I'm not sure I understand. How do you expect to reboot your primary storage while vms are running? It sounds like the host is being fenced since it cannot contact the resources it depends on. On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: On 02.03.2014 21:17, Andrei Mikhailovsky wrote: Hello guys, I've recently came across the bug CLOUDSTACK-5429 which has rebooted all of my host servers without properly shutting down the guest vms. I've simply upgraded and rebooted one of the nfs primary storage servers and a few minutes later, to my horror, i've found out that all of my host servers have been rebooted. Is it just me thinking so, or is this bug should be fixed ASAP and should be a blocker for any new ACS release. I mean not only does it cause downtime, but also possible data loss and server corruption. Hi Andrei, Do you have HA enabled and did you put that primary storage in maintenance mode before rebooting it? It
Re: ALARM - ACS reboots host servers!!!
It's the standard clustering problem. Any software that does any sort of avtive clustering is going to fence nodes that have problems, or should if it cares about your data. If the risk of losing a host due to a storage pool outage is too great, you could perhaps look at rearranging your pool-to-host correlations (certain hosts run vms from certain pools) via clusters. Note that if you register a storage pool with a cluster, it will register the pool with libvirt when the pool is not in maintenance, which, when the storage pool goes down will cause problems for the host even if no VMs from that storage are running (fetching storage stats for example will cause agent threads to hang if its NFS), so you'd need to put ceph in its own cluster and NFS in its own cluster. It's far more dangerous to leave a host in an unknown/bad state. If a host loses contact with one of your storage nodes, with HA, cloudstack will want to start the affected VMs elsewhere. If it does so, and your original host wakes up from it's NFS hang, you suddenly have a VM running in two locations, corruption ensues. You might think we could just stop the affected VMs, but NFS tends to make things that touch it go into D state, even with 'intr' and other parameters, which affects libvirt and the agent. We could perhaps open a feature request to disable all HA and just leave things as-is, disallowing operations when there are outages. If that sounds useful you can create the feature request on https://issues.apache.org/jira. On Mon, Mar 3, 2014 at 5:37 AM, Andrei Mikhailovsky wrote: > > Koushik, I understand that and I will put the storage into the maintenance > mode next time. However, things happen and servers crash from time to time, > which is not the reason to reboot all host servers, even those which do not > have any running vms with volumes on the nfs storage. The bloody agent just > rebooted every single host server regardless if they were running vms with > volumes on the rebooted nfs server. 95% of my vms are running from ceph and > those should have never been effected in the first place. > - Original Message - > > From: "Koushik Das" > To: "" > Cc: d...@cloudstack.apache.org > Sent: Monday, 3 March, 2014 5:55:34 AM > Subject: Re: ALARM - ACS reboots host servers!!! > > The primary storage needs to be put in maintenance before doing any > upgrade/reboot as mentioned in the previous mails. > > -Koushik > > On 03-Mar-2014, at 6:07 AM, Marcus wrote: > >> Also, please note that in the bug you referenced it doesn't have a >> problem with the reboot being triggered, but with the fact that reboot >> never completes due to hanging NFS mount (which is why the reboot >> occurs, inaccessible primary storage). >> >> On Sun, Mar 2, 2014 at 5:26 PM, Marcus wrote: >>> Or do you mean you have multiple primary storages and this one was not >>> in use and put into maintenance? >>> >>> On Sun, Mar 2, 2014 at 5:25 PM, Marcus wrote: >>>> I'm not sure I understand. How do you expect to reboot your primary >>>> storage while vms are running? It sounds like the host is being >>>> fenced since it cannot contact the resources it depends on. >>>> >>>> On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: >>>>> On 02.03.2014 21:17, Andrei Mikhailovsky wrote: >>>>>> >>>>>> Hello guys, >>>>>> >>>>>> >>>>>> I've recently came across the bug CLOUDSTACK-5429 which has rebooted >>>>>> all of my host servers without properly shutting down the guest vms. >>>>>> I've simply upgraded and rebooted one of the nfs primary storage >>>>>> servers and a few minutes later, to my horror, i've found out that all >>>>>> of my host servers have been rebooted. Is it just me thinking so, or >>>>>> is this bug should be fixed ASAP and should be a blocker for any new >>>>>> ACS release. I mean not only does it cause downtime, but also possible >>>>>> data loss and server corruption. >>>>> >>>>> >>>>> Hi Andrei, >>>>> >>>>> Do you have HA enabled and did you put that primary storage in maintenance >>>>> mode before rebooting it? >>>>> It's my understanding that ACS relies on the shared storage to perform HA >>>>> so >>>>> if the storage goes it's expected to go berserk. I've noticed similar >>>>> behaviour in Xenserver pools without ACS. >>>>> I'd imagine a "cure" for this would be to use network distributed >>>>> "filesystems" like GlusterFS or CEPH. >>>>> >>>>> Lucian >>>>> >>>>> -- >>>>> Sent from the Delta quadrant using Borg technology! >>>>> >>>>> Nux! >>>>> www.nux.ro > >
Re: ALARM - ACS reboots host servers!!!
On 03.03.2014 12:37, Andrei Mikhailovsky wrote: Koushik, I understand that and I will put the storage into the maintenance mode next time. However, things happen and servers crash from time to time, which is not the reason to reboot all host servers, even those which do not have any running vms with volumes on the nfs storage. The bloody agent just rebooted every single host server regardless if they were running vms with volumes on the rebooted nfs server. 95% of my vms are running from ceph and those should have never been effected in the first place. It sounds like ACS need to become more aware of multiple primary storages.. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: ALARM - ACS reboots host servers!!!
On 03.03.2014 12:24, Andrei Mikhailovsky wrote: I am using HA for about 30% of the guest vms, but my testing showed that HA is not working reliably with KVM. It works pretty well if you initiate a vm shutdown inside a guest without using the ACS GUI. However, when the host goes down for whatever reason (power failure, init 6/0, network failure, etc.) the HA fails to kick in and restart the vms. This shuld be submitted as a bug. Which version are you on? Regarding the nfs storage, I did not put the nfs server in the maintenance mode. Would this solve the problem with reboots? I will try it next time when I am doing maintenance on the nfs, but I do recall that i've previously restarted the nfs server in the past and I've not seen the hosts rebooting themselves. Is there a timeout which causes the hosts to reboot? Not sure what the timeout is, I'd be interested in finding out as well. To the best of my knowledge, when you put primary storage in m-mode ACS will shut down the VMs on it. Otherwise the shared storage is used by ACS to maintain HA (so your HA is as good as your shared storage ...), if link to the shared storage is down the host assumes something is wrong and shuts down (fences itself), this is the correct and expected behaviour. Maybe your network has segmented etc. In any case, I think it is not safe to do an automated host server reboot and if it was up to me I would disable this feature from the agent. IMHO this should be down to system administrator and acs agent should send an alert email if something goes wrong instead of rebooting the host servers. Not sure what to tell you, HA is a sensitive and complex subject. For now I'm ok with this behaviour and I see it implemented similarly in Xenserver, too. I am using ceph for my primary storage for guest vms data and root disks. The NFS is used as a backup disk offering for the guest. Andrei -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: ALARM - ACS reboots host servers!!!
Koushik, I understand that and I will put the storage into the maintenance mode next time. However, things happen and servers crash from time to time, which is not the reason to reboot all host servers, even those which do not have any running vms with volumes on the nfs storage. The bloody agent just rebooted every single host server regardless if they were running vms with volumes on the rebooted nfs server. 95% of my vms are running from ceph and those should have never been effected in the first place. - Original Message - From: "Koushik Das" To: "" Cc: d...@cloudstack.apache.org Sent: Monday, 3 March, 2014 5:55:34 AM Subject: Re: ALARM - ACS reboots host servers!!! The primary storage needs to be put in maintenance before doing any upgrade/reboot as mentioned in the previous mails. -Koushik On 03-Mar-2014, at 6:07 AM, Marcus wrote: > Also, please note that in the bug you referenced it doesn't have a > problem with the reboot being triggered, but with the fact that reboot > never completes due to hanging NFS mount (which is why the reboot > occurs, inaccessible primary storage). > > On Sun, Mar 2, 2014 at 5:26 PM, Marcus wrote: >> Or do you mean you have multiple primary storages and this one was not >> in use and put into maintenance? >> >> On Sun, Mar 2, 2014 at 5:25 PM, Marcus wrote: >>> I'm not sure I understand. How do you expect to reboot your primary >>> storage while vms are running? It sounds like the host is being >>> fenced since it cannot contact the resources it depends on. >>> >>> On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: >>>> On 02.03.2014 21:17, Andrei Mikhailovsky wrote: >>>>> >>>>> Hello guys, >>>>> >>>>> >>>>> I've recently came across the bug CLOUDSTACK-5429 which has rebooted >>>>> all of my host servers without properly shutting down the guest vms. >>>>> I've simply upgraded and rebooted one of the nfs primary storage >>>>> servers and a few minutes later, to my horror, i've found out that all >>>>> of my host servers have been rebooted. Is it just me thinking so, or >>>>> is this bug should be fixed ASAP and should be a blocker for any new >>>>> ACS release. I mean not only does it cause downtime, but also possible >>>>> data loss and server corruption. >>>> >>>> >>>> Hi Andrei, >>>> >>>> Do you have HA enabled and did you put that primary storage in maintenance >>>> mode before rebooting it? >>>> It's my understanding that ACS relies on the shared storage to perform HA >>>> so >>>> if the storage goes it's expected to go berserk. I've noticed similar >>>> behaviour in Xenserver pools without ACS. >>>> I'd imagine a "cure" for this would be to use network distributed >>>> "filesystems" like GlusterFS or CEPH. >>>> >>>> Lucian >>>> >>>> -- >>>> Sent from the Delta quadrant using Borg technology! >>>> >>>> Nux! >>>> www.nux.ro
Re: ALARM - ACS reboots host servers!!!
Pretty poor, I agree. IMHO the ACS agent should not be allowed to reboot the host server. This is not the type of things you would like to automate as you will eventually end up with broken volumes and data loss. And you are right of course, like what happened in my case. I currently have two vms which used that NFS server for volumes and the rest 50+ vms use ceph. As a result of the nfs server reboot all host servers have rebooted causing 50+ vms to reset without being properly shutdown. I am using ACS 4.2.1 with KVM, so this issue seems to be present on KVM + XenServer. Andrei - Original Message - From: "France" To: users@cloudstack.apache.org Cc: d...@cloudstack.apache.org Sent: Monday, 3 March, 2014 8:49:28 AM Subject: Re: ALARM - ACS reboots host servers!!! I believe this is a bug too, because VMs not running on the storage, get destroyed too: Issue has been around for a long time, like with all others I reported. They do not get fixed: https://issues.apache.org/jira/browse/CLOUDSTACK-3367 We even lost assignee today. Regards, F. On 3/3/14 6:55 AM, Koushik Das wrote: > The primary storage needs to be put in maintenance before doing any > upgrade/reboot as mentioned in the previous mails. > > -Koushik > > On 03-Mar-2014, at 6:07 AM, Marcus wrote: > >> Also, please note that in the bug you referenced it doesn't have a >> problem with the reboot being triggered, but with the fact that reboot >> never completes due to hanging NFS mount (which is why the reboot >> occurs, inaccessible primary storage). >> >> On Sun, Mar 2, 2014 at 5:26 PM, Marcus wrote: >>> Or do you mean you have multiple primary storages and this one was not >>> in use and put into maintenance? >>> >>> On Sun, Mar 2, 2014 at 5:25 PM, Marcus wrote: >>>> I'm not sure I understand. How do you expect to reboot your primary >>>> storage while vms are running? It sounds like the host is being >>>> fenced since it cannot contact the resources it depends on. >>>> >>>> On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: >>>>> On 02.03.2014 21:17, Andrei Mikhailovsky wrote: >>>>>> Hello guys, >>>>>> >>>>>> >>>>>> I've recently came across the bug CLOUDSTACK-5429 which has rebooted >>>>>> all of my host servers without properly shutting down the guest vms. >>>>>> I've simply upgraded and rebooted one of the nfs primary storage >>>>>> servers and a few minutes later, to my horror, i've found out that all >>>>>> of my host servers have been rebooted. Is it just me thinking so, or >>>>>> is this bug should be fixed ASAP and should be a blocker for any new >>>>>> ACS release. I mean not only does it cause downtime, but also possible >>>>>> data loss and server corruption. >>>>> >>>>> Hi Andrei, >>>>> >>>>> Do you have HA enabled and did you put that primary storage in >>>>> maintenance >>>>> mode before rebooting it? >>>>> It's my understanding that ACS relies on the shared storage to perform HA >>>>> so >>>>> if the storage goes it's expected to go berserk. I've noticed similar >>>>> behaviour in Xenserver pools without ACS. >>>>> I'd imagine a "cure" for this would be to use network distributed >>>>> "filesystems" like GlusterFS or CEPH. >>>>> >>>>> Lucian >>>>> >>>>> -- >>>>> Sent from the Delta quadrant using Borg technology! >>>>> >>>>> Nux! >>>>> www.nux.ro
Re: ALARM - ACS reboots host servers!!!
Nux, I am using HA for about 30% of the guest vms, but my testing showed that HA is not working reliably with KVM. It works pretty well if you initiate a vm shutdown inside a guest without using the ACS GUI. However, when the host goes down for whatever reason (power failure, init 6/0, network failure, etc.) the HA fails to kick in and restart the vms. Regarding the nfs storage, I did not put the nfs server in the maintenance mode. Would this solve the problem with reboots? I will try it next time when I am doing maintenance on the nfs, but I do recall that i've previously restarted the nfs server in the past and I've not seen the hosts rebooting themselves. Is there a timeout which causes the hosts to reboot? In any case, I think it is not safe to do an automated host server reboot and if it was up to me I would disable this feature from the agent. IMHO this should be down to system administrator and acs agent should send an alert email if something goes wrong instead of rebooting the host servers. I am using ceph for my primary storage for guest vms data and root disks. The NFS is used as a backup disk offering for the guest. Andrei - Original Message - From: "Nux!" To: users@cloudstack.apache.org Sent: Sunday, 2 March, 2014 10:24:07 PM Subject: Re: ALARM - ACS reboots host servers!!! On 02.03.2014 21:17, Andrei Mikhailovsky wrote: > Hello guys, > > > I've recently came across the bug CLOUDSTACK-5429 which has rebooted > all of my host servers without properly shutting down the guest vms. > I've simply upgraded and rebooted one of the nfs primary storage > servers and a few minutes later, to my horror, i've found out that all > of my host servers have been rebooted. Is it just me thinking so, or > is this bug should be fixed ASAP and should be a blocker for any new > ACS release. I mean not only does it cause downtime, but also possible > data loss and server corruption. Hi Andrei, Do you have HA enabled and did you put that primary storage in maintenance mode before rebooting it? It's my understanding that ACS relies on the shared storage to perform HA so if the storage goes it's expected to go berserk. I've noticed similar behaviour in Xenserver pools without ACS. I'd imagine a "cure" for this would be to use network distributed "filesystems" like GlusterFS or CEPH. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: ALARM - ACS reboots host servers!!!
Hello, This link addresses your issue. https://issues.apache.org/jira/browse/CLOUDSTACK-3367 Amin Sent from my iPad > On Mar 3, 2014, at 1:56 PM, "Koushik Das" wrote: > > The primary storage needs to be put in maintenance before doing any > upgrade/reboot as mentioned in the previous mails. > > -Koushik > >> On 03-Mar-2014, at 6:07 AM, Marcus wrote: >> >> Also, please note that in the bug you referenced it doesn't have a >> problem with the reboot being triggered, but with the fact that reboot >> never completes due to hanging NFS mount (which is why the reboot >> occurs, inaccessible primary storage). >> >>> On Sun, Mar 2, 2014 at 5:26 PM, Marcus wrote: >>> Or do you mean you have multiple primary storages and this one was not >>> in use and put into maintenance? >>> On Sun, Mar 2, 2014 at 5:25 PM, Marcus wrote: I'm not sure I understand. How do you expect to reboot your primary storage while vms are running? It sounds like the host is being fenced since it cannot contact the resources it depends on. > On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: >> On 02.03.2014 21:17, Andrei Mikhailovsky wrote: >> >> Hello guys, >> >> >> I've recently came across the bug CLOUDSTACK-5429 which has rebooted >> all of my host servers without properly shutting down the guest vms. >> I've simply upgraded and rebooted one of the nfs primary storage >> servers and a few minutes later, to my horror, i've found out that all >> of my host servers have been rebooted. Is it just me thinking so, or >> is this bug should be fixed ASAP and should be a blocker for any new >> ACS release. I mean not only does it cause downtime, but also possible >> data loss and server corruption. > > > Hi Andrei, > > Do you have HA enabled and did you put that primary storage in maintenance > mode before rebooting it? > It's my understanding that ACS relies on the shared storage to perform HA > so > if the storage goes it's expected to go berserk. I've noticed similar > behaviour in Xenserver pools without ACS. > I'd imagine a "cure" for this would be to use network distributed > "filesystems" like GlusterFS or CEPH. > > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro >
Re: ALARM - ACS reboots host servers!!!
I believe this is a bug too, because VMs not running on the storage, get destroyed too: Issue has been around for a long time, like with all others I reported. They do not get fixed: https://issues.apache.org/jira/browse/CLOUDSTACK-3367 We even lost assignee today. Regards, F. On 3/3/14 6:55 AM, Koushik Das wrote: The primary storage needs to be put in maintenance before doing any upgrade/reboot as mentioned in the previous mails. -Koushik On 03-Mar-2014, at 6:07 AM, Marcus wrote: Also, please note that in the bug you referenced it doesn't have a problem with the reboot being triggered, but with the fact that reboot never completes due to hanging NFS mount (which is why the reboot occurs, inaccessible primary storage). On Sun, Mar 2, 2014 at 5:26 PM, Marcus wrote: Or do you mean you have multiple primary storages and this one was not in use and put into maintenance? On Sun, Mar 2, 2014 at 5:25 PM, Marcus wrote: I'm not sure I understand. How do you expect to reboot your primary storage while vms are running? It sounds like the host is being fenced since it cannot contact the resources it depends on. On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: On 02.03.2014 21:17, Andrei Mikhailovsky wrote: Hello guys, I've recently came across the bug CLOUDSTACK-5429 which has rebooted all of my host servers without properly shutting down the guest vms. I've simply upgraded and rebooted one of the nfs primary storage servers and a few minutes later, to my horror, i've found out that all of my host servers have been rebooted. Is it just me thinking so, or is this bug should be fixed ASAP and should be a blocker for any new ACS release. I mean not only does it cause downtime, but also possible data loss and server corruption. Hi Andrei, Do you have HA enabled and did you put that primary storage in maintenance mode before rebooting it? It's my understanding that ACS relies on the shared storage to perform HA so if the storage goes it's expected to go berserk. I've noticed similar behaviour in Xenserver pools without ACS. I'd imagine a "cure" for this would be to use network distributed "filesystems" like GlusterFS or CEPH. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: ALARM - ACS reboots host servers!!!
The primary storage needs to be put in maintenance before doing any upgrade/reboot as mentioned in the previous mails. -Koushik On 03-Mar-2014, at 6:07 AM, Marcus wrote: > Also, please note that in the bug you referenced it doesn't have a > problem with the reboot being triggered, but with the fact that reboot > never completes due to hanging NFS mount (which is why the reboot > occurs, inaccessible primary storage). > > On Sun, Mar 2, 2014 at 5:26 PM, Marcus wrote: >> Or do you mean you have multiple primary storages and this one was not >> in use and put into maintenance? >> >> On Sun, Mar 2, 2014 at 5:25 PM, Marcus wrote: >>> I'm not sure I understand. How do you expect to reboot your primary >>> storage while vms are running? It sounds like the host is being >>> fenced since it cannot contact the resources it depends on. >>> >>> On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: On 02.03.2014 21:17, Andrei Mikhailovsky wrote: > > Hello guys, > > > I've recently came across the bug CLOUDSTACK-5429 which has rebooted > all of my host servers without properly shutting down the guest vms. > I've simply upgraded and rebooted one of the nfs primary storage > servers and a few minutes later, to my horror, i've found out that all > of my host servers have been rebooted. Is it just me thinking so, or > is this bug should be fixed ASAP and should be a blocker for any new > ACS release. I mean not only does it cause downtime, but also possible > data loss and server corruption. Hi Andrei, Do you have HA enabled and did you put that primary storage in maintenance mode before rebooting it? It's my understanding that ACS relies on the shared storage to perform HA so if the storage goes it's expected to go berserk. I've noticed similar behaviour in Xenserver pools without ACS. I'd imagine a "cure" for this would be to use network distributed "filesystems" like GlusterFS or CEPH. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: ALARM - ACS reboots host servers!!!
Also, please note that in the bug you referenced it doesn't have a problem with the reboot being triggered, but with the fact that reboot never completes due to hanging NFS mount (which is why the reboot occurs, inaccessible primary storage). On Sun, Mar 2, 2014 at 5:26 PM, Marcus wrote: > Or do you mean you have multiple primary storages and this one was not > in use and put into maintenance? > > On Sun, Mar 2, 2014 at 5:25 PM, Marcus wrote: >> I'm not sure I understand. How do you expect to reboot your primary >> storage while vms are running? It sounds like the host is being >> fenced since it cannot contact the resources it depends on. >> >> On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: >>> On 02.03.2014 21:17, Andrei Mikhailovsky wrote: Hello guys, I've recently came across the bug CLOUDSTACK-5429 which has rebooted all of my host servers without properly shutting down the guest vms. I've simply upgraded and rebooted one of the nfs primary storage servers and a few minutes later, to my horror, i've found out that all of my host servers have been rebooted. Is it just me thinking so, or is this bug should be fixed ASAP and should be a blocker for any new ACS release. I mean not only does it cause downtime, but also possible data loss and server corruption. >>> >>> >>> Hi Andrei, >>> >>> Do you have HA enabled and did you put that primary storage in maintenance >>> mode before rebooting it? >>> It's my understanding that ACS relies on the shared storage to perform HA so >>> if the storage goes it's expected to go berserk. I've noticed similar >>> behaviour in Xenserver pools without ACS. >>> I'd imagine a "cure" for this would be to use network distributed >>> "filesystems" like GlusterFS or CEPH. >>> >>> Lucian >>> >>> -- >>> Sent from the Delta quadrant using Borg technology! >>> >>> Nux! >>> www.nux.ro
Re: ALARM - ACS reboots host servers!!!
I'm not sure I understand. How do you expect to reboot your primary storage while vms are running? It sounds like the host is being fenced since it cannot contact the resources it depends on. On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: > On 02.03.2014 21:17, Andrei Mikhailovsky wrote: >> >> Hello guys, >> >> >> I've recently came across the bug CLOUDSTACK-5429 which has rebooted >> all of my host servers without properly shutting down the guest vms. >> I've simply upgraded and rebooted one of the nfs primary storage >> servers and a few minutes later, to my horror, i've found out that all >> of my host servers have been rebooted. Is it just me thinking so, or >> is this bug should be fixed ASAP and should be a blocker for any new >> ACS release. I mean not only does it cause downtime, but also possible >> data loss and server corruption. > > > Hi Andrei, > > Do you have HA enabled and did you put that primary storage in maintenance > mode before rebooting it? > It's my understanding that ACS relies on the shared storage to perform HA so > if the storage goes it's expected to go berserk. I've noticed similar > behaviour in Xenserver pools without ACS. > I'd imagine a "cure" for this would be to use network distributed > "filesystems" like GlusterFS or CEPH. > > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro
Re: ALARM - ACS reboots host servers!!!
Or do you mean you have multiple primary storages and this one was not in use and put into maintenance? On Sun, Mar 2, 2014 at 5:25 PM, Marcus wrote: > I'm not sure I understand. How do you expect to reboot your primary > storage while vms are running? It sounds like the host is being > fenced since it cannot contact the resources it depends on. > > On Sun, Mar 2, 2014 at 3:24 PM, Nux! wrote: >> On 02.03.2014 21:17, Andrei Mikhailovsky wrote: >>> >>> Hello guys, >>> >>> >>> I've recently came across the bug CLOUDSTACK-5429 which has rebooted >>> all of my host servers without properly shutting down the guest vms. >>> I've simply upgraded and rebooted one of the nfs primary storage >>> servers and a few minutes later, to my horror, i've found out that all >>> of my host servers have been rebooted. Is it just me thinking so, or >>> is this bug should be fixed ASAP and should be a blocker for any new >>> ACS release. I mean not only does it cause downtime, but also possible >>> data loss and server corruption. >> >> >> Hi Andrei, >> >> Do you have HA enabled and did you put that primary storage in maintenance >> mode before rebooting it? >> It's my understanding that ACS relies on the shared storage to perform HA so >> if the storage goes it's expected to go berserk. I've noticed similar >> behaviour in Xenserver pools without ACS. >> I'd imagine a "cure" for this would be to use network distributed >> "filesystems" like GlusterFS or CEPH. >> >> Lucian >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro
Re: ALARM - ACS reboots host servers!!!
On 02.03.2014 21:17, Andrei Mikhailovsky wrote: Hello guys, I've recently came across the bug CLOUDSTACK-5429 which has rebooted all of my host servers without properly shutting down the guest vms. I've simply upgraded and rebooted one of the nfs primary storage servers and a few minutes later, to my horror, i've found out that all of my host servers have been rebooted. Is it just me thinking so, or is this bug should be fixed ASAP and should be a blocker for any new ACS release. I mean not only does it cause downtime, but also possible data loss and server corruption. Hi Andrei, Do you have HA enabled and did you put that primary storage in maintenance mode before rebooting it? It's my understanding that ACS relies on the shared storage to perform HA so if the storage goes it's expected to go berserk. I've noticed similar behaviour in Xenserver pools without ACS. I'd imagine a "cure" for this would be to use network distributed "filesystems" like GlusterFS or CEPH. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
ALARM - ACS reboots host servers!!!
Hello guys, I've recently came across the bug CLOUDSTACK-5429 which has rebooted all of my host servers without properly shutting down the guest vms. I've simply upgraded and rebooted one of the nfs primary storage servers and a few minutes later, to my horror, i've found out that all of my host servers have been rebooted. Is it just me thinking so, or is this bug should be fixed ASAP and should be a blocker for any new ACS release. I mean not only does it cause downtime, but also possible data loss and server corruption. Not sure if one can wait for another year or so until 4.4 is out which may or may not have the fix for this serious issue. From the bug report it seems that this problem is assigned to Edison Su. Edison, could you please get in touch to discuss a possible temporary fix to this problem as this is causing a number of issues. Does anyone know if you can block the reboot request initiated by the cloudstack agent on the OS level? Many thanks for any help Andrei
