Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; c=simple; d=isg.si; h=message-id:date
	:from:mime-version:to:cc:subject:references:in-reply-to
	:content-type:content-transfer-encoding; q=dns; s=postfix; b=KDV
	qr4ePNmI75e8vWG4fSibKZPdZsDwJKDJL2ePjY21QnynkNXQfcmN+NfOcFLHoGSk
	5psleiio021bNMWLu4f5mSO2pq+3IY+w7V8nn2AQqwbwdB9HJcYNB4XMVvQGwR7Q
	HhBBT2aSY/Hc12w/e+k+wxPvtbhWOMC1AVhVsGRw=
Message-ID: <53144218.9010003@isg.si>
Date: Mon, 03 Mar 2014 09:49:28 +0100
From: France <mailinglists@isg.si>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: users@cloudstack.apache.org
CC: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Subject: Re: ALARM - ACS reboots host servers!!!
References: <1724453607.446410.1393795068840.JavaMail.root@arhont.com>
 <9d23151db92008badff8842985b16fad@li.nux.ro>
 <CALFpzo6PbxsUHwfDU31+FPhEqHJLrDBJJeTLHqz_0wTFhx4LHQ@mail.gmail.com>
 <CALFpzo5z8hhnyOYC1SPg934WdHx9hYrxfZi4TuZz_KpJfUbGxw@mail.gmail.com>
 <CALFpzo6GbLtQ3ir6SU6S+gT9=2zm+SOvN-=qAgkLsfqvCPGWSw@mail.gmail.com>
 <8E7010B5-FC65-4DA4-B7AE-7F991D534407@citrix.com>
In-Reply-To: <8E7010B5-FC65-4DA4-B7AE-7F991D534407@citrix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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 <shadowsor@gmail.com> 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 <shadowsor@gmail.com> 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 <shadowsor@gmail.com> 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! <nux@li.nux.ro> 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