- **status**: review --> fixed
---
** [tickets:#3328] mds: valgrind reports errors**
**Status:** fixed
**Milestone:** 5.23.03
**Created:** Mon Dec 05, 2022 07:57 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Dec 27, 2022 04:34 AM UTC
**Owner:** Hieu Hong Hoang
**Valgrind command:**
```
commit 48da9255afcb3899a44e3a1d5ee68c075a15c23f (HEAD -> develop,
origin/develop, ticket-3328)
Author: hieu.h.hoang
Date: Tue Dec 6 12:45:43 2022 +0700
mds: Fix errors reported by valgrind [#3328]
Valgrind reports some errors while running mdstest. This ticket
will fix the
- **status**: review --> fixed
---
** [tickets:#2798] mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6
failed**
**Status:** fixed
**Milestone:** future
**Created:** Wed Mar 07, 2018 04:19 AM UTC by Hoa Le
**Last Updated:** Mon Dec 19, 2022 01:46 AM UTC
**Owner:** Hieu Hong Hoang
commit db861cc07e61330bf0c1686869b18e33d302f255 (HEAD -> develop,
origin/develop, ticket-2798)
Author: hieu.h.hoang
Date: Wed Nov 30 08:27:05 2022 +0700
mds: Fix failed test cases in mdstest [#2798]
A number of test cases are failed because it retrieved the event without
polling
- Description has changed:
Diff:
--- old
+++ new
@@ -139,9 +139,9 @@
==732== by 0x50AA7AE: mdtm_process_recv_events_tcp (mds_dt_trans.c:995)
==732== by 0x52EC6DA: start_thread (pthread_create.c:463)
==732== by 0x562561E: clone (clone.S:95)
-~~~
+```
6) Definitely lost:
-~~~
- **status**: accepted --> review
---
** [tickets:#3328] mds: valgrind reports errors**
**Status:** review
**Milestone:** 5.23.03
**Created:** Mon Dec 05, 2022 07:57 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Dec 06, 2022 03:04 AM UTC
**Owner:** Hieu Hong Hoang
**Valgrind command:**
- **status**: assigned --> accepted
---
** [tickets:#3328] mds: valgrind reports errors**
**Status:** accepted
**Milestone:** 5.23.03
**Created:** Mon Dec 05, 2022 07:57 AM UTC by Hieu Hong Hoang
**Last Updated:** Mon Dec 05, 2022 07:57 AM UTC
**Owner:** Hieu Hong Hoang
**Valgrind
- **status**: accepted --> review
---
** [tickets:#2798] mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6
failed**
**Status:** review
**Milestone:** future
**Created:** Wed Mar 07, 2018 04:19 AM UTC by Hoa Le
**Last Updated:** Tue Dec 06, 2022 02:33 AM UTC
**Owner:** Hieu Hong Hoang
This is a known problem where we retrieve the event without polling the select
object. It's the same as ticket #3249.
---
** [tickets:#2798] mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6
failed**
**Status:** accepted
**Milestone:** future
**Created:** Wed Mar 07, 2018 04:19 AM UTC
- **status**: assigned --> accepted
---
** [tickets:#2798] mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6
failed**
**Status:** accepted
**Milestone:** future
**Created:** Wed Mar 07, 2018 04:19 AM UTC by Hoa Le
**Last Updated:** Mon Dec 05, 2022 03:39 AM UTC
**Owner:** Hieu Hong
---
** [tickets:#3328] mds: valgrind reports errors**
**Status:** assigned
**Milestone:** 5.23.03
**Created:** Mon Dec 05, 2022 07:57 AM UTC by Hieu Hong Hoang
**Last Updated:** Mon Dec 05, 2022 07:57 AM UTC
**Owner:** Hieu Hong Hoang
**Valgrind command:**
```
export MDS_LOG_LEVEL=5;
- **status**: assigned --> duplicate
---
** [tickets:#2174] MDS: mdstest 5 1 failed**
**Status:** duplicate
**Milestone:** 5.2.RC2
**Created:** Tue Nov 08, 2016 06:29 AM UTC by Quyen Dao
**Last Updated:** Mon Dec 05, 2022 03:43 AM UTC
**Owner:** Hieu Hong Hoang
**Attachments:**
-
This ticket is duplicate of ticket #2798
---
** [tickets:#2174] MDS: mdstest 5 1 failed**
**Status:** assigned
**Milestone:** 5.2.RC2
**Created:** Tue Nov 08, 2016 06:29 AM UTC by Quyen Dao
**Last Updated:** Mon Nov 14, 2022 09:16 AM UTC
**Owner:** Hieu Hong Hoang
**Attachments:**
-
- **status**: review --> assigned
- **assigned_to**: Hoa Le --> Hieu Hong Hoang
---
** [tickets:#2798] mds: mdstest 5 1,5 9, 4 10, 4 12, 10 1, 10 2, 14 5, 14 6
failed**
**Status:** assigned
**Milestone:** future
**Created:** Wed Mar 07, 2018 04:19 AM UTC by Hoa Le
**Last Updated:** Tue Sep
- **status**: review --> fixed
---
** [tickets:#3322] log: log agent in main process is disabled after child
process exits**
**Status:** fixed
**Milestone:** 5.23.03
**Created:** Wed Oct 05, 2022 09:36 AM UTC by Hieu Hong Hoang
**Last Updated:** Fri Nov 25, 2022 07:21 AM UTC
**Owner:** Hieu
commit 4e1b84f156bd23965b706784a1ebd7ad0b5b4cfc (HEAD -> develop,
origin/develop, ticket-3322)
Author: hieu.h.hoang
Date: Thu Nov 17 14:08:21 2022 +0700
log: Testcase for closing log stream in destructor [#3322]
Add a testcase for closing log stream in the destructor of a cpp object.
The test is always failed now. This is a known problem where we retrieve the
event without polling the select object. If the mds service is installed with
the flag i_mds_q_ownership, we must poll the select object to know that some
messages are arrived. It's the same as ticket-3249.
---
**
- **status**: not-reproducible --> assigned
- **assigned_to**: A V Mahesh (AVM) --> Hieu Hong Hoang
- **Blocker**: --> False
---
** [tickets:#2174] MDS: mdstest 5 1 failed**
**Status:** assigned
**Milestone:** 5.2.RC2
**Created:** Tue Nov 08, 2016 06:29 AM UTC by Quyen Dao
**Last Updated:**
- **status**: review --> fixed
---
** [tickets:#3324] mds: valgrind detected an invalid read**
**Status:** fixed
**Milestone:** 5.22.11
**Created:** Mon Oct 31, 2022 07:04 AM UTC by Hieu Hong Hoang
**Last Updated:** Fri Nov 04, 2022 08:28 AM UTC
**Owner:** Hieu Hong Hoang
Valgrind has
commit 02037580ba403cb0afc66afb1e70c46c7210e21b (HEAD -> develop, ticket-3324)
Author: hieu.h.hoang
Date: Thu Nov 3 10:07:09 2022 +0700
mds: Test cases for conflicted vdests [#3324]
Verify the service events before and after conflict.
commit f5b653c6a77b0d43b647ef8930403645ff147bcd
- **status**: accepted --> review
---
** [tickets:#3324] mds: valgrind detected an invalid read**
**Status:** review
**Milestone:** 5.22.11
**Created:** Mon Oct 31, 2022 07:04 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Nov 01, 2022 11:07 AM UTC
**Owner:** Hieu Hong Hoang
Valgrind has
- **status**: assigned --> accepted
---
** [tickets:#3324] mds: valgrind detected an invalid read**
**Status:** accepted
**Milestone:** 5.22.11
**Created:** Mon Oct 31, 2022 07:04 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Nov 01, 2022 11:05 AM UTC
**Owner:** Hieu Hong Hoang
Valgrind
- **Comment**:
Reproduced in develop branch.
~~~
==487== Invalid read of size 1
==487==at 0x4843B60: __memcpy_chk (in
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
==487==by 0x4891FE3: memcpy (string_fortified.h:34)
==487==by 0x4891FE3:
- Description has changed:
Diff:
--- old
+++ new
@@ -61,7 +61,7 @@
Object /usr/lib64/libopensaf_core.so.0.2.0
Function mds_mcm_svc_down
-File/Line opensaf/src/mds/mds_c_api.c:3807
+File/Line opensaf/src/mds/mds_c_api.c:3862
Object
---
** [tickets:#3324] mds: valgrind detected an invalid read**
**Status:** assigned
**Milestone:** 5.22.11
**Created:** Mon Oct 31, 2022 07:04 AM UTC by Hieu Hong Hoang
**Last Updated:** Mon Oct 31, 2022 07:04 AM UTC
**Owner:** Hieu Hong Hoang
Valgrind has detected an invalid read from
- **status**: assigned --> review
---
** [tickets:#3322] log: log agent in main process is disabled after child
process exits**
**Status:** review
**Milestone:** 5.22.11
**Created:** Wed Oct 05, 2022 09:36 AM UTC by Hieu Hong Hoang
**Last Updated:** Wed Oct 05, 2022 09:36 AM UTC
**Owner:**
- **status**: accepted --> fixed
---
** [tickets:#3317] amfnd: two NEW_ACTIVE amfd in split-brain scenario**
**Status:** fixed
**Milestone:** 5.22.11
**Created:** Fri Jun 10, 2022 04:00 AM UTC by Hieu Hong Hoang
**Last Updated:** Mon Aug 15, 2022 06:17 AM UTC
**Owner:** Hieu Hong Hoang
This
commit 629f41983434332c732bca7f11362e5f5942a96e (HEAD -> develop,
origin/develop, ticket-3317)
Author: hieu.h.hoang
Date: Tue Jun 14 08:51:33 2022 +0700
amf: Update handling mds event in amfnd [#3317]
In amfnd, there is a flag represent for the amfd service state (up/down).
- **status**: review --> fixed
---
** [tickets:#3294] mds: refactor huge api functions**
**Status:** fixed
**Milestone:** future
**Created:** Tue Oct 26, 2021 06:02 AM UTC by Hieu Hong Hoang
**Last Updated:** Mon Aug 08, 2022 03:14 AM UTC
**Owner:** Hieu Hong Hoang
Some functions have 1.5K+
commit 8274994dd5a75157915f9af805b8ae6e7e2f4cb2 (HEAD -> develop,
origin/develop, ticket-3294)
Author: hieu.h.hoang
Date: Mon Mar 21 14:20:34 2022 +0700
mds: Refactor api functions [#3294]
Refactor big functions in the mds api.
---
** [tickets:#3294] mds: refactor huge api
Hi Mohan,
Please check the variable "IMMSV_COORD_SELECT_NODE" in the file "immd.conf". It
should be enabled to check the partition of a node. That code is in the file
"src/imm/immd/immd_evt.c":
~~~
static bool is_on_same_partition_with_coord(
IMMD_CB *cb,
const
Hi Paul,
OpenSAF have several ways to handle the split-brain. They were mentioned in the
following documents:
* sc absence: src/imm/README.SC_ABSENCE
* remote fencing: docs/OpenSAF_Overview_PR.odt 3.7.5
* split-brain prevention: docs/OpenSAF_Overview_PR.odt 3.7.6
* split-brain recovery:
Hi Mohan,
1. Yes, it is an expected behavior. The active SCs rebooted because the active
SC saw other active SC in a cluster. PLs rebooted because it lost connection
with both active SC and standby SC.
To enhance, OpenSAF introduced the SC absence feature documented in
- **status**: review --> fixed
---
** [tickets:#3102] mds: waste 1.5s in waiting Adest already down to send
response message type**
**Status:** fixed
**Milestone:** 5.20.02
**Created:** Thu Oct 17, 2019 09:23 AM UTC by Thuan Tran
**Last Updated:** Thu Jul 28, 2022 07:20 AM UTC
**Owner:**
commit a7fea9730dd8359b89fbfbf206e645ddfdf38427 (HEAD -> develop,
origin/develop, ticket-3102)
Author: hieu.h.hoang
Date: Tue Jul 19 09:23:03 2022 +0700
mds: Not wait for dead Adest to send RSP [#3102]
Currently, the adest will be deleted after the adest down timer expired.
- **status**: review --> fixed
---
** [tickets:#3319] ntf: Process the asynchronous checkpoint before sending
response**
**Status:** fixed
**Milestone:** 5.22.11
**Created:** Fri Jul 15, 2022 04:20 AM UTC by Hieu Hong Hoang
**Last Updated:** Thu Jul 28, 2022 05:49 AM UTC
**Owner:** Hieu Hong
commit 6d3a4472c7e096af046305088d17dde7107f7fba (HEAD -> develop,
origin/develop, ticket-3319)
Author: hieu.h.hoang
Date: Tue Jul 19 11:00:48 2022 +0700
ntf: Process the asynchronous checkpoint after sending response [#3319]
When ntfd receives an asynchronous checkpoint from its
Hi Mohan Kanakam,
I'm using "lxc" to run the cluster and tool "iptables" to split/merge network.
I reproduce this ticket as follow:
* Add 5 seconds delay before promoting active by changing the fmd
configuration(/etc/opensaf/fmd.conf):
~~~
export FMS_PROMOTE_ACTIVE_TIMER=500 # 5
- **status**: review --> accepted
---
** [tickets:#3317] amfnd: two NEW_ACTIVE amfd in split-brain scenario**
**Status:** accepted
**Milestone:** 5.22.11
**Created:** Fri Jun 10, 2022 04:00 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Jun 14, 2022 07:10 AM UTC
**Owner:** Hieu Hong Hoang
- **status**: accepted --> review
---
** [tickets:#3102] mds: waste 1.5s in waiting Adest already down to send
response message type**
**Status:** review
**Milestone:** 5.20.02
**Created:** Thu Oct 17, 2019 09:23 AM UTC by Thuan Tran
**Last Updated:** Fri Jul 15, 2022 03:11 AM UTC
**Owner:**
- **status**: assigned --> review
- **Type**: defect --> enhancement
---
** [tickets:#3319] ntf: Process the asynchronous checkpoint before sending
response**
**Status:** review
**Milestone:** 5.22.11
**Created:** Fri Jul 15, 2022 04:20 AM UTC by Hieu Hong Hoang
**Last Updated:** Fri Jul 15,
---
** [tickets:#3319] ntf: Process the asynchronous checkpoint before sending
response**
**Status:** assigned
**Milestone:** 5.22.11
**Created:** Fri Jul 15, 2022 04:20 AM UTC by Hieu Hong Hoang
**Last Updated:** Fri Jul 15, 2022 04:20 AM UTC
**Owner:** Hieu Hong Hoang
**Attachments:**
-
- **status**: fixed --> accepted
---
** [tickets:#3102] mds: waste 1.5s in waiting Adest already down to send
response message type**
**Status:** accepted
**Milestone:** 5.20.02
**Created:** Thu Oct 17, 2019 09:23 AM UTC by Thuan Tran
**Last Updated:** Fri Jul 15, 2022 03:10 AM UTC
It still waits 1.5s for sending response to down adest if the adest down
timeout expires and the adest is deleted.
Log analysis:
- Detect adest was down then start the down timer:
~~~
<143>1 2022-07-15T07:34:20.283881+07:00 SC-1 mdstest 488 mds.log [meta
sequenceId="213"] >> mds_mcm_svc_down
- **status**: accepted --> review
---
** [tickets:#3317] amfnd: two NEW_ACTIVE amfd in split-brain scenario**
**Status:** review
**Milestone:** 5.22.11
**Created:** Fri Jun 10, 2022 04:00 AM UTC by Hieu Hong Hoang
**Last Updated:** Fri Jun 10, 2022 04:30 AM UTC
**Owner:** Hieu Hong Hoang
In normal case, the up flag will be reset by the mds thread whenever the amfnd
receives a NEW_ACTIVE event:
~~~
case NCSMDS_NEW_ACTIVE:
if (evt_info->i_svc_id == NCSMDS_SVC_ID_AVD) {
LOG_NO("AVD NEW_ACTIVE, adest:%" PRIu64, evt_info->i_dest);
// sometimes NEW_ACTIVE
---
** [tickets:#3317] amfnd: two NEW_ACTIVE amfd in split-brain scenario**
**Status:** accepted
**Milestone:** 5.22.11
**Created:** Fri Jun 10, 2022 04:00 AM UTC by Hieu Hong Hoang
**Last Updated:** Fri Jun 10, 2022 04:00 AM UTC
**Owner:** Hieu Hong Hoang
This issue happen when we test the
- **status**: review --> fixed
---
** [tickets:#3315] imm : Redundancy admin owner after aborting sync**
**Status:** fixed
**Milestone:** 5.22.04
**Created:** Mon May 02, 2022 03:54 PM UTC by Hieu Hong Hoang
**Last Updated:** Fri May 27, 2022 04:47 AM UTC
**Owner:** Hieu Hong Hoang
While
commit 412f5da2a9c5cc60a349be6672f13238306c9785 (HEAD -> develop,
origin/develop, ticket-3315)
Author: hieu.h.hoang
Date: Mon May 2 13:20:08 2022 +0700
imm: Remove dead admin owner [#3315]
While imm is synchronizing, the function to delete admin owner
only changes the state
- **status**: review --> fixed
---
** [tickets:#3314] imm: Deadlock between pbe and ccb applied on a pbe object**
**Status:** fixed
**Milestone:** 5.22.04
**Created:** Mon May 02, 2022 03:20 PM UTC by Hieu Hong Hoang
**Last Updated:** Fri May 27, 2022 04:46 AM UTC
**Owner:** Hieu Hong Hoang
commit 1542758ef4637321b987bd67becac66ba06d (ticket-3314)
Author: hieu.h.hoang
Date: Mon May 2 12:56:23 2022 +0700
imm: Fix pbe deadlock [#3314]
Immpbe will fail to restart if a ccb which applies to an immpbe object
changes state to critical. The ccb will be aborted if
- **status**: accepted --> review
---
** [tickets:#3294] mds: refactor huge api functions**
**Status:** review
**Milestone:** future
**Created:** Tue Oct 26, 2021 06:02 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Feb 08, 2022 05:09 AM UTC
**Owner:** Hieu Hong Hoang
Some functions have
- **status**: assigned --> review
---
** [tickets:#3314] imm: Deadlock between pbe and ccb applied on a pbe object**
**Status:** review
**Milestone:** 5.22.04
**Created:** Mon May 02, 2022 03:20 PM UTC by Hieu Hong Hoang
**Last Updated:** Mon May 02, 2022 03:20 PM UTC
**Owner:** Hieu Hong
- **status**: assigned --> review
---
** [tickets:#3315] imm : Redundancy admin owner after aborting sync**
**Status:** review
**Milestone:** 5.22.04
**Created:** Mon May 02, 2022 03:54 PM UTC by Hieu Hong Hoang
**Last Updated:** Mon May 02, 2022 03:54 PM UTC
**Owner:** Hieu Hong Hoang
---
** [tickets:#3315] imm : Redundancy admin owner after aborting sync**
**Status:** assigned
**Milestone:** 5.22.04
**Created:** Mon May 02, 2022 03:54 PM UTC by Hieu Hong Hoang
**Last Updated:** Mon May 02, 2022 03:54 PM UTC
**Owner:** Hieu Hong Hoang
While imm is synchronizing, the
---
** [tickets:#3314] imm: Deadlock between pbe and ccb applied on a pbe object**
**Status:** assigned
**Milestone:** 5.22.04
**Created:** Mon May 02, 2022 03:20 PM UTC by Hieu Hong Hoang
**Last Updated:** Mon May 02, 2022 03:20 PM UTC
**Owner:** Hieu Hong Hoang
Generally, a critical ccb
- **status**: review --> fixed
---
** [tickets:#3313] log: logtest 2 36 failed while initializing log agent**
**Status:** fixed
**Milestone:** 5.22.04
**Created:** Tue Apr 12, 2022 07:41 AM UTC by Hieu Hong Hoang
**Last Updated:** Thu Apr 28, 2022 03:09 AM UTC
**Owner:** Hieu Hong Hoang
commit 38bfec225c6f8e1d540f45d7ee4a563db5041bb1 (HEAD -> ticket-3313,
origin/develop, develop)
Author: hieu.h.hoang
Date: Tue Apr 12 15:01:12 2022 +0700
log: Update counting log client [#3313]
A log client is not saved to the client list until the log agent receives
the
- **status**: assigned --> review
- Attachments has changed:
Diff:
--- old
+++ new
@@ -0,0 +1 @@
+loga.txt (2.1 MB; text/plain)
---
** [tickets:#3313] log: logtest 2 36 failed while initializing log agent**
**Status:** review
**Milestone:** 5.22.04
**Created:** Tue Apr 12, 2022
In ticket [#3291](https://sourceforge.net/p/opensaf/tickets/3291/), the
function "CountClient" was added. It counts the number of client base on the
number of saved client. However, there are some client wasn't saved yet because
its initialization is in progress.
---
** [tickets:#3313]
---
** [tickets:#3313] log: logtest 2 36 failed while initializing log agent**
**Status:** assigned
**Milestone:** 5.22.04
**Created:** Tue Apr 12, 2022 07:41 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Apr 12, 2022 07:41 AM UTC
**Owner:** Hieu Hong Hoang
While initializing log agent,
commit 78cbf3c763439e24d3db459fe5a0d6e5974c693e (HEAD -> develop,
origin/develop, ticket-3310)
Author: hieu.h.hoang
Date: Thu Mar 17 15:27:01 2022 +0700
log: The log director always sends the initial message [#3310]
The log agent 5.22.01 will wait for the initial message
but
- **status**: review --> fixed
---
** [tickets:#3310] log: log agent is blocked for 10s**
**Status:** fixed
**Milestone:** 5.22.04
**Created:** Tue Mar 08, 2022 03:32 AM UTC by Hieu Hong Hoang
**Last Updated:** Thu Mar 24, 2022 01:30 AM UTC
**Owner:** Hieu Hong Hoang
In [ticket
- **status**: accepted --> review
---
** [tickets:#3310] log: log agent is blocked for 10s**
**Status:** review
**Milestone:** 5.22.04
**Created:** Tue Mar 08, 2022 03:32 AM UTC by Hieu Hong Hoang
**Last Updated:** Thu Mar 17, 2022 08:22 AM UTC
**Owner:** Hieu Hong Hoang
In [ticket
In previous commit, the log agent 5.22.01 is still blocked for 10s if it runs
with new log director. The log agent 5.22.01 will wait for the initial message
but its subpart version is 1. Therefore the log director doesn't know that it
needs to send the initial message.
A different approach is
- **status**: fixed --> accepted
---
** [tickets:#3310] log: log agent is blocked for 10s**
**Status:** accepted
**Milestone:** 5.22.04
**Created:** Tue Mar 08, 2022 03:32 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Mar 15, 2022 03:23 AM UTC
**Owner:** Hieu Hong Hoang
In [ticket
- **status**: accepted --> fixed
---
** [tickets:#3310] log: log agent is blocked for 10s**
**Status:** fixed
**Milestone:** 5.22.04
**Created:** Tue Mar 08, 2022 03:32 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Mar 15, 2022 03:22 AM UTC
**Owner:** Hieu Hong Hoang
In [ticket
- **status**: assigned --> accepted
---
** [tickets:#3310] log: log agent is blocked for 10s**
**Status:** accepted
**Milestone:** 5.22.04
**Created:** Tue Mar 08, 2022 03:32 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Mar 08, 2022 03:32 AM UTC
**Owner:** Hieu Hong Hoang
In [ticket
---
** [tickets:#3310] log: log agent is blocked for 10s**
**Status:** assigned
**Milestone:** 5.22.04
**Created:** Tue Mar 08, 2022 03:32 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Mar 08, 2022 03:32 AM UTC
**Owner:** Hieu Hong Hoang
In [ticket
- Description has changed:
Diff:
--- old
+++ new
@@ -1,13 +1,13 @@
-After the active SC rebooted, the standby SC executed failover to active. The
new active SC notified a PL left cluster but that PL was still in cluster. The
reason is the connection between the standby SC and that PL was
---
** [tickets:#3309] clm: the payload node unexpectedly left cluster right after
failover**
**Status:** accepted
**Milestone:** 5.22.04
**Created:** Thu Feb 24, 2022 03:57 AM UTC by Hieu Hong Hoang
**Last Updated:** Thu Feb 24, 2022 03:57 AM UTC
**Owner:** Hieu Hong Hoang
After the
- **status**: assigned --> accepted
---
** [tickets:#3294] mds: refactor huge api functions**
**Status:** accepted
**Milestone:** future
**Created:** Tue Oct 26, 2021 06:02 AM UTC by Hieu Hong Hoang
**Last Updated:** Sun Jan 23, 2022 10:05 PM UTC
**Owner:** Hieu Hong Hoang
Some functions
- **status**: review --> fixed
---
** [tickets:#3304] mds: Packet loss without log**
**Status:** fixed
**Milestone:** 5.22.04
**Created:** Tue Jan 04, 2022 03:47 AM UTC by Hieu Hong Hoang
**Last Updated:** Fri Jan 28, 2022 01:42 AM UTC
**Owner:** Hieu Hong Hoang
In mds module, there is a
commit fb5a176285562d08edd6a7d04e67ba4a96f8e9f8 (HEAD -> develop,
origin/develop)
Author: hieu.h.hoang
Date: Thu Jan 6 10:37:51 2022 +0700
mds: Correct checking the sequence number in loss indication [#3304]
The sequence number of broadcast message is associated with a specific
- **status**: unassigned --> assigned
---
** [tickets:#3294] mds: refactor huge api functions**
**Status:** assigned
**Milestone:** 5.21.12
**Created:** Tue Oct 26, 2021 06:02 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Oct 26, 2021 06:02 AM UTC
**Owner:** Hieu Hong Hoang
Some functions
- **status**: accepted --> review
- **Type**: enhancement --> defect
---
** [tickets:#3304] mds: Packet loss without log**
**Status:** review
**Milestone:** 5.21.12
**Created:** Tue Jan 04, 2022 03:47 AM UTC by Hieu Hong Hoang
**Last Updated:** Wed Jan 05, 2022 04:04 AM UTC
**Owner:** Hieu
There is another error with the broadcast message. Currently, mds chooses an
adest (active adest for normal mode or any adest for redundancy mode) and gets
its sent message count to assign the sequence number of broadcast message.
That sequence number is only valid to the chosen adest and
- **status**: assigned --> accepted
---
** [tickets:#3304] mds: Packet loss without log**
**Status:** accepted
**Milestone:** 5.21.12
**Created:** Tue Jan 04, 2022 03:47 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Jan 04, 2022 04:49 AM UTC
**Owner:** Hieu Hong Hoang
In mds module, there
There are several packet loss logs which is always printed out although no
packet loss.
~~~
<139>1 2022-01-04T11:34:35.408579+07:00 SC-1 osafntfd 276 mds.log [meta
sequenceId="6"] MDS_SND_RCV: msg loss detected, Src svc_id = LGS(20), Src vdest
id= 11, Src Adest = 564116277870562, local svc_id
---
** [tickets:#3304] mds: Packet loss without log**
**Status:** assigned
**Milestone:** 5.21.12
**Created:** Tue Jan 04, 2022 03:47 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Jan 04, 2022 03:47 AM UTC
**Owner:** Hieu Hong Hoang
In mds module, there is a packet loss feature. This
- **status**: review --> fixed
---
** [tickets:#3302] log: Threads wasn't stopped while releasing log agent**
**Status:** fixed
**Milestone:** 5.21.12
**Created:** Mon Dec 27, 2021 06:29 AM UTC by Hieu Hong Hoang
**Last Updated:** Tue Jan 04, 2022 03:12 AM UTC
**Owner:** Hieu Hong Hoang
In
commit a9e7afa1215407b43c0e993768a003f980e85010 (HEAD -> develop,
origin/develop)
Author: hieu.h.hoang
Date: Mon Dec 27 13:52:49 2021 +0700
log: Stop all threads while releasing the log agent object [#3302]
In the destructor of LogAgent, stop all threads of log agent.
---
**
- **status**: accepted --> review
---
** [tickets:#3302] log: Threads wasn't stopped while releasing log agent**
**Status:** review
**Milestone:** 5.21.12
**Created:** Mon Dec 27, 2021 06:29 AM UTC by Hieu Hong Hoang
**Last Updated:** Mon Dec 27, 2021 06:29 AM UTC
**Owner:** Hieu Hong Hoang
- **status**: assigned --> accepted
- **assigned_to**: Hieu Hong Hoang
---
** [tickets:#3302] log: Threads wasn't stopped while releasing log agent**
**Status:** accepted
**Milestone:** 5.21.12
**Created:** Mon Dec 27, 2021 06:29 AM UTC by Hieu Hong Hoang
**Last Updated:** Mon Dec 27, 2021
---
** [tickets:#3302] log: Threads wasn't stopped while releasing log agent**
**Status:** assigned
**Milestone:** 5.21.12
**Created:** Mon Dec 27, 2021 06:29 AM UTC by Hieu Hong Hoang
**Last Updated:** Mon Dec 27, 2021 06:29 AM UTC
**Owner:** nobody
In the destructor of a class, we should
- **Type**: enhancement --> defect
---
** [tickets:#3291] log: shutdown log agent when not in use**
**Status:** fixed
**Milestone:** 5.21.12
**Created:** Mon Oct 18, 2021 07:59 AM UTC by Hieu Hong Hoang
**Last Updated:** Wed Dec 08, 2021 08:22 AM UTC
**Owner:** Hieu Hong Hoang
Currently,
- **status**: review --> fixed
---
** [tickets:#3301] log: Try to shutdown the log agent even if it already
shutdown**
**Status:** fixed
**Milestone:** 5.21.12
**Created:** Thu Dec 09, 2021 08:50 AM UTC by Hieu Hong Hoang
**Last Updated:** Wed Dec 15, 2021 10:45 AM UTC
**Owner:** Hieu Hong
commit aec1464068db214e50dee7d66b3511c7816dc79f (HEAD -> develop,
origin/develop, ticket-3301)
Author: hieu.h.hoang
Date: Fri Dec 10 07:41:08 2021 +0700
log: Correct condition to shutdown the log agent [#3301]
The shutdown function was invoked every time invoking the finalize
- **summary**: log: Correct condition to shutdown the log agent --> log: Try to
shutdown the log agent even if it already shutdown
---
** [tickets:#3301] log: Try to shutdown the log agent even if it already
shutdown**
**Status:** review
**Milestone:** 5.21.12
**Created:** Thu Dec 09, 2021
- **summary**: log: Check the value of waiting variable before assigning -->
log: Correct condition to shutdown the log agent
- Description has changed:
Diff:
--- old
+++ new
@@ -15,4 +15,4 @@
atomic_data_.waiting_log_server_up = true;
}
~~~
-The signal wait for server was
- **summary**: log: Correct assigning the signal wait for server --> log: Check
the value of waiting variable before assigning
---
** [tickets:#3301] log: Check the value of waiting variable before assigning**
**Status:** accepted
**Milestone:** 5.21.12
**Created:** Thu Dec 09, 2021 08:50 AM
- **status**: assigned --> accepted
---
** [tickets:#3301] log: Correct assigning the signal wait for server**
**Status:** accepted
**Milestone:** 5.21.12
**Created:** Thu Dec 09, 2021 08:50 AM UTC by Hieu Hong Hoang
**Last Updated:** Thu Dec 09, 2021 08:50 AM UTC
**Owner:** Hieu Hong Hoang
---
** [tickets:#3301] log: Correct assigning the signal wait for server**
**Status:** assigned
**Milestone:** 5.21.12
**Created:** Thu Dec 09, 2021 08:50 AM UTC by Hieu Hong Hoang
**Last Updated:** Thu Dec 09, 2021 08:50 AM UTC
**Owner:** Hieu Hong Hoang
In [ticket
- **status**: assigned --> duplicate
- **Comment**:
The problem has been solved in [ticket
3291](https://sourceforge.net/p/opensaf/tickets/3291/) .
---
** [tickets:#3292] log: Introduce an initial clm node status**
**Status:** duplicate
**Milestone:** 5.21.12
**Created:** Mon Oct 18, 2021
- **status**: review --> fixed
- **Comment**:
commit fbcb58c1dfa384c2922f65861befa478fff7ee41 (HEAD -> develop,
origin/develop, ticket-3291)
Author: hieu.h.hoang
Date: Tue Dec 7 19:37:40 2021 +0700
log: Increase timeout in logtest [#3291]
Because the log agent have to wait for
- **status**: review --> fixed
---
** [tickets:#3296] amf: The csi attribute callback is non backward compatible**
**Status:** fixed
**Milestone:** 5.21.12
**Created:** Mon Nov 22, 2021 10:26 AM UTC by Hieu Hong Hoang
**Last Updated:** Thu Dec 02, 2021 12:47 AM UTC
**Owner:** Hieu Hong Hoang
- **Comment**:
commit 9945ae29d09350340d6d2bb4c1d463bd010dde47 (HEAD -> develop,
origin/develop)
Author: hieu.h.hoang
Date: Mon Nov 22 17:29:02 2021 +0700
amf: Correct the version of csi attribute message [#3296]
In ticket 3255, the csi attribute message was changed its format
- **status**: assigned --> review
---
** [tickets:#3291] log: shutdown log agent when not in use**
**Status:** review
**Milestone:** 5.21.12
**Created:** Mon Oct 18, 2021 07:59 AM UTC by Hieu Hong Hoang
**Last Updated:** Mon Oct 18, 2021 07:59 AM UTC
**Owner:** Hieu Hong Hoang
Currently,
- **summary**: log: Introduce an initial node status callback --> log:
Introduce an initial clm node status
- Description has changed:
Diff:
--- old
+++ new
@@ -1,9 +1,9 @@
-Currently, loga don't know when logd is ready for a request. In this ticket,
we introduce a new callback from
- **status**: accepted --> review
---
** [tickets:#3296] amf: The csi attribute callback is non backward compatible**
**Status:** review
**Milestone:** 5.21.12
**Created:** Mon Nov 22, 2021 10:26 AM UTC by Hieu Hong Hoang
**Last Updated:** Mon Nov 22, 2021 10:37 AM UTC
**Owner:** Hieu Hong
1 - 100 of 143 matches
Mail list logo
