- **status**: review --> fixed
- **Comment**:
changeset: 8727:9a1452dcd190
branch: opensaf-5.0.x
parent: 8721:b2e2a9162664
user:Praveen Malviya
date:Tue Mar 28 12:19:02 2017 +0530
summary: amf: fix track callback when multiple CLM nodes leaves
membership[#2372].
- **status**: assigned --> duplicate
- **Milestone**: 5.2.RC2 --> future
---
** [tickets:#2371] AMF: NPM app went into unstable state while expanding
cluster**
**Status:** duplicate
**Milestone:** future
**Created:** Tue Mar 14, 2017 08:03 AM UTC by Chani Srivastava
**Last Updated:** Fri Mar
Mar 13 01:12:00 SUSE-S1-C2 osafamfd[2192]: NO got si
:safSi=TestApp_SI1,safApp=TestApp_TwoN
Mar 13 01:12:00 SUSE-S1-C2 osafamfd[2192]: NO got si
:safSi=TestApp_SI1,safApp=TestApp_TwoN
Mar 13 01:12:00 SUSE-S1-C2 osafamfd[2192]: NO got si
:safSi=TestApp_SI1,safApp=TestApp_TwoN
The syslog does not
- **status**: accepted --> review
---
** [tickets:#2399] log: unit test failed due to not updating new rfc5424 msgid
handling**
**Status:** review
**Milestone:** 5.2.RC2
**Created:** Mon Mar 27, 2017 02:22 PM UTC by Vu Minh Nguyen
**Last Updated:** Mon Mar 27, 2017 02:22 PM UTC
**Owner:** Vu
---
** [tickets:#2399] log: unit test failed due to not updating new rfc5424 msgid
handling**
**Status:** accepted
**Milestone:** 5.2.RC2
**Created:** Mon Mar 27, 2017 02:22 PM UTC by Vu Minh Nguyen
**Last Updated:** Mon Mar 27, 2017 02:22 PM UTC
**Owner:** Vu Minh Nguyen
The RFC5424 msgid
In safLog, the first appearance of "Sg unstable" started from:
5166 17:14:29 03/13/2017 NO safApp=safAmfService "Admin op "LOCK"
initiated for 'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN',
invocation: 1421634174977"
5167 17:14:29 03/13/2017 NO safApp=safAmfService "Admin
- **status**: assigned --> duplicate
- **Part**: - --> d
- **Milestone**: 5.2.RC2 --> 5.0.2
- **Comment**:
Problem is fixed in #2325. Please raise a new ticket with traces and logs if
still observed.
---
** [tickets:#2320] clm: standby clmd crashes due to missing node information**
**Statu
- **status**: unassigned --> assigned
- **assigned_to**: Praveen
---
** [tickets:#2320] clm: standby clmd crashes due to missing node information**
**Status:** assigned
**Milestone:** 5.2.RC2
**Created:** Wed Feb 22, 2017 12:55 PM UTC by Zoran Milinkovic
**Last Updated:** Fri Feb 24, 2017 10:0
- **summary**: amf/clm: CLM lock of two more nodes returns REPAIR_PENDING for
first node. --> amf: CLM lock of two more nodes returns REPAIR_PENDING for
first node.
---
** [tickets:#2372] amf: CLM lock of two more nodes returns REPAIR_PENDING for
first node.**
**Status:** review
**Milestone
- **status**: accepted --> review
---
** [tickets:#2372] amf/clm: CLM lock of two more nodes returns REPAIR_PENDING
for first node.**
**Status:** review
**Milestone:** 5.0.2
**Created:** Tue Mar 14, 2017 09:29 AM UTC by Praveen
**Last Updated:** Thu Mar 23, 2017 09:16 AM UTC
**Owner:** Pravee
The problem here is to avoid newccbid when the old ccbid is not finalized when
saImmOmCcbAbort is called.
If the TIMEOUT is returned, then the agent may re-try saImmOmCcbAbort, to avoid
old ccb not finalized. If the old ccb is finaized, then server will return
BD_HANDLE, which is converted to S
TRY_AGAIN ok.
But ERR_TIMEOUT ? Not sure what you are doing here.
The two error codes are different in meaning.
TRY_AGAIN means the client KNOWS that the call was NOT processed.
TIMEOUT mens the client does NOT KNOW if the call was processed in the server
or not.
TIMEOUT may be (is typically
- **summary**: imm: retry of cbb abort should be allowed if failed with
TRY_AGAIN and TIMEOUT --> imm: retry of ccb abort should be allowed if failed
with TRY_AGAIN and TIMEOUT
- **status**: accepted --> review
---
** [tickets:#2398] imm: retry of ccb abort should be allowed if failed with
T
---
** [tickets:#2398] imm: retry of cbb abort should be allowed if failed with
TRY_AGAIN and TIMEOUT**
**Status:** accepted
**Milestone:** 5.0.2
**Created:** Mon Mar 27, 2017 07:50 AM UTC by Neelakanta Reddy
**Last Updated:** Mon Mar 27, 2017 07:50 AM UTC
**Owner:** Neelakanta Reddy
steps
Performance degrade of cpsv expected because of #2202 , we agreed to have
performance degrade in default configuration to address #2202 , if user what
to natural performance OSAF_CKPT_SHM_ALLOC_GUARANTEE is set to true cpsv give
natural performance.
==
- **status**: unassigned --> assigned
- **assigned_to**: A V Mahesh (AVM)
---
** [tickets:#2395] CKPT: Performance degradation upto 200%**
**Status:** assigned
**Milestone:** 5.2.RC2
**Created:** Thu Mar 23, 2017 10:26 AM UTC by Chani Srivastava
**Last Updated:** Mon Mar 27, 2017 07:04 AM UTC
16 matches
Mail list logo
