---
** [tickets:#1027] LOG: Incorrectly detects the log service configuration
object is invalid**
**Status:** unassigned
**Milestone:** 4.5.0
**Created:** Thu Aug 28, 2014 06:02 AM UTC by David Byrne
**Last Updated:** Thu Aug 28, 2014 06:02 AM UTC
**Owner:** nobody
log service logs "No or in
- **status**: accepted --> review
---
** [tickets:#1026] PLM: ignore MDS events from other nodes**
**Status:** review
**Milestone:** 4.5.0
**Created:** Wed Aug 27, 2014 09:26 PM UTC by Alex Jones
**Last Updated:** Wed Aug 27, 2014 09:26 PM UTC
**Owner:** Alex Jones
When receiving MDS events,
---
** [tickets:#1026] PLM: ignore MDS events from other nodes**
**Status:** accepted
**Milestone:** 4.5.0
**Created:** Wed Aug 27, 2014 09:26 PM UTC by Alex Jones
**Last Updated:** Wed Aug 27, 2014 09:26 PM UTC
**Owner:** Alex Jones
When receiving MDS events, PLMS does not look at the node f
---
** [tickets:#1025] osafamfd crashed during restart failure **
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Wed Aug 27, 2014 05:31 PM UTC by KANG-SEN LU
**Last Updated:** Wed Aug 27, 2014 05:31 PM UTC
**Owner:** nobody
We are running opensaf 4.4.0.
Here is a gdb stack trace of
The testcase involves killing of IMMND. In the newly shared logs IMMND got
killed 10 time. The problem got reproduced when killing at 10th time.
Attachment: 1024_new.tgz (807.9 kB; application/x-compressed-tar)
---
** [tickets:#1024] mds access control : imma is not able to connect to immnd
The problem is happening when IMMND is killed more than one time and the agent
is still there.
---
** [tickets:#1024] mds access control : imma is not able to connect to immnd
after immnd restart**
**Status:** unassigned
**Milestone:** 4.5.0
**Created:** Wed Aug 27, 2014 02:28 PM UTC by Neela
attached immnd traces, imma races and syslog.
Attachment: 1024.tgz (390.5 kB; application/x-compressed-tar)
---
** [tickets:#1024] mds access control : imma is not able to connect to immnd
after immnd restart**
**Status:** unassigned
**Milestone:** 4.5.0
**Created:** Wed Aug 27, 2014 02:28
- **summary**: LOG: Update Programmer's Reference for enhancement #921 --> LOG:
Update Programmer's Reference for 4.5
- **status**: accepted --> fixed
- **Comment**:
changeset: 119:a051a0a44c3e
tag: tip
user:Mathivanan N.P.
date:Wed Aug 27 20:54:11 2014 -0400
summary:
can you provide more complete traces?
---
** [tickets:#1024] mds access control : imma is not able to connect to immnd
after immnd restart**
**Status:** unassigned
**Milestone:** 4.5.0
**Created:** Wed Aug 27, 2014 02:28 PM UTC by Neelakanta Reddy
**Last Updated:** Wed Aug 27, 2014 03:16 PM UT
changeset 5648 with additional patch of 938 (which is a part of 5670
changeset)
---
** [tickets:#1024] mds access control : imma is not able to connect to immnd
after immnd restart**
**Status:** unassigned
**Milestone:** 4.5.0
**Created:** Wed Aug 27, 2014 02:28 PM UTC by Neelakanta Reddy
*
1556 is an IMM agent application, where the agent continuously do initialize
and do imm operation and finalize.
---
** [tickets:#1024] mds access control : imma is not able to connect to immnd
after immnd restart**
**Status:** unassigned
**Milestone:** 4.5.0
**Created:** Wed Aug 27, 2014 02
- **summary**: mds: imma is not able to connect to immnd after immnd restart
--> mds access control : imma is not able to connect to immnd after immnd
restart
- **assigned_to**: Hans Feldt
- **Comment**:
Hans,
This seems to be IMM access control related.
---
** [tickets:#1024] mds access
Most (all?) opensaf processes seems to be able to reconnet. What process (PID
1556) is this?
There seems to be some race here. Can you reproduce with immnd traces?
---
** [tickets:#1024] mds: imma is not able to connect to immnd after immnd
restart**
**Status:** unassigned
**Milestone:** 4.5
---
** [tickets:#1024] mds: imma is not able to connect to immnd after immnd
restart**
**Status:** unassigned
**Milestone:** 4.5.0
**Created:** Wed Aug 27, 2014 02:28 PM UTC by Neelakanta Reddy
**Last Updated:** Wed Aug 27, 2014 02:28 PM UTC
**Owner:** nobody
syslog:
---
Aug 27 16:40:07
- **status**: accepted --> review
---
** [tickets:#961] Imm: IMMND get restarted when opensafImmSyncBatchSize is
modified when PBE is enabled**
**Status:** review
**Milestone:** 4.3.3
**Created:** Wed Jul 16, 2014 07:18 AM UTC by Neelakanta Reddy
**Last Updated:** Wed Aug 27, 2014 10:34 AM UT
---
** [tickets:#1023] su stuck in instantiating state**
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Wed Aug 27, 2014 12:04 PM UTC by surender khetavath
**Last Updated:** Wed Aug 27, 2014 12:04 PM UTC
**Owner:** nobody
changeset : 5608
model : 2n
configuration : 1App,1SG,2SUs wit
- **status**: review --> fixed
- **assigned_to**: Hans Feldt --> nobody
---
** [tickets:#995] IMM: after immnd restart amfd fails to become class
implementer**
**Status:** fixed
**Milestone:** 4.5.0
**Created:** Tue Aug 19, 2014 10:36 AM UTC by Hans Feldt
**Last Updated:** Thu Aug 21, 2014
- **Priority**: major --> minor
- **Comment**:
Questionable if it should be fixed.
Use case would likely be someone issuing e.g
do "amf-adm shutdown X"
wait a while, give up and hit CTRL-C
do "amf-adm lock X".
=> nowhere to send the admin op response anyway
---
** [tickets:#1021] AMF: no res
Please write a defect on 4.5
---
** [tickets:#911] AMF: allow creation/deletion of unlocked SUs**
**Status:** fixed
**Milestone:** 4.5.0
**Created:** Thu May 15, 2014 11:49 AM UTC by Hans Feldt
**Last Updated:** Wed Aug 27, 2014 10:34 AM UTC
**Owner:** Hans Feldt
Allow creation of unlocked SUs
- **status**: assigned --> accepted
---
** [tickets:#961] Imm: IMMND get restarted when opensafImmSyncBatchSize is
modified when PBE is enabled**
**Status:** accepted
**Milestone:** 4.3.3
**Created:** Wed Jul 16, 2014 07:18 AM UTC by Neelakanta Reddy
**Last Updated:** Fri Aug 22, 2014 08:13 A
- **status**: assigned --> fixed
---
** [tickets:#911] AMF: allow creation/deletion of unlocked SUs**
**Status:** fixed
**Milestone:** 4.5.0
**Created:** Thu May 15, 2014 11:49 AM UTC by Hans Feldt
**Last Updated:** Wed Aug 27, 2014 10:33 AM UTC
**Owner:** Hans Feldt
Allow creation of unlocke
- **Milestone**: 4.6.FC --> 4.5.0
---
** [tickets:#911] AMF: allow creation/deletion of unlocked SUs**
**Status:** assigned
**Milestone:** 4.5.0
**Created:** Thu May 15, 2014 11:49 AM UTC by Hans Feldt
**Last Updated:** Wed Aug 27, 2014 10:15 AM UTC
**Owner:** Hans Feldt
Allow creation of unl
---
** [tickets:#1022] AMF: no response to SI lock when payload is rebooted**
**Status:** unassigned
**Milestone:** future
**Created:** Wed Aug 27, 2014 10:31 AM UTC by Hans Feldt
**Last Updated:** Wed Aug 27, 2014 10:31 AM UTC
**Owner:** nobody
Test case that used to work before with 4.4
Do
Ok, I will check.
---
** [tickets:#1021] AMF: no response to SI shutdown when overridden by SI lock**
**Status:** unassigned
**Milestone:** future
**Created:** Wed Aug 27, 2014 09:42 AM UTC by Hans Feldt
**Last Updated:** Wed Aug 27, 2014 10:20 AM UTC
**Owner:** nobody
A previously working tes
Shutdown an SI
SI stays in SHUTTING-DOWN because the test app does not call quiescingComplete()
Lock the SI
test app gets a quiesced and remove callback to which it responds OK
Lock admin op responded
Shutdown admin op never responded
---
** [tickets:#1021] AMF: no response to SI shutdown when
Hi Hans, Any update ??
---
** [tickets:#911] AMF: allow creation/deletion of unlocked SUs**
**Status:** assigned
**Milestone:** 4.6.FC
**Created:** Thu May 15, 2014 11:49 AM UTC by Hans Feldt
**Last Updated:** Fri Aug 15, 2014 02:55 PM UTC
**Owner:** Hans Feldt
Allow creation of unlocked SUs w
can you please update the test steps.
---
** [tickets:#1021] AMF: no response to SI shutdown when overridden by SI lock**
**Status:** unassigned
**Milestone:** future
**Created:** Wed Aug 27, 2014 09:42 AM UTC by Hans Feldt
**Last Updated:** Wed Aug 27, 2014 09:42 AM UTC
**Owner:** nobody
A pr
- **status**: unassigned --> assigned
- **assigned_to**: Praveen
- **Milestone**: 4.3.3 --> 4.4.1
---
** [tickets:#1015] si's are not assigned to su after si-swap with fault**
**Status:** assigned
**Milestone:** 4.4.1
**Created:** Tue Aug 26, 2014 09:22 AM UTC by surender khetavath
**Last Upda
Analysis:
1) si-swap was started at
Aug 26 17:03:32.377085 osafamfd [24033:lga_api.c:0915] << saLogWriteLogAsync
Aug 26 17:03:32.377095 osafamfd [24033:si.cc:0780] >> si_admin_op_cb:
safSi=AmfDemo1,safApp=AmfDemo1 op=7
Aug 26 17:03:32.377114 osafamfd [24033:sg_2n_fsm.cc:0757] >> si_swap:
'safSi=
---
** [tickets:#1021] AMF: no response to SI shutdown when overridden by SI lock**
**Status:** unassigned
**Milestone:** future
**Created:** Wed Aug 27, 2014 09:42 AM UTC by Hans Feldt
**Last Updated:** Wed Aug 27, 2014 09:42 AM UTC
**Owner:** nobody
A previously working testcase no longer w
---
** [tickets:#1020] amfnd crashed on payload node**
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Wed Aug 27, 2014 09:34 AM UTC by surender khetavath
**Last Updated:** Wed Aug 27, 2014 09:34 AM UTC
**Owner:** nobody
changeset : 5608
model : 2n
configuration : 1App,1SG,2SUs with
The info is already there, check the validation I did for accessControlMode
---
** [tickets:#1008] IMM: Changes to access control attribute should be local
validated**
**Status:** accepted
**Milestone:** 4.5.0
**Created:** Fri Aug 22, 2014 01:52 PM UTC by Anders Bjornerstedt
**Last Updated:**
This means the validation code needs acces to the user id for the client.
Needs to be added to client_node srtuct in IMMND.
---
** [tickets:#1008] IMM: Changes to access control attribute should be local
validated**
**Status:** accepted
**Milestone:** 4.5.0
**Created:** Fri Aug 22, 2014 01:52
that was not my thought and not the way accessControlMode is handled now. I
meant _all_ changes to the service object should need root.
---
** [tickets:#1008] IMM: Changes to access control attribute should be local
validated**
**Status:** accepted
**Milestone:** 4.5.0
**Created:** Fri Aug 22
The restiriction to all changes to root is of course only enforced if the
current mode is "enforcing"
/AndersBj
From: Hans Feldt [mailto:hansfe...@users.sf.net]
Sent: den 27 augusti 2014 07:28
To: [opensaf:tickets]
Subject: [opensaf:tickets] #1008 IMM: Changes to
35 matches
Mail list logo