---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassigned
**Milestone:** future
**Created:** Tue May 20, 2014 07:08 AM UTC by surender khetavath
**Last Updated:** Tue May 20, 2014 07:08 AM UTC
**Owner:** nobody
changeset : 5270
1)
---
** [tickets:#917] LOG: App stream with special file name creates runtime object
that is not removed correctly**
**Status:** unassigned
**Milestone:** 4.5.FC
**Created:** Tue May 20, 2014 07:57 AM UTC by elunlen
**Last Updated:** Tue May 20, 2014 07:57 AM UTC
**Owner:** nobody
1. Pro
- **status**: fixed --> accepted
- **Comment**:
Add support for enabling/disabling the new features tracked by this ticket
based on the opensafImmNostdFlags bit 5 for upgrades to OpenSAF 4.5
---
** [tickets:#798] IMM: Support for explicit ccb-validate and explicit
ccb-abort**
**Status:** a
- **status**: accepted --> review
- **Comment**:
https://sourceforge.net/p/opensaf/mailman/message/32359215/
---
** [tickets:#842] IMM: Additional upgrade flag (noStdFlags) needed for OpenSAF
4.5**
**Status:** review
**Milestone:** 4.5.FC
**Created:** Wed Apr 09, 2014 08:37 AM UTC by Anders
- **status**: fixed --> accepted
- **Comment**:
Add support for enabling/disabling the new features tracked by this ticket
based on the opensafImmNostdFlags bit 5 for upgrades to OpenSAF 4.5
---
** [tickets:#799] IMM: Allow admin-operations directly targeting an
implementer/applier**
**Stat
I tried to reproduced it, but the test steps works successfully.
Please check binary linkage, there may be possibility of linking it with other
installed libraries.
Thanks
-Nagu
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassi
- **status**: accepted --> fixed
- **Comment**:
Fixed in following changesets (fixed comment from Ramesh on using host order
for client id):
[staging:73f229]
[staging:4a1d99]
[staging:b2d18f]
changeset: 5283:73f2298068c9
branch: opensaf-4.3.x
parent: 5276:422a57501142
user:M
---
** [tickets:#918] log: Wrong timeout time on 32-bit systems**
**Status:** unassigned
**Milestone:** 4.4.1
**Created:** Tue May 20, 2014 01:06 PM UTC by Anders Widell
**Last Updated:** Tue May 20, 2014 01:06 PM UTC
**Owner:** nobody
There is a bug in the function get_timeout_time() in lgs_
When fixing this bug, it is probably a good idea to change the code to use the
support functions in osaf_time.h for time calculations.
---
** [tickets:#918] log: Wrong timeout time on 32-bit systems**
**Status:** unassigned
**Milestone:** 4.4.1
**Created:** Tue May 20, 2014 01:06 PM UTC by And
i checked my setup. libraries are properly linked.
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassigned
**Milestone:** future
**Created:** Tue May 20, 2014 07:08 AM UTC by surender khetavath
**Last Updated:** Tue May 20, 2014 1
- **status**: fixed --> accepted
- **Comment**:
The ticket is reopened for fixing the loading of the first value of double
attribute from PBE.
---
** [tickets:#53] IMM: SaDoubleT and SaFloatT attributes not handled correctly**
**Status:** accepted
**Milestone:** 4.5.FC
**Created:** Wed May 0
- **status**: review --> fixed
- **Comment**:
changeset: 5288:b10140b4b3fb
tag: tip
parent: 5285:b2d18f29d6a7
user:Anders Bjornerstedt
date:Tue May 20 17:33:37 2014 +0200
summary: immpbe: unlink any /tmp/imm.db. file and journal when exiting
on error [#869]
- **status**: accepted --> review
- **Comment**:
https://sourceforge.net/p/opensaf/mailman/message/32360574/
---
** [tickets:#53] IMM: SaDoubleT and SaFloatT attributes not handled correctly**
**Status:** review
**Milestone:** 4.5.FC
**Created:** Wed May 08, 2013 08:15 AM UTC by Anders Bjorne
changeset: 5289:a295a54d6334
branch: opensaf-4.4.x
parent: 5287:f713889d0eff
user:Alex Jones
date:Mon May 19 17:51:25 2014 -0400
summary: amfd: allow increase of saAmfSGNumPrefActiveSUs for N+M SG while
UNLOCKED [#871]
changeset: 5290:83e568c7b393
tag: t
- **status**: review --> fixed
- **assigned_to**: Alex Jones --> nobody
- **Version**: --> 4.4
- **Milestone**: future --> 4.4.1
- **Comment**:
I did not realize this was an enhancement so I also pushed it to 4.4
---
** [tickets:#871] AMF: allow in-service modification of saAmfSGNumPrefActi
- **status**: assigned --> review
---
** [tickets:#770] CKPT service performance enhancements**
**Status:** review
**Milestone:** future
**Created:** Thu Feb 06, 2014 07:01 PM UTC by Alex Jones
**Last Updated:** Tue Apr 29, 2014 06:05 PM UTC
**Owner:** Alex Jones
The checkpoint service has so
Analysis:
1. The command was issued from payload PL-4 for lock-in the
safSu=PL-4,safSg=NoRed,safApp=OpenSAF.
2. Amfnd on PL-4 terminates the immnd and sends response to Amfd(on SC-1) and
Amfd(on SC-1) responds to immnd(on SC-1).
May 20 12:19:59.855987 osafamfd [3515:avd_ndproc.c:0323] >>
su_ad
- **Component**: amf --> imm
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassigned
**Milestone:** future
**Created:** Tue May 20, 2014 07:08 AM UTC by surender khetavath
**Last Updated:** Wed May 21, 2014 03:02 AM UTC
**Owner:**
- **status**: review --> fixed
- **Version**: --> 4.3
- **Comment**:
changeset: 5291:5b26ace99c1b
branch: opensaf-4.3.x
parent: 5286:95a9ef027285
user:minh.c...@dektech.com.au
date:Wed May 21 10:41:46 2014 +0530
summary: amfnd : fix SU restart escalation [#885].
c
My interpretation is that the payload where the admin-op request is issued,
can not be communicated with when the reply for the admin-op is to be sent.
The analysis above says that the IMMND is "terminated" and that would then
be an explanation. The only question would be why is the IMMND terminate
- **Component**: imm --> unknown
- **Comment**:
The IMMND at PL_4 receives a terminate callback from the AMF.
---
** [tickets:#916] lock-in of payload middleware su times-out and remains in
ENABLED state**
**Status:** unassigned
**Milestone:** future
**Created:** Tue May 20, 2014 07:08 AM U
21 matches
Mail list logo
