cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fuchs, Andreas (SwissTXT)" <Andreas.Fu...@swisstxt.ch>
Subject RE: Issues when vCenter becomes unavailable
Date Fri, 22 Feb 2013 15:05:50 GMT
What we learned so far is, that vCenter needs tob e offline for a certain ammount of time (10-15
minutes), if you just restart vCenter service it won't happen.

Would be great if you can verify.

Regards
Andi

-----Original Message-----
From: Musayev, Ilya [mailto:imusayev@webmd.net] 
Sent: Donnerstag, 21. Februar 2013 20:43
To: cloudstack-users@incubator.apache.org
Subject: RE: Issues when vCenter becomes unavailable

This is definitely not the behavior we want with vcenter.

I will test this out on my lab setup shortly.

Thanks
ilya

-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: Thursday, February 21, 2013 9:40 AM
To: cloudstack-users@incubator.apache.org
Subject: Re: Issues when vCenter becomes unavailable

On Thu, Feb 21, 2013 at 08:59:14AM -0500, Mathias Mullins wrote:
> Andreas,
> 
> The open source community doesn't support the Citrix version 3.0.6. 
> You need to report this via your Citrix Support contract. Sounds like 
> this could be a bug.
> 
> Community - this could be a possible issue in 4.0.0 / 4.0.1. I don't 
> know if this test case has been explored.

Thx - I forwarded to cs-dev@i.a.o to get the test engineers in the community to take a look.

> 
> Thanks,
> Matt Mullins
> CloudPlatform Implementation Engineer
> Worldwide Cloud Services  Citrix System, Inc.
> +1 (407) 920-1107  Office/Cell Phone
> matt.mullins@citrix.com
> 
> 
> 
> On 2/21/13 5:35 AM, "Fuchs, Andreas (SwissTXT)"
> <Andreas.Fuchs@swisstxt.ch> wrote:
> 
> >Hi CS Users
> >
> >We are running CS 3.0.6 on a vSphere platform and found a strange 
> >behavior.
> >
> >When the vCenter becomes unavailable due to a reboot or some other 
> >issue, it seems that CS is shutting down instances when vCenter 
> >becomes available again.
> >
> >What we think what happens.
> >1. vCenter becomes unrechabale
> >2. CS marks the ESX servers as "down"
> >3. We think this leads to: CS marks the instances as down as well 4. 
> >When vCenter becomes available again, CS stops the "marked as down"
> >instances
> >
> >This is very bad as the Instances where running all the time and the 
> >the shutdown issued by CS is forcing a service interruption.
> >
> >My problem is that I cannot realy reporoduce as allot of testing is 
> >ongoing on the platform at the moment, so my question:
> >
> >Does someone else see this issue as well and can maybe reproduce?
> >Is there a workaround to it, can I change some flag or something 
> >which tells CS to never shut down an instance by himself?
> >Why are the ESX hosts getting marked as down and not unreachable or 
> >something?
> >
> >Best regards
> >Andi
> 
> 



Mime
View raw message