On Thu, Feb 21, 2013 at 06:47:22AM -0800, Sudha Ponnaganti wrote: > I am sure this must have been covered as part of 3.0.6. Will go through > internal escalation process if a case has been logged. > However I will get this checked out for ACS 4x version and will post the > results.
Great, thanks Sudha! > > -----Original Message----- > From: Chip Childers [mailto:[email protected]] > Sent: Thursday, February 21, 2013 6:39 AM > To: [email protected] > Subject: [QA] VMware HV Plugin Testing Question (Re: Issues when vCenter > becomes unavailable) > > Forward from the user list, hoping to catch the Citrix test engineering > team's attention. Is this a tested scenario? > > -chip > > ----- Forwarded message from Mathias Mullins <[email protected]> > ----- > > Date: Thu, 21 Feb 2013 08:59:14 -0500 > From: Mathias Mullins <[email protected]> > To: "[email protected]" > <[email protected]> > Subject: Re: Issues when vCenter becomes unavailable > Reply-To: [email protected] > Message-ID: <cd4b90cd.9884%[email protected]> > > 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. > > Thanks, > Matt Mullins > CloudPlatform Implementation Engineer > Worldwide Cloud Services Citrix System, Inc. > +1 (407) 920-1107 Office/Cell Phone > [email protected] > > > > On 2/21/13 5:35 AM, "Fuchs, Andreas (SwissTXT)" > <[email protected]> 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 > > > > ----- End forwarded message ----- >
