Hi Nagu,
Attached patch is for TC 41, 42.
We have noticed one bug in sidep, will update it soon.
Thanks,
Minh
On 22/02/16 23:48, Hans Nordebäck wrote:
Hi,
please see enclosed patch for TC #1, #6, #7, #8, #9, #10 and
#11/Thanks HansN
On 02/19/2016 10:09 AM, minh chau wrote:
Hi Nagu,
Hi,
please see enclosed patch for TC #1, #6, #7, #8, #9, #10 and #11/Thanks
HansN
On 02/19/2016 10:09 AM, minh chau wrote:
Hi Nagu,
Thanks for your testing.
Below is our investigation from TC1 - TC31 which seem to be important,
plus some patches that we're trying to fix the issues
1. IMM
It seems the file wasn't attached properly. Take #2.
Quoting Gary Lee :
Hi Nagu
Please ignore fix.patch Minh previously sent, and replace with this version.
Thanks
Gary
On 19 Feb 2016, at 8:09 PM, minh chau wrote:
Hi Nagu,
Thanks for
Hi Nagu
Please ignore fix.patch Minh previously sent, and replace with this version.
Thanks
Gary
> On 19 Feb 2016, at 8:09 PM, minh chau wrote:
>
> Hi Nagu,
>
> Thanks for your testing.
> Below is our investigation from TC1 - TC31 which seem to be important, plus
Hi Minh,
I thought traces should be ok, so I didn't uploaded the
configuration file. I will upload it going forward.
Thanks
-Nagu
> -Original Message-
> From: minh chau [mailto:minh.c...@dektech.com.au]
> Sent: 15 February 2016 14:27
> To: Nagendra Kumar; Gary Lee
> Cc:
Hi Nagu,
One thing that can help us to reproduce your problems, that can you
attach to the ticket the models you are using for test?
Thanks,
Minh
On 15/02/16 19:32, Nagendra Kumar wrote:
> Hi Gary,
> I am using the patch tar sent by Minh(9 Feb on devel list) and I using
> these on same
Hi Nagu
I think we need to make sure we’re all looking at the same source code.
I have trouble recreating some of the problems you’ve seen, but I see other
problems.
Perhaps we can set up a fork of opensaf-staging on source forge, and check in
the patches?
Thanks
Gary
> On 15 Feb 2016, at
Hi Gary,
Yes, you are right. I attach gdb in amf_demo process only.
Thanks
-Nagu
> -Original Message-
> From: Gary Lee [mailto:gary@dektech.com.au]
> Sent: 15 February 2016 10:30
> To: Nagendra Kumar
> Cc: minh chau; hans.nordeb...@ericsson.com; Praveen Malviya; opensaf-
>
Hi Nagu
Just wanted to confirm that when you attach gdb to a process, the process is
amf_demo, and not amfnd?
Thanks
Gary
> On 13 Feb 2016, at 1:35 AM, Nagendra Kumar wrote:
>
> TC #27: Same configuration as TC #24:
> Add a new Csi in running demo appl: Keep gdb in SU1
Hi Minh,
Doing some sanity testing and I am observing below problems:
1 controller and 1 payload. SU1 is hosted on payload PL-3.
1. Issue shutdown on SU1 and stop the controller. Start controller, Amfd
is crashing and controller is not able to come up:
Feb 5 13:51:08 PM_SC-1
Hi Minh,
While testing backward compatibility with older branches, I
found that Standby Amfd(not configured with
IMMSV_SC_ABSENCE_ALLOWED) is not coming up:
Feb 4 14:36:52 PM_SC-2 osafamfd[32168]: Started Feb 4 14:36:53 PM_SC-2
osafimmnd[32118]: NO SearchInit ERR_INVALID_PARAM:
Hi Nagu,
Can you describe your backward compatibility test case?
It looks to me that the new attr saAmfUnassignedAlarmStatus was not
added to IMM while standby amfd was running cloud resilience version
Thanks,
Minh
On 04/02/16 20:08, Nagendra Kumar wrote:
> Hi Minh,
> While
Hi Minh,
While testing backward compatibility with older branches, I
found that Standby Amfd(not configured with IMMSV_SC_ABSENCE_ALLOWED) is not
coming up:
Feb 4 14:36:52 PM_SC-2 osafamfd[32168]: Started
Feb 4 14:36:53 PM_SC-2 osafimmnd[32118]: NO SearchInit
13 matches
Mail list logo