If you get this issue continuously, can you please share the logs against master as we have improved some logs in the master yesterday?
Thanks, Reka On Thu, Apr 30, 2015 at 2:08 PM, Reka Thirunavukkarasu <[email protected]> wrote: > Hi Martin, > > I have deployed the attached samples as earlier in openstack with latest > master. All the clusters got created with the members. Please see the > attached diagram. I'm unable to proceed further as my puppet configuration > has to be corrected to make the member active. Thought of sharing this as > all the clusters have members. > > Thanks, > Reka > > On Thu, Apr 30, 2015 at 10:25 AM, Reka Thirunavukkarasu <[email protected]> > wrote: > >> HI Martin, >> >> Can you please confirm whether you are using unique applicationId and >> group alias? I can see from the UI, the applicationID and next group alias >> are same value as sub-G1-G2-G3-1.. >> >> Thanks, >> Reka >> >> >> On Thu, Apr 30, 2015 at 10:16 AM, Martin Eppel (meppel) <[email protected] >> > wrote: >> >>> Hi Reka, >>> >>> >>> >>> I have upgraded from beta to the latest stratos code on master and >>> retested the scenario from jira STRATOS-1345 but still see the same issue >>> (on open stack) >>> >>> >>> >>> Thanks >>> >>> >>> >>> Martin >>> >>> >>> >>> >>> >>> *From:* Martin Eppel (meppel) >>> *Sent:* Wednesday, April 29, 2015 2:54 PM >>> *To:* [email protected] >>> *Subject:* RE: Testing Stratos 4.1 : nested grouping scenario with >>> startup and termination issues (?) >>> >>> >>> >>> Hi Reka, >>> >>> >>> >>> I will upgrade my system to the latest master and re-test, >>> >>> >>> >>> Regards >>> >>> >>> >>> Martin >>> >>> >>> >>> *From:* Reka Thirunavukkarasu [mailto:[email protected] <[email protected]>] >>> *Sent:* Wednesday, April 29, 2015 11:55 AM >>> *To:* dev >>> *Subject:* Re: Testing Stratos 4.1 : nested grouping scenario with >>> startup and termination issues (?) >>> >>> >>> >>> Hi Martin, >>> >>> While i was working on Application update, i fixed few issues with the >>> termination behavior. Anyway there seems to be small issues in the logic >>> which has to be fixed. I have started to verify this in my local setup. Can >>> you create a jira? So that we can track it. I will update the progress in >>> the jira.. >>> >>> Thanks, >>> >>> Reka >>> >>> >>> >>> On Tue, Apr 28, 2015 at 10:11 PM, Martin Eppel (meppel) < >>> [email protected]> wrote: >>> >>> Hi Reka, >>> >>> >>> >>> Thanks for following up - let me know if I should open a JIRA, >>> >>> >>> >>> Thanks >>> >>> >>> >>> Martin >>> >>> >>> >>> *From:* Reka Thirunavukkarasu [mailto:[email protected]] >>> *Sent:* Tuesday, April 28, 2015 5:37 AM >>> *To:* dev >>> *Subject:* Re: Testing Stratos 4.1 : nested grouping scenario with >>> startup and termination issues (?) >>> >>> >>> >>> Hi Martin, >>> >>> Thanks for bringing this up. I have fixed some issue in the flow while >>> testing application update support with instances count. I will go through >>> your scenarios to reproduce it and update the thread with the progress.. >>> >>> Thanks, >>> >>> Reka >>> >>> >>> >>> On Tue, Apr 28, 2015 at 7:08 AM, Martin Eppel (meppel) <[email protected]> >>> wrote: >>> >>> I am testing a (nested grouping) scenario where a group defines a >>> termination behavior “terminate-all”. When terminating the instance (of >>> cartridge type c3), no new instance is restarted. >>> >>> My understanding is that a new instance should be started up. >>> >>> >>> >>> The scenario looks like this: >>> >>> >>> >>> Group ~G1 has a cartridge member c1 and group member ~G2 >>> >>> Group ~G2 has a cartridge member c2 and group member ~G3 >>> >>> Group ~G3 has a cartridge member c3 >>> >>> >>> >>> Startup dependencies are: c1 depends on G2, c2 depends on G3 >>> >>> >>> >>> ~G1 defines termination: none >>> >>> ~G2 defines termination: dependents >>> >>> ~G3 defines termination: all >>> >>> >>> >>> After startup, when all instances are active, instance c3 is terminated >>> which correctly also terminates also instance c2 (since it depends on G3 / >>> c3) . >>> >>> *Issue 1:* >>> >>> However, no new instances for c3 is started up (consequently no new >>> instance for c2 should be started up as well) (see log see log >>> wso2carbon.log) >>> >>> >>> >>> Only instance which remains running is c1. >>> >>> *Issue 2:* >>> >>> When subsequently c1 is manually being terminated, a new instance of c1 >>> is started up (as opposed to Issue1) which I think is incorrect since it >>> defines a startup dependency (c1 depends on G2) which is not fulfilled at >>> the time (G2 should not be active since c2 is still terminated, see log >>> wso2carbon-issue2.log, same log as wso2carbon.log but at a later time) >>> >>> >>> >>> WDYT ? >>> >>> >>> >>> Please find attached artifacts and logs >>> >>> >>> >>> Thanks >>> >>> >>> >>> Martin >>> >>> >>> >>> >>> -- >>> >>> Reka Thirunavukkarasu >>> Senior Software Engineer, >>> WSO2, Inc.:http://wso2.com, >>> >>> Mobile: +94776442007 >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Reka Thirunavukkarasu >>> Senior Software Engineer, >>> WSO2, Inc.:http://wso2.com, >>> >>> Mobile: +94776442007 >>> >>> >>> >> >> >> >> -- >> Reka Thirunavukkarasu >> Senior Software Engineer, >> WSO2, Inc.:http://wso2.com, >> Mobile: +94776442007 >> >> >> > > > -- > Reka Thirunavukkarasu > Senior Software Engineer, > WSO2, Inc.:http://wso2.com, > Mobile: +94776442007 > > > -- Reka Thirunavukkarasu Senior Software Engineer, WSO2, Inc.:http://wso2.com, Mobile: +94776442007
