[tickets] [opensaf:tickets] #2431 smf: imm version changes need to be updated to latest

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

commit fb4ca33088b9191a937a48dc1b935e5bc2f4e3cd
Author: Neelakanta Reddy <reddy.neelaka...@oracle.com>
Date:   Thu Apr 20 15:52:55 2017 +0530

smf: updated the imm API vesrion to latest supported [#2431]

commit 83eb0fd373d36ea5603fa78f08dbad34560db31a
Author: Neelakanta Reddy <reddy.neelaka...@oracle.com>
Date:   Thu Apr 20 15:52:55 2017 +0530

smf: updated the imm API vesrion to latest supported [#2431]

changeset:   8789:7857092baa49
tag: tip
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Wed May 03 14:35:25 2017 +0530
summary: smf: updated the imm API vesrion to latest supported [#2431]





---

** [tickets:#2431] smf: imm version changes need to be updated to latest **

**Status:** fixed
**Milestone:** 5.17.08
**Created:** Tue Apr 18, 2017 12:49 PM UTC by Neelakanta Reddy
**Last Updated:** Mon Apr 24, 2017 08:19 AM UTC
**Owner:** Neelakanta Reddy


Update the IMM version from A.2.1 to A.2.17 (latest version) im SMFD, to 
support saImmOmCcbGetErrorStrings.

The logic for return value for IMM operations has to be corrected  to support 
only TRY_AGAIN for "Resource abort".



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2431 smf: imm version changes need to be updated to latest

[Neelakanta Reddy]

 [a4c626]


---

** [tickets:#2431] smf: imm version changes need to be updated to latest **

**Status:** review
**Milestone:** 5.17.08
**Created:** Tue Apr 18, 2017 12:49 PM UTC by Neelakanta Reddy
**Last Updated:** Thu Apr 20, 2017 11:00 AM UTC
**Owner:** Neelakanta Reddy


Update the IMM version from A.2.1 to A.2.18 (latest version) im SMFD, to 
support saImmOmCcbGetErrorStrings.

The logic for return value for IMM operations has to be corrected  to support 
only TRY_AGAIN for "Resource abort".



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2431 smf: imm version changes need to be updated to latest

[Neelakanta Reddy]

https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_u_neelakanta_review_ci_a4c626d17618f69abffc35893294f26e3cde2887_=DwMCAg=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=Vydv5EY3gJ1pzUvE62N7bXZAd7zlTAXJmu6ygWdk5jU=8SKTT-JaW_ywObgwN4Y-KWjzVX7c9LXhZiEiUgi2d9k=AVyDeGHvKBvbUWTNF5qWBvwkI7M8yxnCy-QzKFIkNfU=


---

** [tickets:#2431] smf: imm version changes need to be updated to latest **

**Status:** review
**Milestone:** 5.17.08
**Created:** Tue Apr 18, 2017 12:49 PM UTC by Neelakanta Reddy
**Last Updated:** Thu Apr 20, 2017 11:04 AM UTC
**Owner:** Neelakanta Reddy


Update the IMM version from A.2.1 to A.2.18 (latest version) im SMFD, to 
support saImmOmCcbGetErrorStrings.

The logic for return value for IMM operations has to be corrected  to support 
only TRY_AGAIN for "Resource abort".



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2431 smf: imm version changes need to be updated to latest

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2431] smf: imm version changes need to be updated to latest **

**Status:** review
**Milestone:** 5.17.08
**Created:** Tue Apr 18, 2017 12:49 PM UTC by Neelakanta Reddy
**Last Updated:** Tue Apr 18, 2017 12:49 PM UTC
**Owner:** Neelakanta Reddy


Update the IMM version from A.2.1 to A.2.18 (latest version) im SMFD, to 
support saImmOmCcbGetErrorStrings.

The logic for return value for IMM operations has to be corrected  to support 
only TRY_AGAIN for "Resource abort".



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2431 smf: imm version changes need to be updated to latest

[Neelakanta Reddy]

---

** [tickets:#2431] smf: imm version changes need to be updated to latest **

**Status:** accepted
**Milestone:** 5.17.08
**Created:** Tue Apr 18, 2017 12:49 PM UTC by Neelakanta Reddy
**Last Updated:** Tue Apr 18, 2017 12:49 PM UTC
**Owner:** Neelakanta Reddy


Update the IMM version from A.2.1 to A.2.18 (latest version) im SMFD, to 
support saImmOmCcbGetErrorStrings.

The logic for return value for IMM operations has to be corrected  to support 
only TRY_AGAIN for "Resource abort".



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2413 smf: coredump, suspend is issued at completed state

[Neelakanta Reddy]

- Description has changed:

Diff:



--- old
+++ new
@@ -1,4 +1,4 @@
-ticket [#2145] looks to be causing this issue. 
+ticket #2145 looks to be causing this issue. 
 
 coredump printout is attached.
 



- **Comment**:

The following is the analysis:
1. From the FIGURE 7 from SMF AIS spec, async-failure is supported in the 
following campaign state:
SA_SMF_CMPG_EXECUTING
SA_SMF_CMPG_SUSPENDING_EXECUTION
SA_SMF_CMPG_ROLLING_BACK

>From the campaign perspective mark the campaign as 
>SA_SMF_CMPG_SUSPENDED_BY_ERROR_DETECTED only when
the present campaign state is one of the above. This will avoid smfd 
segmentation fault.

2. But, the saAmfSUMaintenanceCampaign will be reset(cleared) at the time of 
committing the campaign, the same has been said in section 4.2.1.3 of SMF AIS.

"When an upgrade campaign is committed, the Software Management Framework
must reset all the maintenance status attributes that refer to the campaign 
being committed.
Beyond this point, it cannot determine whether a failed entity was upgraded
by the campaign or not."

when the component is failed, in the states other than above states(like 
SA_SMF_CMPG_EXECUTION_COMPLETED)
the amfnd will not restart, since saAmfSUMaintenanceCampaign is not yet reset. 
Ideally the failed component has to be reset
because the campaign will not be moved to error state.



---

** [tickets:#2413] smf: coredump, suspend is issued at completed state**

**Status:** unassigned
**Milestone:** 5.2.0
**Created:** Wed Apr 05, 2017 12:39 PM UTC by Rafael
**Last Updated:** Thu Apr 06, 2017 10:35 AM UTC
**Owner:** nobody
**Attachments:**

- 
[osafsmfd.9276.SC-2.core.txt](https://sourceforge.net/p/opensaf/tickets/2413/attachment/osafsmfd.9276.SC-2.core.txt)
 (15.4 kB; text/plain)


ticket #2145 looks to be causing this issue. 

coredump printout is attached.

Steps to reproduce: run a campaign and have AMF compenent fail at the campaign 
completed state. This triggers a event in SMF which tries to suspend a 
completed campaign.

Function handleAmfObjectStateChangeNotification will try to call asyncFailure() 
which is the same as suspend() because the campaign is completed and commited 
this is not a valid transition. The campaign state instance is most likely 
deleted therefore we get a coredump.

For reference refer to figures 5, 6, 7 in SMF AIS. Starting from section 5.1.3


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1889 Immnd crashed on Payload during headless operation

[Neelakanta Reddy]

- **status**: needinfo --> wontfix
- **Comment**:

Reopen, the defect with sufficient logs



---

** [tickets:#1889] Immnd crashed on Payload during headless operation**

**Status:** wontfix
**Milestone:** future
**Created:** Tue Jun 21, 2016 09:50 AM UTC by Ritu Raj
**Last Updated:** Tue Nov 08, 2016 07:11 AM UTC
**Owner:** nobody
**Attachments:**

- 
[SC-1.tar.bz2](https://sourceforge.net/p/opensaf/tickets/1889/attachment/SC-1.tar.bz2)
 (7.6 MB; application/x-bzip)
- 
[SCALE_SLOT-75.tar.bz2](https://sourceforge.net/p/opensaf/tickets/1889/attachment/SCALE_SLOT-75.tar.bz2)
 (4.8 MB; application/x-bzip)


setup:
Version - opensaf 5.0.GA
6-Node cluster(SC-1:Active, SC-2:Standby, SC-3:Spare PL:4,PL-5: Payloads)

* Issue Observed:
Immnd crashed on Payload during headless operation

* Steps performed: 
(1). Invoke headless 
(2). Created logsv application stream after headless
(3). Closed the stream after performing write operation
(4). While reverting back to default configuration one of the CCB operation 
failed

>> SCALE_SLOT-75 osafimmnd[18906]: WA ERR_FAILED_OPERATION: ccb 1 is not in an 
>> expected state: 11 rejecting ccbObjectModify operation
>>
immcfg -a saLogStreamLogFullAction=3 
safLgStrCfg=saLogNotification,safApp=safLogService
error - saImmOmCcbObjectModify_2 FAILED: SA_AIS_ERR_FAILED_OPERATION (21)
OI reports: IMM: Resource abort: CCB is not in an expected state
error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21)

(5). On invoking second headless immnd crashed on both the payload

>>
Jun 21 14:27:53 SCALE_SLOT-75 osafimmnd[18906]: ImmModel.cc:648: 
immModel_abortNonCriticalCcbs: **Assertion 'immModel_ccbAbort(cb, (*i3)->mId, 
, , , , , )' 
failed**.
Jun 21 14:27:53 SCALE_SLOT-75 osafamfnd[18925]: NO 
'safSu=PL-5,safSg=NoRed,safApp=OpenSAF' component restart probation timer 
started (timeout: 600 ns)
Jun 21 14:27:53 SCALE_SLOT-75 osafamfnd[18925]: NO Restarting a component of 
'safSu=PL-5,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1)
Jun 21 14:27:53 SCALE_SLOT-75 osafamfnd[18925]: NO 
'**safComp=IMMND,safSu=PL-5,safSg=NoRed,safApp=OpenSAF' faulted** due to 
'avaDown' : Recovery is 'componentRestart'
Jun 21 14:27:53 SCALE_SLOT-75 osafimmnd[19167]: Started


* Syslog and Immnd trace file is attached


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1868 Headless: IMM: Cluster reset happened due to 'avaDown' while killing immd

[Neelakanta Reddy]

- **status**: unassigned --> wontfix
- **Comment**:

The problem and the logs share are not matching, share the correct logs.



---

** [tickets:#1868] Headless: IMM: Cluster reset happened due to 'avaDown' while 
killing immd**

**Status:** wontfix
**Milestone:** future
**Created:** Wed Jun 08, 2016 12:45 PM UTC by Chani Srivastava
**Last Updated:** Tue Nov 08, 2016 09:04 AM UTC
**Owner:** nobody
**Attachments:**

- 
[syslog_PL5](https://sourceforge.net/p/opensaf/tickets/1868/attachment/syslog_PL5)
 (153.5 kB; application/octet-stream)
- 
[syslog_SC1](https://sourceforge.net/p/opensaf/tickets/1868/attachment/syslog_SC1)
 (173.4 kB; application/octet-stream)
- 
[syslog_SC2](https://sourceforge.net/p/opensaf/tickets/1868/attachment/syslog_SC2)
 (147.6 kB; application/octet-stream)
- 
[syslog_SC3](https://sourceforge.net/p/opensaf/tickets/1868/attachment/syslog_SC3)
 (124.9 kB; application/octet-stream)


setup:
Version - opensaf 5.0.GA
6-Node cluster(SC-1:Active, SC-2:Standby, SC-3:Spare PL:4,PL-5: Payloads)

Step to reproduce:
1. Install and bring up opensaf on 6 nodes in cluster with with Active, 
Stanbdy, Spare and 3 Payloads
2. Take cluster in headless state by killing immd onActive Controller first 
followed by Standby and Spare controller.
3. IMMD got crashed due to avaDown andf cluster reset happened.

> Jun  8 15:35:53 SCALE_SLOT-81 osafimmnd[1806]: NO SERVER STATE: 
> IMM_SERVER_SYNC_SERVER --> IMM_SERVER_READY
Jun  8 15:35:53 SCALE_SLOT-81 osafimmd[1756]: NO ACT: New Epoch for IMMND 
process at node 2060f old epoch: 0  new epoch:104
Jun  8 15:35:54 SCALE_SLOT-81 osafamfd[1852]: NO Received node_up from 2060f: 
msg_id 1
Jun  8 15:35:54 SCALE_SLOT-81 osafamfd[1852]: NO Node 'PL-6' joined the cluster
Jun  8 15:35:56 SCALE_SLOT-81 osafimmnd[1806]: NO Implementer connected: 748 
(MsgQueueService132623) <0, 2060f>
Jun  8 15:43:50 SCALE_SLOT-81 osafimmnd[1806]: NO ERR_BAD_OPERATION: parent 
object not owned by 'SetUp_Ccb'
Jun  8 15:43:50 SCALE_SLOT-81 osafimmnd[1806]: NO ERR_BAD_OPERATION: parent 
object not owned by 'SetUp_Ccb'
Jun  8 15:43:52 SCALE_SLOT-81 osafimmnd[1806]: NO Implementer connected: 749 
(RUNTIMEIMPL) <0, 2050f>
Jun  8 15:44:06 SCALE_SLOT-81 sshd[3213]: Accepted keyboard-interactive/pam for 
root from 192.2.8.94 port 37187 ssh2
Jun  8 15:44:07 SCALE_SLOT-81 root: killing osafimmd from run_headless.sh on 
spare controller
Jun  8 15:44:07 SCALE_SLOT-81 osafamfnd[1863]: NO 
'safComp=IMMD,safSu=SC-1,safSg=2N,safApp=OpenSAF' faulted due to 'avaDown' : 
Recovery is 'nodeFailfast'
Jun  8 15:44:07 SCALE_SLOT-81 osafamfnd[1863]: **ER 
safComp=IMMD,safSu=SC-1,safSg=2N,safApp=OpenSAF Faulted due to:avaDown Recovery 
is:nodeFailfast
Jun  8 15:44:07 SCALE_SLOT-81 osafamfnd[1863]: Rebooting OpenSAF NodeId = 
131343 EE Name = , Reason: Component faulted: recovery is node failfast, 
OwnNodeId = 131343, SupervisionTime = 60**
Jun  8 15:44:07 SCALE_SLOT-81 osafimmnd[1806]: WA DISCARD DUPLICATE FEVS 
message:67683
Jun  8 15:44:07 SCALE_SLOT-81 osafimmnd[1806]: WA Error code 2 returned for 
message type 82 - ignoring
Jun  8 15:44:07 SCALE_SLOT-81 osafimmnd[1806]: WA DISCARD DUPLICATE FEVS 
message:67684
Jun  8 15:44:07 SCALE_SLOT-81 osafimmnd[1806]: WA Error code 2 returned for 
message type 82 - ignoring
Jun  8 15:44:07 SCALE_SLOT-81 opensaf_reboot: Rebooting local node; timeout=60

> 
Attaching syslogs for controllers and payload in action
Traces are huge in size. Will share seperately

Note: Machines are not sync with timings. Current logs are the ones after June 8


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2343 IMM: immnd failed to spawn while starting opensaf on controller

[Neelakanta Reddy]

- **status**: assigned --> wontfix
- **Comment**:

check if there is any link loss in the cluster.
re-open the ticket if the problem is not related to link loss and provide the 
requested information.



---

** [tickets:#2343] IMM: immnd failed to spawn while starting opensaf on 
controller**

**Status:** wontfix
**Milestone:** future
**Created:** Fri Mar 03, 2017 11:46 AM UTC by Chani Srivastava
**Last Updated:** Mon Mar 13, 2017 10:06 AM UTC
**Owner:** Neelakanta Reddy


**Environment details**

OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads with 1PBE enabled )

Summary

immnd failed to spawn a number of times while starting openSaf on controller.
This issue is observed in various situations

1. While resetting cluster and starting OpenSaf again
2. While invoking continuous failovers.
3. While stoping and starting openSaf on standby controller.



Mar  3 15:45:49 OSAF-SC1 opensafd: Starting OpenSAF Services(5.2.FC - ) (Using 
TIPC)
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828240] TIPC: Activated (version 2.0.0)
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828391] NET: Registered protocol family 
30
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828393] TIPC: Started in single node 
mode
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.834836] TIPC: Started in network mode
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.834839] TIPC: Own node address <1.1.1>, 
network identity 4141
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.838982] TIPC: Enabled bearer 
, discovery domain <1.1.0>, priority 10
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.840611] TIPC: Established link 
<1.1.1:eth1-1.1.2:eth1> on network plane A
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.840688] TIPC: Established link 
<1.1.1:eth1-1.1.3:eth1> on network plane A
Mar  3 15:45:49 OSAF-SC1 osaftransportd[3854]: mkfifo already exists: 
/var/lib/opensaf/osaftransportd.fifo File exists
Mar  3 15:45:49 OSAF-SC1 osaftransportd[3854]: Started
Mar  3 15:45:49 OSAF-SC1 opensafd[3830]: NO Monitoring of TRANSPORT started
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: mkfifo already exists: 
/var/lib/opensaf/osafclmna.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: Started
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of CLMNA started
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: NO 
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Mar  3 15:45:50 OSAF-SC1 osafrded[3870]: mkfifo already exists: 
/var/lib/opensaf/osafrded.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafrded[3870]: Started
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: mkfifo already exists: 
/var/lib/opensaf/osaffmd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: Started
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: NO Remote fencing is disabled
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of HLFM started
Mar  3 15:45:50 OSAF-SC1 osafimmd[3889]: mkfifo already exists: 
/var/lib/opensaf/osafimmd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafimmd[3889]: Started
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of IMMD started
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: mkfifo already exists: 
/var/lib/opensaf/osafimmnd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: Started
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO Persistent Back-End capability 
configured, Pbe file:imm.db (suffix may get added)
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO IMMD service is UP ... 
ScAbsenseAllowed?:0 introduced?:0
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: IMM_SERVER_ANONYMOUS 
--> IMM_SERVER_CLUSTER_WAITING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_ISOLATED
Mar  3 15:45:51 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Mar  3 15:45:51 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: WA Global ABORT SYNC received for 
epoch 508
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: WA SERVER STATE: 
IMM_SERVER_SYNC_CLIENT --> IMM_SERVER_LOADING_PENDING (sync aborted)
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_UNKNOW 2827
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: NO Abort sync: Discarding synced 
objects
Mar  3 15:51:04 OSAF-SC1 osafimmnd[3900]: NO Abort sync: Discarding synced 
classes
Mar  3 15:51:04 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar  3 15:51:05 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_ISOLATED
Mar  3 15:51:06 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Mar  3 15:51:06 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar  3 15:51:41 OSAF-SC1 osafimmnd[3900]: NO Implem

[tickets] [opensaf:tickets] #2388 imm: active node rebooted due immd assertion failure

[Neelakanta Reddy]

- **status**: assigned --> invalid
- **Comment**:

4.7 is not supported from OpenSAF perspective.
closing this defect as invalid



---

** [tickets:#2388] imm: active node rebooted due immd assertion failure**

**Status:** invalid
**Milestone:** 5.2.0
**Created:** Tue Mar 21, 2017 07:18 AM UTC by M Chandrasekhar
**Last Updated:** Fri Mar 24, 2017 11:38 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[logs.tar](https://sourceforge.net/p/opensaf/tickets/2388/attachment/logs.tar) 
(38.0 MB; application/octet-stream)


###Environment details

OS : Suse 64bit
Setup : 4 nodes ( 2 controllers and 2 payloads with 1PBE enabled )
SC-1 and PL-3 installed with 4.7GA
SC-2 and PL-4 installed with 5.2RC1

###Summary
Active controller got rebooted due to immd got assertion failure after few 
immnd restarts.

steps followed:
1. bring up SC-1 and PL-3 with 4.7GA version
2. bring up SC-2 and PL-4 with 5.2RC version 
3. do si-swap, and make SC-2 active
3. run few regression tests and immnd restarts and issue was noticed.


Mar 20 23:38:02 fos2 osafimmnd[27544]: NO NODE STATE-> IMM_NODE_FULLY_AVAILABLE 
2927
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2010f old epoch: 29  new epoch:30
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO RepositoryInitModeT is 
SA_IMM_KEEP_REPOSITORY
Mar 20 23:38:02 fos2 osafimmnd[27544]: WA IMM Access Control mode is DISABLED!
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Epoch set to 30 in ImmModel
Mar 20 23:38:02 fos2 test_immsv: IN Received PROC_STALE_CLIENTS
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO SERVER STATE: IMM_SERVER_SYNC_CLIENT 
--> IMM_SERVER_READY
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO ImmModel received scAbsenceAllowed 0
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2030f old epoch: 29  new epoch:30
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2040f old epoch: 29  new epoch:30
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2020f old epoch: 0  new epoch:30
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 944 
(safSmfService) <315, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 945 
(safEvtService) <123, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 946 
(safLogService) <127, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 947 
(safCheckPointService) <134, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 948 
(safClmService) <131, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 949 
(safLckService) <135, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 950 
(MsgQueueService131599) <12777, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 951 
(safAmfService) <129, 2020f>
Mar 20 23:38:03 fos2 osafimmnd[27544]: NO Implementer (applier) connected: 952 
(@OpenSafImmReplicatorB) <13770, 2020f>
Mar 20 23:38:03 fos2 osafntfimcnd[27526]: NO Started
Mar 20 23:38:03 fos2 osafimmnd[27544]: NO PBE-OI established on other SC. 
Dumping incrementally to file imm.db
Mar 20 23:38:08 fos2 sudo:  tet : TTY=unknown ; PWD=/tmp/26815aa ; 
USER=root ; COMMAND=/bin/kill -9 27544
Mar 20 23:38:08 fos2 osafimmd[17384]: NO MDS event from svc_id 25 (change:4, 
dest:565217221926950)
Mar 20 23:38:08 fos2 osafamfnd[17445]: NO Restarting a component of 
'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 10)
Mar 20 23:38:08 fos2 osafamfnd[17445]: NO 
'safComp=IMMND,safSu=SC-2,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' 
: Recovery is 'componentRestart'
Mar 20 23:38:08 fos2 osafntfimcnd[27526]: NO saImmOiDispatch() Fail 
SA_AIS_ERR_BAD_HANDLE (9)
Mar 20 23:38:08 fos2 osafimmnd[27586]: mkfifo already exists: 
/var/lib/opensaf/osafimmnd.fifo File exists
Mar 20 23:38:08 fos2 osafimmnd[27586]: Started
Mar 20 23:38:08 fos2 osafimmnd[27586]: NO Persistent Back-End capability 
configured, Pbe file:imm.db (suffix may get added)
Mar 20 23:38:08 fos2 osafimmd[17384]: NO MDS event from svc_id 25 (change:3, 
dest:565217221935144)
Mar 20 23:38:08 fos2 osafimmnd[27586]: NO IMMD service is UP ... 
ScAbsenseAllowed?:0 introduced?:0
Mar 20 23:38:08 fos2 osafimmnd[27586]: NO SERVER STATE: IMM_SERVER_ANONYMOUS 
--> IMM_SERVER_CLUSTER_WAITING
Mar 20 23:38:08 fos2 osafimmnd[27586]: NO Fevs count adjusted to 64649 
preLoadPid: 0
Mar 20 23:38:08 fos2 osafimmnd[27586]: src/imm/immnd/immnd_evt.c:9125: 
immnd_evt_proc_fevs_rcv: Assertion '!reply_dest || (reply_dest == 
cb->immnd_mdest_id) || isObjSync' failed.
Mar 20 23:38:08 fos2 osafimmd[17384]: NO MDS event from svc_id 25 (change:4, 
dest:565217221935144)
Mar 20 23:38:08 fos2 osafamfnd[17445]: NO Restarting a component of 
'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 11)
Mar 20 23:38:08 fos2 osafamfnd[17445]: NO 
'safComp=IMMND,safSu=SC-2,safSg=NoRed,safA

[tickets] [opensaf:tickets] #2398 imm: retry of ccb abort should be allowed if failed with TRY_AGAIN and TIMEOUT

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8732:ea44141c05ee
branch:  opensaf-5.0.x
parent:  8727:9a1452dcd190
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Mar 28 16:25:09 2017 +0530
summary: retry ccbabort when failed with TRY_AGAIN and TIMEOUT[#2398]

changeset:   8733:be2fd9824bc4
branch:  opensaf-5.1.x
parent:  8728:bdd9cdb1ced9
user:Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Mar 28 16:25:09 2017 +0530
summary: retry ccbabort when failed with TRY_AGAIN and TIMEOUT[#2398]

changeset:   8734:5810bba59478
tag: tip
parent:  8731:52f7fab7b8a7
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Mar 28 16:30:11 2017 +0530
summary: imm:retry ccbabort when failed with TRY_AGAIN and TIMEOUT[#2398]




---

** [tickets:#2398] imm: retry of ccb abort should be allowed if failed with 
TRY_AGAIN and TIMEOUT**

**Status:** fixed
**Milestone:** 5.0.2
**Created:** Mon Mar 27, 2017 07:50 AM UTC by Neelakanta Reddy
**Last Updated:** Mon Mar 27, 2017 08:37 AM UTC
**Owner:** Neelakanta Reddy


steps :
1. create a ccb
2. saImmOmCcbAbort the ccb, the return code should be TRY_AGAIN, which can be 
re-produced when fevs queue is full
T2 Too many pending incoming FEVS messages (> 16) enqueueing async message. 
Backlog:1

The saImmOmCcbAbort ccb will create the imma_newCcbId, without finalizing old 
ccbid.

solution:
do not create new ccbid when the return code is TRY_AGAIN or TIMEOUT


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2391 IMM: OI should not receive callbacks on a locked node

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8730:50398de4f5bc
tag: tip
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Mar 28 11:49:41 2017 +0530
summary: imm:unregister local implementers when clm node is locked[#2391]




---

** [tickets:#2391] IMM: OI should not receive callbacks on a locked node**

**Status:** fixed
**Milestone:** 5.2.RC2
**Created:** Wed Mar 22, 2017 09:08 AM UTC by Chani Srivastava
**Last Updated:** Mon Mar 27, 2017 05:46 AM UTC
**Owner:** Neelakanta Reddy


**Environment details**

OS : Suse 64bit
Changeset : 8701 ( 5.2RC1)
Setup : 4 nodes

**Steps to Reproduce:**
* Create a test class
* Node1 - Initialize OM with A.2.18
* Node2 - Initialize OI with A.2.18
* Node2 - Make OI implementer for the test class created
* Node2 - Call OiDispatch
* Lock Node2
* Node1 - Try creating an object for test class for which OI is an implementer

OI receives CreateCallback and responds with SA_AIS_OK

**Expected**: On a clm locked node, OI should not receive any callback when 
initialize with A.2.18


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] Re: #2398 imm: retry of ccb abort should be allowed if failed with TRY_AGAIN and TIMEOUT

[Neelakanta Reddy]

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 SA_AIS_OK in library.


---

** [tickets:#2398] imm: retry of ccb abort should be allowed if failed with 
TRY_AGAIN and TIMEOUT**

**Status:** review
**Milestone:** 5.0.2
**Created:** Mon Mar 27, 2017 07:50 AM UTC by Neelakanta Reddy
**Last Updated:** Mon Mar 27, 2017 08:37 AM UTC
**Owner:** Neelakanta Reddy


steps :
1. create a ccb
2. saImmOmCcbAbort the ccb, the return code should be TRY_AGAIN, which can be 
re-produced when fevs queue is full
T2 Too many pending incoming FEVS messages (> 16) enqueueing async message. 
Backlog:1

The saImmOmCcbAbort ccb will create the imma_newCcbId, without finalizing old 
ccbid.

solution:
do not create new ccbid when the return code is TRY_AGAIN or TIMEOUT


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2398 imm: retry of ccb abort should be allowed if failed with TRY_AGAIN and TIMEOUT

[Neelakanta Reddy]

- **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 
TRY_AGAIN and TIMEOUT**

**Status:** review
**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 :
1. create a ccb
2. saImmOmCcbAbort the ccb, the return code should be TRY_AGAIN, which can be 
re-produced when fevs queue is full
T2 Too many pending incoming FEVS messages (> 16) enqueueing async message. 
Backlog:1

The saImmOmCcbAbort ccb will create the imma_newCcbId, without finalizing old 
ccbid.

solution:
do not create new ccbid when the return code is TRY_AGAIN or TIMEOUT


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2398 imm: retry of cbb abort should be allowed if failed with TRY_AGAIN and TIMEOUT

[Neelakanta Reddy]

---

** [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 :
1. create a ccb
2. saImmOmCcbAbort the ccb, the return code should be TRY_AGAIN, which can be 
re-produced when fevs queue is full
T2 Too many pending incoming FEVS messages (> 16) enqueueing async message. 
Backlog:1

The saImmOmCcbAbort ccb will create the imma_newCcbId, without finalizing old 
ccbid.

solution:
do not create new ccbid when the return code is TRY_AGAIN or TIMEOUT


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2391 IMM: OI should not receive callbacks on a locked node

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2391] IMM: OI should not receive callbacks on a locked node**

**Status:** review
**Milestone:** 5.2.RC2
**Created:** Wed Mar 22, 2017 09:08 AM UTC by Chani Srivastava
**Last Updated:** Thu Mar 23, 2017 12:14 PM UTC
**Owner:** Neelakanta Reddy


**Environment details**

OS : Suse 64bit
Changeset : 8701 ( 5.2RC1)
Setup : 4 nodes

**Steps to Reproduce:**
* Create a test class
* Node1 - Initialize OM with A.2.18
* Node2 - Initialize OI with A.2.18
* Node2 - Make OI implementer for the test class created
* Node2 - Call OiDispatch
* Lock Node2
* Node1 - Try creating an object for test class for which OI is an implementer

OI receives CreateCallback and responds with SA_AIS_OK

**Expected**: On a clm locked node, OI should not receive any callback when 
initialize with A.2.18


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2388 imm: active node rebooted due immd assertion failure

[Neelakanta Reddy]

Please, try to reproduce again: 
share the following logs from all the nodes :
1) IMMD traces from starting of the service
2) syslog
3) IMMND traces (if they are big, share from the time of immnd tests)


---

** [tickets:#2388] imm: active node rebooted due immd assertion failure**

**Status:** assigned
**Milestone:** 5.2.RC2
**Created:** Tue Mar 21, 2017 07:18 AM UTC by M Chandrasekhar
**Last Updated:** Fri Mar 24, 2017 10:58 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[logs.tar](https://sourceforge.net/p/opensaf/tickets/2388/attachment/logs.tar) 
(38.0 MB; application/octet-stream)


###Environment details

OS : Suse 64bit
Setup : 4 nodes ( 2 controllers and 2 payloads with 1PBE enabled )
SC-1 and PL-3 installed with 4.7GA
SC-2 and PL-4 installed with 5.2RC1

###Summary
Active controller got rebooted due to immd got assertion failure after few 
immnd restarts.

steps followed:
1. bring up SC-1 and PL-3 with 4.7GA version
2. bring up SC-2 and PL-4 with 5.2RC version 
3. do si-swap, and make SC-2 active
3. run few regression tests and immnd restarts and issue was noticed.


Mar 20 23:38:02 fos2 osafimmnd[27544]: NO NODE STATE-> IMM_NODE_FULLY_AVAILABLE 
2927
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2010f old epoch: 29  new epoch:30
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO RepositoryInitModeT is 
SA_IMM_KEEP_REPOSITORY
Mar 20 23:38:02 fos2 osafimmnd[27544]: WA IMM Access Control mode is DISABLED!
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Epoch set to 30 in ImmModel
Mar 20 23:38:02 fos2 test_immsv: IN Received PROC_STALE_CLIENTS
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO SERVER STATE: IMM_SERVER_SYNC_CLIENT 
--> IMM_SERVER_READY
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO ImmModel received scAbsenceAllowed 0
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2030f old epoch: 29  new epoch:30
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2040f old epoch: 29  new epoch:30
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2020f old epoch: 0  new epoch:30
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 944 
(safSmfService) <315, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 945 
(safEvtService) <123, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 946 
(safLogService) <127, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 947 
(safCheckPointService) <134, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 948 
(safClmService) <131, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 949 
(safLckService) <135, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 950 
(MsgQueueService131599) <12777, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 951 
(safAmfService) <129, 2020f>
Mar 20 23:38:03 fos2 osafimmnd[27544]: NO Implementer (applier) connected: 952 
(@OpenSafImmReplicatorB) <13770, 2020f>
Mar 20 23:38:03 fos2 osafntfimcnd[27526]: NO Started
Mar 20 23:38:03 fos2 osafimmnd[27544]: NO PBE-OI established on other SC. 
Dumping incrementally to file imm.db
Mar 20 23:38:08 fos2 sudo:  tet : TTY=unknown ; PWD=/tmp/26815aa ; 
USER=root ; COMMAND=/bin/kill -9 27544
Mar 20 23:38:08 fos2 osafimmd[17384]: NO MDS event from svc_id 25 (change:4, 
dest:565217221926950)
Mar 20 23:38:08 fos2 osafamfnd[17445]: NO Restarting a component of 
'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 10)
Mar 20 23:38:08 fos2 osafamfnd[17445]: NO 
'safComp=IMMND,safSu=SC-2,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' 
: Recovery is 'componentRestart'
Mar 20 23:38:08 fos2 osafntfimcnd[27526]: NO saImmOiDispatch() Fail 
SA_AIS_ERR_BAD_HANDLE (9)
Mar 20 23:38:08 fos2 osafimmnd[27586]: mkfifo already exists: 
/var/lib/opensaf/osafimmnd.fifo File exists
Mar 20 23:38:08 fos2 osafimmnd[27586]: Started
Mar 20 23:38:08 fos2 osafimmnd[27586]: NO Persistent Back-End capability 
configured, Pbe file:imm.db (suffix may get added)
Mar 20 23:38:08 fos2 osafimmd[17384]: NO MDS event from svc_id 25 (change:3, 
dest:565217221935144)
Mar 20 23:38:08 fos2 osafimmnd[27586]: NO IMMD service is UP ... 
ScAbsenseAllowed?:0 introduced?:0
Mar 20 23:38:08 fos2 osafimmnd[27586]: NO SERVER STATE: IMM_SERVER_ANONYMOUS 
--> IMM_SERVER_CLUSTER_WAITING
Mar 20 23:38:08 fos2 osafimmnd[27586]: NO Fevs count adjusted to 64649 
preLoadPid: 0
Mar 20 23:38:08 fos2 osafimmnd[27586]: src/imm/immnd/immnd_evt.c:9125: 
immnd_evt_proc_fevs_rcv: Assertion '!reply_dest || (reply_dest == 
cb->immnd_mdest_id) || isObjSync' failed.
Mar 20 23:38:08 fos2 osafimmd[17384]: NO MDS event from svc_id 25 (change:4, 
dest:565217221935144)
Mar 20 23:38:08 fos2 osafamfnd[17445]: NO Restarting a component of 
'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 11)
Mar 20 23:38:0

[tickets] [opensaf:tickets] #2388 imm: active node rebooted due immd assertion failure

[Neelakanta Reddy]

- **status**: unassigned --> assigned
- **assigned_to**: Neelakanta Reddy
- **Comment**:

The Assertion src/imm/immd/immd_evt.c:813: immd_accept_node: Assertion 
'node_info->immnd_key != cb->node_id' failed.

1. The cb->node_id will be updated at immd_mds_register
The cb->node_id  has to be 2020f, since it is 2020f
2. The node arrived is :
LOG_NO("Extended intro from node %x", node_info->immnd_key);
Mar 20 23:38:09.111387 osafimmd [17384:src/imm/immd/immd_evt.c:1563] NO 
Extended intro from node 2020f

Means "node_info->immnd_key is 2020f from above trace print"

There should be some memory corruption problem over here.
For how many IMMND restarts does you observe this, the shared immd logs are not 
from starting.



---

** [tickets:#2388] imm: active node rebooted due immd assertion failure**

**Status:** assigned
**Milestone:** 5.2.RC2
**Created:** Tue Mar 21, 2017 07:18 AM UTC by M Chandrasekhar
**Last Updated:** Tue Mar 21, 2017 07:18 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[logs.tar](https://sourceforge.net/p/opensaf/tickets/2388/attachment/logs.tar) 
(38.0 MB; application/octet-stream)


###Environment details

OS : Suse 64bit
Setup : 4 nodes ( 2 controllers and 2 payloads with 1PBE enabled )
SC-1 and PL-3 installed with 4.7GA
SC-2 and PL-4 installed with 5.2RC1

###Summary
Active controller got rebooted due to immd got assertion failure after few 
immnd restarts.

steps followed:
1. bring up SC-1 and PL-3 with 4.7GA version
2. bring up SC-2 and PL-4 with 5.2RC version 
3. do si-swap, and make SC-2 active
3. run few regression tests and immnd restarts and issue was noticed.


Mar 20 23:38:02 fos2 osafimmnd[27544]: NO NODE STATE-> IMM_NODE_FULLY_AVAILABLE 
2927
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2010f old epoch: 29  new epoch:30
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO RepositoryInitModeT is 
SA_IMM_KEEP_REPOSITORY
Mar 20 23:38:02 fos2 osafimmnd[27544]: WA IMM Access Control mode is DISABLED!
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Epoch set to 30 in ImmModel
Mar 20 23:38:02 fos2 test_immsv: IN Received PROC_STALE_CLIENTS
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO SERVER STATE: IMM_SERVER_SYNC_CLIENT 
--> IMM_SERVER_READY
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO ImmModel received scAbsenceAllowed 0
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2030f old epoch: 29  new epoch:30
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2040f old epoch: 29  new epoch:30
Mar 20 23:38:02 fos2 osafimmd[17384]: NO ACT: New Epoch for IMMND process at 
node 2020f old epoch: 0  new epoch:30
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 944 
(safSmfService) <315, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 945 
(safEvtService) <123, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 946 
(safLogService) <127, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 947 
(safCheckPointService) <134, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 948 
(safClmService) <131, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 949 
(safLckService) <135, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 950 
(MsgQueueService131599) <12777, 2020f>
Mar 20 23:38:02 fos2 osafimmnd[27544]: NO Implementer connected: 951 
(safAmfService) <129, 2020f>
Mar 20 23:38:03 fos2 osafimmnd[27544]: NO Implementer (applier) connected: 952 
(@OpenSafImmReplicatorB) <13770, 2020f>
Mar 20 23:38:03 fos2 osafntfimcnd[27526]: NO Started
Mar 20 23:38:03 fos2 osafimmnd[27544]: NO PBE-OI established on other SC. 
Dumping incrementally to file imm.db
Mar 20 23:38:08 fos2 sudo:  tet : TTY=unknown ; PWD=/tmp/26815aa ; 
USER=root ; COMMAND=/bin/kill -9 27544
Mar 20 23:38:08 fos2 osafimmd[17384]: NO MDS event from svc_id 25 (change:4, 
dest:565217221926950)
Mar 20 23:38:08 fos2 osafamfnd[17445]: NO Restarting a component of 
'safSu=SC-2,safSg=NoRed,safApp=OpenSAF' (comp restart count: 10)
Mar 20 23:38:08 fos2 osafamfnd[17445]: NO 
'safComp=IMMND,safSu=SC-2,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' 
: Recovery is 'componentRestart'
Mar 20 23:38:08 fos2 osafntfimcnd[27526]: NO saImmOiDispatch() Fail 
SA_AIS_ERR_BAD_HANDLE (9)
Mar 20 23:38:08 fos2 osafimmnd[27586]: mkfifo already exists: 
/var/lib/opensaf/osafimmnd.fifo File exists
Mar 20 23:38:08 fos2 osafimmnd[27586]: Started
Mar 20 23:38:08 fos2 osafimmnd[27586]: NO Persistent Back-End capability 
configured, Pbe file:imm.db (suffix may get added)
Mar 20 23:38:08 fos2 osafimmd[17384]: NO MDS event from svc_id 25 (change:3, 
dest:565217221935144)
Mar 20 23:38:08 fos2 osafimmnd[27586]: NO IMMD service is UP ... 
ScAbsenseAllowed?:0 introduced?:0
Mar 20 23:38:08 fos2 osafimmnd[27586]: NO SERVER STATE: IMM_

[tickets] [opensaf:tickets] #2214 SMF: ONE-STEP upgrade failed with AU/DU on component level

[Neelakanta Reddy]

- **Milestone**: 5.2.RC2 --> future



---

** [tickets:#2214] SMF: ONE-STEP upgrade failed with AU/DU on component level**

**Status:** unassigned
**Milestone:** future
**Created:** Fri Dec 02, 2016 10:11 AM UTC by Tai Dinh
**Last Updated:** Fri Dec 02, 2016 10:11 AM UTC
**Owner:** nobody


SmfAdminOperation::getAdminState does not handle component object lead to 
campaign failed to be executed.

In the comment it is clearly said that "If the unit is a component presence 
state is fetched", but the code does not look to be matched.

// Admin state shall be read from a SU object or a Node object
if (i_objectName.find("safSu") != std::string::npos) {
SaImmAttrNameT suAdminStateAttr[] = {
const_cast ("saAmfSUAdminState"),
NULL
};
m_errno = immutil_saImmOmAccessorGet_2(m_accessorHandle,
 ,
 suAdminStateAttr,
 );
   
This if condition is matched for both SU and component, but saAmfSUAdminState 
is only available for SU.

Dec  2 20:38:25 SC-2-1 osafsmfd[15855]: NO Waiting for bundle command execution 
to finish on all affected nodes
Dec  2 20:38:25 SC-2-1 osafsmfd[15855]: NO STEP: Lock activation units
Dec  2 20:38:25 SC-2-1 osafimmnd[15740]: NO ERR_NOT_EXIST: Some attributeNames 
did not exist in Object 
'safComp=TestComp,safSu=SC-1,safSg=2N,safApp=ERIC-TestApp' (nrof names:1 
matched:0)
Dec  2 20:38:25 SC-2-1 osafsmfd[15855]: NO getAdminState saImmOmAccessorGet_2 
Fail SA_AIS_ERR_NOT_EXIST (12)
Dec  2 20:38:25 SC-2-1 osafsmfd[15855]: NO saveInitAndCurrentStateForAllUnits: 
getAdminStateForUnit() Fail SA_AIS_ERR_NOT_EXIST (12)
Dec  2 20:38:25 SC-2-1 osafsmfd[15855]: NO lock: 
saveInitAndCurrentStateForAllUnits() Fail SA_AIS_ERR_NOT_EXIST (12)
Dec  2 20:38:25 SC-2-1 osafsmfd[15855]: ER Failed to Lock activation units in 
step=safSmfStep=0001
Dec  2 20:38:25 SC-2-1 osafsmfd[15855]: ER Step undoing failed
Dec  2 20:38:25 SC-2-1 osafsmfd[15855]: NO Step safSmfStep=0001 in procedure 
safSmfProc=SmfSSMergedProc failed, step result 5
Dec  2 20:38:25 SC-2-1 osafsmfd[15855]: NO CAMP: Procedure 
safSmfProc=SmfSSMergedProc returned FAILED


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2227 smf:ONE-STEP upgrade failed due to duplicated entities in comp and SU

[Neelakanta Reddy]

- **Milestone**: 5.2.RC2 --> future



---

** [tickets:#2227] smf:ONE-STEP upgrade failed due to duplicated entities in 
comp and SU**

**Status:** unassigned
**Milestone:** future
**Created:** Tue Dec 13, 2016 06:16 AM UTC by Neelakanta Reddy
**Last Updated:** Tue Dec 13, 2016 06:16 AM UTC
**Owner:** nobody


This Ticket is extension of #2209.
In #2209 if a campaign contains both rolling and singlestep.
The singlestep contains duplicated node forAddremove AU/DU present in the 
rolling upgrad also.

This ticket is related to duplcated entities SU and comp present in 
forAddRemove and rolling procedure.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2391 IMM: OI should not receive callbacks on a locked node

[Neelakanta Reddy]

- **status**: assigned --> accepted



---

** [tickets:#2391] IMM: OI should not receive callbacks on a locked node**

**Status:** accepted
**Milestone:** 5.2.RC2
**Created:** Wed Mar 22, 2017 09:08 AM UTC by Chani Srivastava
**Last Updated:** Thu Mar 23, 2017 06:57 AM UTC
**Owner:** Neelakanta Reddy


**Environment details**

OS : Suse 64bit
Changeset : 8701 ( 5.2RC1)
Setup : 4 nodes

**Steps to Reproduce:**
* Create a test class
* Node1 - Initialize OM with A.2.18
* Node2 - Initialize OI with A.2.18
* Node2 - Make OI implementer for the test class created
* Node2 - Call OiDispatch
* Lock Node2
* Node1 - Try creating an object for test class for which OI is an implementer

OI receives CreateCallback and responds with SA_AIS_OK

**Expected**: On a clm locked node, OI should not receive any callback when 
initialize with A.2.18


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2389 smf: retry of ccb operations when failed with resouce abort

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8723:7084e687e017
tag: tip
parent:  8720:057a8a4b1a99
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Thu Mar 23 15:34:50 2017 +0530
summary: smf: retry of ccb operations when failed with resouce abort[#2389]

changeset:   8722:9c295151f262
branch:  opensaf-5.1.x
parent:  8719:263af6bf5c65
user:Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Thu Mar 23 15:30:54 2017 +0530
summary: smf: retry of ccb operations when failed with resouce abort[#2389]

changeset:   8721:b2e2a9162664
branch:  opensaf-5.0.x
parent:  8718:8d305dff2257
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Thu Mar 23 15:30:54 2017 +0530
summary: smf: retry of ccb operations when failed with resouce abort[#2389]




---

** [tickets:#2389] smf: retry of ccb operations when failed with resouce abort**

**Status:** fixed
**Milestone:** 5.0.2
**Created:** Tue Mar 21, 2017 01:08 PM UTC by Neelakanta Reddy
**Last Updated:** Tue Mar 21, 2017 01:26 PM UTC
**Owner:** Neelakanta Reddy


This is the extension of #2277, which adds TRY_AGAIN for modify operation.

In this defect, TRY_AGAIN is added for create, delete and apply ccb operation 
when the ccb is aborted with RESOUCE ABORT error string


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2391 IMM: OI should not receive callbacks on a locked node

[Neelakanta Reddy]

- **Part**: doc --> nd
- **Comment**:

>From The README:

IMMD is not yet integrated, as the IMMND has to services to clients with lesser 
versions.
IMMND has to be UP even if the CLM node is down. The IMMD integration has to be 
done along
with Enhanced cluster management(#439).

since IMMND is up, on the CLM locked node, OI is receiving callback and 
responds.

>From the IMM spec:
When the cluster node leaves the membership, the IMM Service executing on the
remaining nodes of the cluster behaves as if all processes that were using the 
IMM
Service on the leaving cluster node had been terminated. **In particular, if a 
process on
the leaving cluster node was registered as an Object Implementer, the IMM 
Service
will unregister it automatically**

Following is the observation:

1. since, to service clients with lesser version, IMMND is not down on the node 
the same has been updated in README.
2. when calling object implementer registered with A.02.18, the callback is 
allowed as there is no proper return code and implementers are not unregistered.

solution:
when the node is locked, and there are OI registered with A.02.18 with 
implementers, then these implementers will be unregistered.



---

** [tickets:#2391] IMM: OI should not receive callbacks on a locked node**

**Status:** assigned
**Milestone:** 5.2.RC2
**Created:** Wed Mar 22, 2017 09:08 AM UTC by Chani Srivastava
**Last Updated:** Thu Mar 23, 2017 06:28 AM UTC
**Owner:** Neelakanta Reddy


**Environment details**

OS : Suse 64bit
Changeset : 8701 ( 5.2RC1)
Setup : 4 nodes

**Steps to Reproduce:**
* Create a test class
* Node1 - Initialize OM with A.2.18
* Node2 - Initialize OI with A.2.18
* Node2 - Make OI implementer for the test class created
* Node2 - Call OiDispatch
* Lock Node2
* Node1 - Try creating an object for test class for which OI is an implementer

OI receives CreateCallback and responds with SA_AIS_OK

**Expected**: On a clm locked node, OI should not receive any callback when 
initialize with A.2.18


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2391 IMM: OI should not receive callbacks on a locked node

[Neelakanta Reddy]

- **status**: unassigned --> assigned
- **assigned_to**: Neelakanta Reddy
- **Part**: - --> doc



---

** [tickets:#2391] IMM: OI should not receive callbacks on a locked node**

**Status:** assigned
**Milestone:** 5.2.RC2
**Created:** Wed Mar 22, 2017 09:08 AM UTC by Chani Srivastava
**Last Updated:** Wed Mar 22, 2017 09:08 AM UTC
**Owner:** Neelakanta Reddy


**Environment details**

OS : Suse 64bit
Changeset : 8701 ( 5.2RC1)
Setup : 4 nodes

**Steps to Reproduce:**
* Create a test class
* Node1 - Initialize OM with A.2.18
* Node2 - Initialize OI with A.2.18
* Node2 - Make OI implementer for the test class created
* Node2 - Call OiDispatch
* Lock Node2
* Node1 - Try creating an object for test class for which OI is an implementer

OI receives CreateCallback and responds with SA_AIS_OK

**Expected**: On a clm locked node, OI should not receive any callback when 
initialize with A.2.18


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2386 imm: decrement the pending reply when error is other than SA_AIS_OK when newCcbId is called

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8715:dae6b6197639
branch:  opensaf-5.0.x
parent:  8713:3a718e40acec
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Thu Mar 23 11:49:02 2017 +0530
summary: imm:decrement the pending reply when error is other than SA_AIS_OK 
when newCcbId is called [#2386]

changeset:   8716:8d149783d95a
branch:  opensaf-5.1.x
parent:  8712:a3ba6212ecf6
user:Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Thu Mar 23 11:49:02 2017 +0530
summary: imm:decrement the pending reply when error is other than SA_AIS_OK 
when newCcbId is called [#2386]

changeset:   8717:6cffd8965ae4
tag: tip
parent:  8714:ffb6233abe8b
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Thu Mar 23 11:52:55 2017 +0530
summary: imm:decrement the pending reply when error is other than SA_AIS_OK 
when newCcbId is called [#2386]




---

** [tickets:#2386] imm: decrement the pending reply when error is other than 
SA_AIS_OK when newCcbId is called**

**Status:** fixed
**Milestone:** 5.0.2
**Created:** Fri Mar 17, 2017 09:46 AM UTC by Neelakanta Reddy
**Last Updated:** Fri Mar 17, 2017 10:19 AM UTC
**Owner:** Neelakanta Reddy


After Ccb operation returned SA_AIS_ERR_FAILED_OPERATION, Ccbfinalize returned 
TRY_AGAIN due to "Too many pending incoming fevs messages (> 16)" .
In the imma_finalizeCcb, if the imma_newCcbId returns error other than 
SA_AIS_OK, imma_proc_decrement_pending_reply is not called.

solution is to call imma_proc_decrement_pending_reply when error is not 
SA_AIS_OK

logs:
IMMA
Mar 10 13:00:10.428430 imma [26655:imma_om_api.c:2907] TR objectDelete send 
RETURNED:1
Mar 10 13:00:10.428448 imma [26655:imma_om_api.c:3001] TR objectDelete really 
RETURNING:21
Mar 10 13:00:10.428456 imma [26655:imma_om_api.c:3002] << 
ccb_object_delete_common
Mar 10 13:00:10.428485 imma [26655:imma_om_api.c:9384] >> 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428496 imma [26655:imma_om_api.c:9391] >> 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428503 imma [26655:imma_om_api.c:9452] << 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428651 imma [26655:imma_om_api.c:8838] >> imma_finalizeCcb
Mar 10 13:00:10.428662 imma [26655:imma_om_api.c:8860] T1 CCb node found for 
ccbhandle 14aa837f7c79cc07 ccbid:4158
Mar 10 13:00:10.428670 imma [26655:imma_om_api.c:8929] TR Ccb is active when 
finalizing
Mar 10 13:00:10.428774 imma [26655:imma_om_api.c:5777] >> accessor_get_common
Mar 10 13:00:10.429358 imma [26655:imma_om_api.c:8956] TR CcbFinalize returned 6
Mar 10 13:00:10.429369 imma [26655:imma_om_api.c:1198] >> imma_newCcbId
Mar 10 13:00:10.429373 imma [26655:imma_om_api.c:1199] TR imma_newCcbId:create 
new ccb id with admoId:103603
Mar 10 13:00:10.429377 imma [26655:imma_om_api.c:1232] TR Sending request for 
new ccbid with admin OwnerId:103603
Mar 10 13:00:10.429684 imma [26655:imma_om_api.c:6120] << accessor_get_common
Mar 10 13:00:10.430233 imma [26655:imma_om_api.c:5777] >> accessor_get_common
Mar 10 13:00:10.430653 imma [26655:imma_om_api.c:1302] << imma_newCcbId
Mar 10 13:00:10.430663 imma [26655:imma_om_api.c:9070] << imma_finalizeCcb

IMMND:

Mar 10 13:00:10.430608 osafimmnd [8927:immsv_evt.c:5473] T8 Received: 
IMMND_EVT_A2ND_CCBINIT (15) from 2010f
Mar 10 13:00:10.430612 osafimmnd [8927:immnd_evt.c:2641] >> 
immnd_evt_proc_ccb_init
Mar 10 13:00:10.430615 osafimmnd [8927:immnd_evt.c:2666] T2 ERR_TRY_AGAIN: Too 
many pending incoming fevs messages (> 16) rejecting ccb_init request
Mar 10 13:00:10.430619 osafimmnd [8927:immnd_evt.c:2722] T2 SENDRSP FAIL 6
Mar 10 13:00:10.430627 osafimmnd [8927:immnd_evt.c:2725] << 
immnd_evt_proc_ccb_init



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2373 IMM: Object Implementer APIs giving BAD_ANDLE on a locked node

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2373] IMM: Object Implementer APIs giving BAD_ANDLE on a locked 
node**

**Status:** review
**Milestone:** 5.2.RC2
**Created:** Tue Mar 14, 2017 11:15 AM UTC by Chani Srivastava
**Last Updated:** Mon Mar 20, 2017 10:03 AM UTC
**Owner:** Neelakanta Reddy


**Environment details**

OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes

**Steps to Reproduce:**
1. Initialize OI a on a payload
2. Perform lock operation on that payload
3. Call saImmOiObjectImplementerSet()/saImmOiObjectImplementerRelease() with 
the handle obtained in step1

Step 3 returned with BAD_HANDLE

Expected: Step 3 should return ERR_UNAVAILABLE like 
saImmOiClassImplementerSet() and others


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2373 IMM: Object Implementer APIs giving BAD_ANDLE on a locked node

[Neelakanta Reddy]

- **status**: unassigned --> accepted
- **assigned_to**: Neelakanta Reddy
- **Part**: - --> lib
- **Version**:  --> 5.2
- **Comment**:

when the OI was initalized with version A.02.18 and CLM node is locked. 
saImmOiObjectImplementerSet()/saImmOiObjectImplementerRelease() must return 
ERR_UNAVAILABLE



---

** [tickets:#2373] IMM: Object Implementer APIs giving BAD_ANDLE on a locked 
node**

**Status:** accepted
**Milestone:** 5.2.RC2
**Created:** Tue Mar 14, 2017 11:15 AM UTC by Chani Srivastava
**Last Updated:** Tue Mar 14, 2017 11:15 AM UTC
**Owner:** Neelakanta Reddy


**Environment details**

OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes

**Steps to Reproduce:**
1. Initialize OI a on a payload
2. Perform lock operation on that payload
3. Call saImmOiObjectImplementerSet()/saImmOiObjectImplementerRelease() with 
the handle obtained in step1

Step 3 returned with BAD_HANDLE

Expected: Step 3 should return ERR_UNAVAILABLE like 
saImmOiClassImplementerSet() and others


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2379 smf:PR documentation for 5.2 release

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2379] smf:PR documentation for 5.2 release**

**Status:** review
**Milestone:** 5.2.RC2
**Created:** Wed Mar 15, 2017 10:03 AM UTC by Neelakanta Reddy
**Last Updated:** Wed Mar 15, 2017 10:03 AM UTC
**Owner:** Neelakanta Reddy


update the PR document wit 5.2 Enancements

smf: add support for asynchronous detection of failed AMF entities [#2145]


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2212 smf: avoid unpredictable timeout for adminoperations

[Neelakanta Reddy]

- **Milestone**: 5.2.RC2 --> future



---

** [tickets:#2212] smf: avoid unpredictable timeout for adminoperations**

**Status:** accepted
**Milestone:** future
**Created:** Thu Dec 01, 2016 05:06 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Dec 01, 2016 05:06 AM UTC
**Owner:** Neelakanta Reddy


SmfImmUtils AdminOperation can be changed to avoid unpredictable timeout 
similar to adminoperation in nodegroup.

call the nodegroup adminoperation using SmfImmUtils




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2382 imm: reducing log level for ccb-committed messages

[Neelakanta Reddy]

- **status**: review --> wontfix
- **Comment**:

The fix for the problem wil be a part of  Enhancement #2306



---

** [tickets:#2382] imm: reducing log level for ccb-committed messages**

**Status:** wontfix
**Milestone:** 5.0.2
**Created:** Thu Mar 16, 2017 09:26 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Mar 16, 2017 10:30 AM UTC
**Owner:** Neelakanta Reddy


 if(i != sOwnerVector.end()) {
LOG_NO("Ccb %u COMMITTED (%s)", ccb->mId, 
(*i)->mAdminOwnerName.c_str());
} else {
LOG_NO("Ccb %u COMMITTED (%s)", ccb->mId, "");
}

Reduce the LOG_NO to TRACE


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2386 imm: decrement the pending reply when error is other than SA_AIS_OK when newCcbId is called

[Neelakanta Reddy]

- **summary**: imm: decrement the pending reply when error is other than 
SA_AIS_OK in finalizeCcb --> imm: decrement the pending reply when error is 
other than SA_AIS_OK when newCcbId is called



---

** [tickets:#2386] imm: decrement the pending reply when error is other than 
SA_AIS_OK when newCcbId is called**

**Status:** accepted
**Milestone:** 5.0.2
**Created:** Fri Mar 17, 2017 09:46 AM UTC by Neelakanta Reddy
**Last Updated:** Fri Mar 17, 2017 09:54 AM UTC
**Owner:** Neelakanta Reddy


After Ccb operation returned SA_AIS_ERR_FAILED_OPERATION, Ccbfinalize returned 
TRY_AGAIN due to "Too many pending incoming fevs messages (> 16)" .
In the imma_finalizeCcb, if the imma_newCcbId returns error other than 
SA_AIS_OK, imma_proc_decrement_pending_reply is not called.

solution is to call imma_proc_decrement_pending_reply when error is not 
SA_AIS_OK

logs:
IMMA
Mar 10 13:00:10.428430 imma [26655:imma_om_api.c:2907] TR objectDelete send 
RETURNED:1
Mar 10 13:00:10.428448 imma [26655:imma_om_api.c:3001] TR objectDelete really 
RETURNING:21
Mar 10 13:00:10.428456 imma [26655:imma_om_api.c:3002] << 
ccb_object_delete_common
Mar 10 13:00:10.428485 imma [26655:imma_om_api.c:9384] >> 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428496 imma [26655:imma_om_api.c:9391] >> 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428503 imma [26655:imma_om_api.c:9452] << 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428651 imma [26655:imma_om_api.c:8838] >> imma_finalizeCcb
Mar 10 13:00:10.428662 imma [26655:imma_om_api.c:8860] T1 CCb node found for 
ccbhandle 14aa837f7c79cc07 ccbid:4158
Mar 10 13:00:10.428670 imma [26655:imma_om_api.c:8929] TR Ccb is active when 
finalizing
Mar 10 13:00:10.428774 imma [26655:imma_om_api.c:5777] >> accessor_get_common
Mar 10 13:00:10.429358 imma [26655:imma_om_api.c:8956] TR CcbFinalize returned 6
Mar 10 13:00:10.429369 imma [26655:imma_om_api.c:1198] >> imma_newCcbId
Mar 10 13:00:10.429373 imma [26655:imma_om_api.c:1199] TR imma_newCcbId:create 
new ccb id with admoId:103603
Mar 10 13:00:10.429377 imma [26655:imma_om_api.c:1232] TR Sending request for 
new ccbid with admin OwnerId:103603
Mar 10 13:00:10.429684 imma [26655:imma_om_api.c:6120] << accessor_get_common
Mar 10 13:00:10.430233 imma [26655:imma_om_api.c:5777] >> accessor_get_common
Mar 10 13:00:10.430653 imma [26655:imma_om_api.c:1302] << imma_newCcbId
Mar 10 13:00:10.430663 imma [26655:imma_om_api.c:9070] << imma_finalizeCcb

IMMND:

Mar 10 13:00:10.430608 osafimmnd [8927:immsv_evt.c:5473] T8 Received: 
IMMND_EVT_A2ND_CCBINIT (15) from 2010f
Mar 10 13:00:10.430612 osafimmnd [8927:immnd_evt.c:2641] >> 
immnd_evt_proc_ccb_init
Mar 10 13:00:10.430615 osafimmnd [8927:immnd_evt.c:2666] T2 ERR_TRY_AGAIN: Too 
many pending incoming fevs messages (> 16) rejecting ccb_init request
Mar 10 13:00:10.430619 osafimmnd [8927:immnd_evt.c:2722] T2 SENDRSP FAIL 6
Mar 10 13:00:10.430627 osafimmnd [8927:immnd_evt.c:2725] << 
immnd_evt_proc_ccb_init



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2386 imm: decrement the pending reply when error is other than SA_AIS_OK in finalizeCcb

[Neelakanta Reddy]

- **summary**: imm:  --> imm: decrement the pending reply when error is other 
than SA_AIS_OK in finalizeCcb
- **Part**: nd --> lib



---

** [tickets:#2386] imm: decrement the pending reply when error is other than 
SA_AIS_OK in finalizeCcb**

**Status:** accepted
**Milestone:** 5.0.2
**Created:** Fri Mar 17, 2017 09:46 AM UTC by Neelakanta Reddy
**Last Updated:** Fri Mar 17, 2017 09:46 AM UTC
**Owner:** Neelakanta Reddy


After Ccb operation returned SA_AIS_ERR_FAILED_OPERATION, Ccbfinalize returned 
TRY_AGAIN due to "Too many pending incoming fevs messages (> 16)" .
In the imma_finalizeCcb, if the imma_newCcbId returns error other than 
SA_AIS_OK, imma_proc_decrement_pending_reply is not called.

solution is to call imma_proc_decrement_pending_reply when error is not 
SA_AIS_OK

logs:
IMMA
Mar 10 13:00:10.428430 imma [26655:imma_om_api.c:2907] TR objectDelete send 
RETURNED:1
Mar 10 13:00:10.428448 imma [26655:imma_om_api.c:3001] TR objectDelete really 
RETURNING:21
Mar 10 13:00:10.428456 imma [26655:imma_om_api.c:3002] << 
ccb_object_delete_common
Mar 10 13:00:10.428485 imma [26655:imma_om_api.c:9384] >> 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428496 imma [26655:imma_om_api.c:9391] >> 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428503 imma [26655:imma_om_api.c:9452] << 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428651 imma [26655:imma_om_api.c:8838] >> imma_finalizeCcb
Mar 10 13:00:10.428662 imma [26655:imma_om_api.c:8860] T1 CCb node found for 
ccbhandle 14aa837f7c79cc07 ccbid:4158
Mar 10 13:00:10.428670 imma [26655:imma_om_api.c:8929] TR Ccb is active when 
finalizing
Mar 10 13:00:10.428774 imma [26655:imma_om_api.c:5777] >> accessor_get_common
Mar 10 13:00:10.429358 imma [26655:imma_om_api.c:8956] TR CcbFinalize returned 6
Mar 10 13:00:10.429369 imma [26655:imma_om_api.c:1198] >> imma_newCcbId
Mar 10 13:00:10.429373 imma [26655:imma_om_api.c:1199] TR imma_newCcbId:create 
new ccb id with admoId:103603
Mar 10 13:00:10.429377 imma [26655:imma_om_api.c:1232] TR Sending request for 
new ccbid with admin OwnerId:103603
Mar 10 13:00:10.429684 imma [26655:imma_om_api.c:6120] << accessor_get_common
Mar 10 13:00:10.430233 imma [26655:imma_om_api.c:5777] >> accessor_get_common
Mar 10 13:00:10.430653 imma [26655:imma_om_api.c:1302] << imma_newCcbId
Mar 10 13:00:10.430663 imma [26655:imma_om_api.c:9070] << imma_finalizeCcb

IMMND:

Mar 10 13:00:10.430608 osafimmnd [8927:immsv_evt.c:5473] T8 Received: 
IMMND_EVT_A2ND_CCBINIT (15) from 2010f
Mar 10 13:00:10.430612 osafimmnd [8927:immnd_evt.c:2641] >> 
immnd_evt_proc_ccb_init
Mar 10 13:00:10.430615 osafimmnd [8927:immnd_evt.c:2666] T2 ERR_TRY_AGAIN: Too 
many pending incoming fevs messages (> 16) rejecting ccb_init request
Mar 10 13:00:10.430619 osafimmnd [8927:immnd_evt.c:2722] T2 SENDRSP FAIL 6
Mar 10 13:00:10.430627 osafimmnd [8927:immnd_evt.c:2725] << 
immnd_evt_proc_ccb_init



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2386 imm:

[Neelakanta Reddy]

---

** [tickets:#2386] imm: **

**Status:** accepted
**Milestone:** 5.0.2
**Created:** Fri Mar 17, 2017 09:46 AM UTC by Neelakanta Reddy
**Last Updated:** Fri Mar 17, 2017 09:46 AM UTC
**Owner:** Neelakanta Reddy


After Ccb operation returned SA_AIS_ERR_FAILED_OPERATION, Ccbfinalize returned 
TRY_AGAIN due to "Too many pending incoming fevs messages (> 16)" .
In the imma_finalizeCcb, if the imma_newCcbId returns error other than 
SA_AIS_OK, imma_proc_decrement_pending_reply is not called.

solution is to call imma_proc_decrement_pending_reply when error is not 
SA_AIS_OK

logs:
IMMA
Mar 10 13:00:10.428430 imma [26655:imma_om_api.c:2907] TR objectDelete send 
RETURNED:1
Mar 10 13:00:10.428448 imma [26655:imma_om_api.c:3001] TR objectDelete really 
RETURNING:21
Mar 10 13:00:10.428456 imma [26655:imma_om_api.c:3002] << 
ccb_object_delete_common
Mar 10 13:00:10.428485 imma [26655:imma_om_api.c:9384] >> 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428496 imma [26655:imma_om_api.c:9391] >> 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428503 imma [26655:imma_om_api.c:9452] << 
saImmOmCcbGetErrorStrings
Mar 10 13:00:10.428651 imma [26655:imma_om_api.c:8838] >> imma_finalizeCcb
Mar 10 13:00:10.428662 imma [26655:imma_om_api.c:8860] T1 CCb node found for 
ccbhandle 14aa837f7c79cc07 ccbid:4158
Mar 10 13:00:10.428670 imma [26655:imma_om_api.c:8929] TR Ccb is active when 
finalizing
Mar 10 13:00:10.428774 imma [26655:imma_om_api.c:5777] >> accessor_get_common
Mar 10 13:00:10.429358 imma [26655:imma_om_api.c:8956] TR CcbFinalize returned 6
Mar 10 13:00:10.429369 imma [26655:imma_om_api.c:1198] >> imma_newCcbId
Mar 10 13:00:10.429373 imma [26655:imma_om_api.c:1199] TR imma_newCcbId:create 
new ccb id with admoId:103603
Mar 10 13:00:10.429377 imma [26655:imma_om_api.c:1232] TR Sending request for 
new ccbid with admin OwnerId:103603
Mar 10 13:00:10.429684 imma [26655:imma_om_api.c:6120] << accessor_get_common
Mar 10 13:00:10.430233 imma [26655:imma_om_api.c:5777] >> accessor_get_common
Mar 10 13:00:10.430653 imma [26655:imma_om_api.c:1302] << imma_newCcbId
Mar 10 13:00:10.430663 imma [26655:imma_om_api.c:9070] << imma_finalizeCcb

IMMND:

Mar 10 13:00:10.430608 osafimmnd [8927:immsv_evt.c:5473] T8 Received: 
IMMND_EVT_A2ND_CCBINIT (15) from 2010f
Mar 10 13:00:10.430612 osafimmnd [8927:immnd_evt.c:2641] >> 
immnd_evt_proc_ccb_init
Mar 10 13:00:10.430615 osafimmnd [8927:immnd_evt.c:2666] T2 ERR_TRY_AGAIN: Too 
many pending incoming fevs messages (> 16) rejecting ccb_init request
Mar 10 13:00:10.430619 osafimmnd [8927:immnd_evt.c:2722] T2 SENDRSP FAIL 6
Mar 10 13:00:10.430627 osafimmnd [8927:immnd_evt.c:2725] << 
immnd_evt_proc_ccb_init



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2378 imm: PR document updation for 5.2 Release

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2378] imm: PR document updation for 5.2 Release**

**Status:** review
**Milestone:** 5.2.RC2
**Created:** Wed Mar 15, 2017 05:36 AM UTC by Neelakanta Reddy
**Last Updated:** Wed Mar 15, 2017 05:36 AM UTC
**Owner:** Neelakanta Reddy


Update the IMM PR document, about integration of IMM with CLM


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2382 imm: reducing log level for ccb-committed messages

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2382] imm: reducing log level for ccb-committed messages**

**Status:** review
**Milestone:** 5.0.2
**Created:** Thu Mar 16, 2017 09:26 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Mar 16, 2017 09:32 AM UTC
**Owner:** Neelakanta Reddy


 if(i != sOwnerVector.end()) {
LOG_NO("Ccb %u COMMITTED (%s)", ccb->mId, 
(*i)->mAdminOwnerName.c_str());
} else {
LOG_NO("Ccb %u COMMITTED (%s)", ccb->mId, "");
}

Reduce the LOG_NO to TRACE


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2382 imm: reducing log level for ccb-committed messages

[Neelakanta Reddy]

- **Milestone**: 5.2.RC2 --> 5.0.2



---

** [tickets:#2382] imm: reducing log level for ccb-committed messages**

**Status:** accepted
**Milestone:** 5.0.2
**Created:** Thu Mar 16, 2017 09:26 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Mar 16, 2017 09:26 AM UTC
**Owner:** Neelakanta Reddy


 if(i != sOwnerVector.end()) {
LOG_NO("Ccb %u COMMITTED (%s)", ccb->mId, 
(*i)->mAdminOwnerName.c_str());
} else {
LOG_NO("Ccb %u COMMITTED (%s)", ccb->mId, "");
}

Reduce the LOG_NO to TRACE


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2382 imm: reducing log level for ccb-committed messages

[Neelakanta Reddy]

---

** [tickets:#2382] imm: reducing log level for ccb-committed messages**

**Status:** accepted
**Milestone:** 5.2.RC2
**Created:** Thu Mar 16, 2017 09:26 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Mar 16, 2017 09:26 AM UTC
**Owner:** Neelakanta Reddy


 if(i != sOwnerVector.end()) {
LOG_NO("Ccb %u COMMITTED (%s)", ccb->mId, 
(*i)->mAdminOwnerName.c_str());
} else {
LOG_NO("Ccb %u COMMITTED (%s)", ccb->mId, "");
}

Reduce the LOG_NO to TRACE


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2379 smf:PR documentation for 5.2 release

[Neelakanta Reddy]

---

** [tickets:#2379] smf:PR documentation for 5.2 release**

**Status:** accepted
**Milestone:** 5.2.RC2
**Created:** Wed Mar 15, 2017 10:03 AM UTC by Neelakanta Reddy
**Last Updated:** Wed Mar 15, 2017 10:03 AM UTC
**Owner:** Neelakanta Reddy


update the PR document wit 5.2 Enancements

smf: add support for asynchronous detection of failed AMF entities [#2145]


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2340 immnd : restarts if larg db

[Neelakanta Reddy]

- **status**: assigned --> wontfix
- **Comment**:

The Problem reported in the ticket may be observed when the disk is full. IMM 
is tested for 300k objects.
When the test is performed in my setup, the IMMND is not restarted for 500k 
(when immomtest 3 10 is performed.) But the IMMND is restarted for the same 
test, when the traces are enabled and the disk is full .

please share the bt .



---

** [tickets:#2340] immnd : restarts if larg db**

**Status:** wontfix
**Milestone:** 5.2.RC2
**Created:** Fri Mar 03, 2017 06:18 AM UTC by A V Mahesh (AVM)
**Last Updated:** Tue Mar 14, 2017 06:36 AM UTC
**Owner:** Neelakanta Reddy


1) Configure opensaf with  --enable-ntf-imcn

/# ./bootstrap.sh ;./configure --enable-imm-pbe --enable-tests --enable-tipc 
--enable-ntf-imcn; make rpm 

2) Have a larg XML database of objects ( 70 k objects)

3) Run 

/# /usr/bin/immomtest 3 10 

error: in src/imm/apitest/management/test_saImmOmSearchInitialize_2.c at 171: 
SA_AIS_ERR_TIMEOUT (5), expected SA_AIS_OK (1) - exiting


4) Immnd restarts 

=

Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO ERR_INVALID_PARAM: Problem with new 
class 'saImmOmClassCreate_2_10'
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO ERR_INVALID_PARAM: Attribute 
'SaImmAttrImplementerName' is neither SA_IMM_ATTR_CONFIG nor SA_IMM_ATTR_RUNTIME
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO ERR_INVALID_PARAM: Attribute 
'SaImmAttrAdminOwnerName' is neither SA_IMM_ATTR_CONFIG nor SA_IMM_ATTR_RUNTIME
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO ERR_INVALID_PARAM: Attribute 
'SaImmAttrClassName' is neither SA_IMM_ATTR_CONFIG nor SA_IMM_ATTR_RUNTIME
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO ERR_INVALID_PARAM: Problem with new 
class 'saImmOmClassCreate_2_11'
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO opensafImmNostdFlags changed to: 0x1f6
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO opensafImmNostdFlags changed to: 0x1f7
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Class 
'saImmOmClassCreate_SchemaChange_2_17' exist - check implied schema upgrade
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Allowed upgrade, attribute 
saImmOmClassCreate_SchemaChange_2_17:attr adds flag SA_IMM_ATTR_STRONG_DEFAULT
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Schema change for class 
saImmOmClassCreate_SchemaChange_2_17 ACCEPTED. Adding 0 and changing 1 
attribute defs
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO No instances to migrate - schema 
change could have been avoided
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Schema change completed for class 
saImmOmClassCreate_SchemaChange_2_17
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO opensafImmNostdFlags changed to: 0x1f6
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO opensafImmNostdFlags changed to: 0x1f7
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Class 
'saImmOmClassCreate_SchemaChange_2_18' exist - check implied schema upgrade
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Allowed upgrade, attribute 
saImmOmClassCreate_SchemaChange_2_18:attr removes flag 
SA_IMM_ATTR_STRONG_DEFAULT
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Schema change for class 
saImmOmClassCreate_SchemaChange_2_18 ACCEPTED. Adding 0 and changing 1 
attribute defs
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO No instances to migrate - schema 
change could have been avoided
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Schema change completed for class 
saImmOmClassCreate_SchemaChange_2_18
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO opensafImmNostdFlags changed to: 0x1f6
Mar  3 11:40:57 SC-1 osafimmd[32335]: NO MDS event from svc_id 25 (change:4, 
dest:564114323931152)
Mar  3 11:40:57 SC-1 osafsmfd[32430]: WA DispatchOiCallback: saImmOiDispatch() 
Fail 'SA_AIS_ERR_BAD_HANDLE (9)'
Mar  3 11:40:57 SC-1 osafntfimcnd[32381]: NO saImmOiDispatch() Fail 
SA_AIS_ERR_BAD_HANDLE (9)
Mar  3 11:40:58 SC-1 osafamfnd[32412]: NO 
'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' component restart probation timer 
started (timeout: 600 ns)
Mar  3 11:40:58 SC-1 osafamfnd[32412]: NO Restarting a component of 
'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1)
Mar  3 11:40:58 SC-1 osafamfnd[32412]: NO 
'safComp=IMMND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' 
: Recovery is 'componentRestart'
Mar  3 11:40:58 SC-1 osafimmd[32335]: WA IMMND coordinator at 2010f apparently 
crashed => electing new coord
Mar  3 11:40:58 SC-1 osafimmd[32335]: NO New coord elected, resides at 2020f




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sd

[tickets] [opensaf:tickets] #2378 imm: PR document updation for 5.2 Release

[Neelakanta Reddy]

---

** [tickets:#2378] imm: PR document updation for 5.2 Release**

**Status:** accepted
**Milestone:** 5.2.RC2
**Created:** Wed Mar 15, 2017 05:36 AM UTC by Neelakanta Reddy
**Last Updated:** Wed Mar 15, 2017 05:36 AM UTC
**Owner:** Neelakanta Reddy


Update the IMM PR document, about integration of IMM with CLM


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2364 SMF: Payloads went for continuous reboot while upgraing an NWAY Active application

[Neelakanta Reddy]

- **status**: unassigned --> assigned
- **assigned_to**: Neelakanta Reddy



---

** [tickets:#2364] SMF: Payloads went for continuous reboot while upgraing an 
NWAY Active application**

**Status:** assigned
**Milestone:** 5.2.RC1
**Created:** Sat Mar 11, 2017 11:52 AM UTC by Chani Srivastava
**Last Updated:** Sat Mar 11, 2017 11:52 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[NWAYACT.sh](https://sourceforge.net/p/opensaf/tickets/2364/attachment/NWAYACT.sh)
 (20.9 kB; application/octet-stream)
- 
[campaign18.xml](https://sourceforge.net/p/opensaf/tickets/2364/attachment/campaign18.xml)
 (26.2 kB; text/xml)
- 
[import_sysmodel.xml](https://sourceforge.net/p/opensaf/tickets/2364/attachment/import_sysmodel.xml)
 (26.4 kB; text/xml)


**Environment details**

OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads / no PBE )

**Steps followed & Observed behaviour**
1. Import attached xml
2. Bring up the attached NWAYACT.sh application
3. Execute attached campaign18.xml to upgrade the application

Campaign.xml is modeled to : Add more SIs and CSIs ( i.e work ) and assign it 
to SUs which can handle more work and also assign to spare SUs

Campaign.xml is successfully executed but after that both the payloads are 
continuously rebooted.


**Mar 11 17:04:45 NewSC1 osafamfd[3331]: NO Ordering reboot of 
'safAmfNode=PL-4,safAmfCluster=myAmfCluster' as node fail/switch-over repair 
action**
Mar 11 17:04:45 NewSC1 osaflogd[3295]: CR MDTM: undelivered message condition 
ancillary data: TIPC_RETDATA
|
|
Mar 11 17:04:45 NewSC1 osaflogd[3295]: NO Failed (2) to send of WRITE ack to: 
2030fac102024
Mar 11 17:04:45 NewSC1 osaflogd[3295]: NO Failed (2) to send of WRITE ack to: 
2030fac100022
**Mar 11 17:04:45 NewSC1 osafamfd[3331]: NO Ordering reboot of 
'safAmfNode=PL-3,safAmfCluster=myAmfCluster' as node fail/switch-over repair 
action**
Mar 11 17:04:45 NewSC1 osafamfd[3331]: NO Assigning due to dep 
'safSi=NWAYACTSI4,safApp=NWAYACTAPP'
Mar 11 17:04:45 NewSC1 osafamfd[3331]: NO Assigning due to dep 
'safSi=NWAYACTSI4,safApp=NWAYACTAPP'
Mar 11 17:04:46 NewSC1 osafamfd[3331]: NO 'safSi=NWAYACTSI7,safApp=NWAYACTAPP' 
could not be assigned to any SU
Mar 11 17:04:46 NewSC1 osafamfd[3331]: NO 'safSi=NWAYACTSI8,safApp=NWAYACTAPP' 
could not be assigned to any SU
Mar 11 17:04:46 NewSC1 osafamfd[3331]: NO 'safSi=NWAYACTSI9,safApp=NWAYACTAPP' 
could not be assigned to any SU
Mar 11 17:04:46 NewSC1 osafamfd[3331]: NO 'safSi=NWAYACTSI10,safApp=NWAYACTAPP' 
could not be assigned to any SU
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO PROC: Procedure wrapup actions 
completed
**Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO PROC: Upgrade procedure completed 
safSmfProc=AddSIAndCSIs**
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: Procedure 
safSmfProc=AddSIAndCSIs returned COMPLETED
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: All procedures executed, start 
wrapup
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO IMM PBE was not turned off at 
campaign start and was not turned on at PBE restore.
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: Start campaign complete actions 
(0)
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: Campaign complete actions 
completed
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: Start wait to complete timer 
(not implemented yet)
**Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: Upgrade campaign completed 
safSmfCampaign=campaign_18**


Note: syslogs and immnd/immd/smfnd/smfd/amfd traces are huge in size so will be 
shared offline when asked


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2340 immnd : restarts if larg db

[Neelakanta Reddy]

- **status**: unassigned --> assigned
- **assigned_to**: Neelakanta Reddy



---

** [tickets:#2340] immnd : restarts if larg db**

**Status:** assigned
**Milestone:** 5.2.RC1
**Created:** Fri Mar 03, 2017 06:18 AM UTC by A V Mahesh (AVM)
**Last Updated:** Fri Mar 03, 2017 06:18 AM UTC
**Owner:** Neelakanta Reddy


1) Configure opensaf with  --enable-ntf-imcn

/# ./bootstrap.sh ;./configure --enable-imm-pbe --enable-tests --enable-tipc 
--enable-ntf-imcn; make rpm 

2) Have a larg XML database of objects ( 70 k objects)

3) Run 

/# /usr/bin/immomtest 3 10 

error: in src/imm/apitest/management/test_saImmOmSearchInitialize_2.c at 171: 
SA_AIS_ERR_TIMEOUT (5), expected SA_AIS_OK (1) - exiting


4) Immnd restarts 

=

Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO ERR_INVALID_PARAM: Problem with new 
class 'saImmOmClassCreate_2_10'
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO ERR_INVALID_PARAM: Attribute 
'SaImmAttrImplementerName' is neither SA_IMM_ATTR_CONFIG nor SA_IMM_ATTR_RUNTIME
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO ERR_INVALID_PARAM: Attribute 
'SaImmAttrAdminOwnerName' is neither SA_IMM_ATTR_CONFIG nor SA_IMM_ATTR_RUNTIME
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO ERR_INVALID_PARAM: Attribute 
'SaImmAttrClassName' is neither SA_IMM_ATTR_CONFIG nor SA_IMM_ATTR_RUNTIME
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO ERR_INVALID_PARAM: Problem with new 
class 'saImmOmClassCreate_2_11'
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO opensafImmNostdFlags changed to: 0x1f6
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO opensafImmNostdFlags changed to: 0x1f7
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Class 
'saImmOmClassCreate_SchemaChange_2_17' exist - check implied schema upgrade
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Allowed upgrade, attribute 
saImmOmClassCreate_SchemaChange_2_17:attr adds flag SA_IMM_ATTR_STRONG_DEFAULT
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Schema change for class 
saImmOmClassCreate_SchemaChange_2_17 ACCEPTED. Adding 0 and changing 1 
attribute defs
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO No instances to migrate - schema 
change could have been avoided
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Schema change completed for class 
saImmOmClassCreate_SchemaChange_2_17
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO opensafImmNostdFlags changed to: 0x1f6
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO opensafImmNostdFlags changed to: 0x1f7
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Class 
'saImmOmClassCreate_SchemaChange_2_18' exist - check implied schema upgrade
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Allowed upgrade, attribute 
saImmOmClassCreate_SchemaChange_2_18:attr removes flag 
SA_IMM_ATTR_STRONG_DEFAULT
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Schema change for class 
saImmOmClassCreate_SchemaChange_2_18 ACCEPTED. Adding 0 and changing 1 
attribute defs
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO No instances to migrate - schema 
change could have been avoided
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO Schema change completed for class 
saImmOmClassCreate_SchemaChange_2_18
Mar  3 11:40:27 SC-1 osafimmnd[32348]: NO opensafImmNostdFlags changed to: 0x1f6
Mar  3 11:40:57 SC-1 osafimmd[32335]: NO MDS event from svc_id 25 (change:4, 
dest:564114323931152)
Mar  3 11:40:57 SC-1 osafsmfd[32430]: WA DispatchOiCallback: saImmOiDispatch() 
Fail 'SA_AIS_ERR_BAD_HANDLE (9)'
Mar  3 11:40:57 SC-1 osafntfimcnd[32381]: NO saImmOiDispatch() Fail 
SA_AIS_ERR_BAD_HANDLE (9)
Mar  3 11:40:58 SC-1 osafamfnd[32412]: NO 
'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' component restart probation timer 
started (timeout: 600 ns)
Mar  3 11:40:58 SC-1 osafamfnd[32412]: NO Restarting a component of 
'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1)
Mar  3 11:40:58 SC-1 osafamfnd[32412]: NO 
'safComp=IMMND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' 
: Recovery is 'componentRestart'
Mar  3 11:40:58 SC-1 osafimmd[32335]: WA IMMND coordinator at 2010f apparently 
crashed => electing new coord
Mar  3 11:40:58 SC-1 osafimmd[32335]: NO New coord elected, resides at 2020f




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2364 SMF: Payloads went for continuous reboot while upgraing an NWAY Active application

[Neelakanta Reddy]

- **status**: assigned --> invalid
- **Comment**:

when the campaign is run the above  "Ordering reboot " is not  observed.
In syslog of payloads segfaults are observed:
kernel: [870763.985178] sysAppComp[27555]: segfault at 0 ip 0040e390 sp 
7fffbd71cf90 error 4 in sysAppComp[40+13000]

The AMF Order node reboot may happen when the component is continuesly 
restarted and escalated to node failover. Try to run on newly bring up cluster.



---

** [tickets:#2364] SMF: Payloads went for continuous reboot while upgraing an 
NWAY Active application**

**Status:** invalid
**Milestone:** 5.2.RC1
**Created:** Sat Mar 11, 2017 11:52 AM UTC by Chani Srivastava
**Last Updated:** Tue Mar 14, 2017 06:24 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[NWAYACT.sh](https://sourceforge.net/p/opensaf/tickets/2364/attachment/NWAYACT.sh)
 (20.9 kB; application/octet-stream)
- 
[campaign18.xml](https://sourceforge.net/p/opensaf/tickets/2364/attachment/campaign18.xml)
 (26.2 kB; text/xml)
- 
[import_sysmodel.xml](https://sourceforge.net/p/opensaf/tickets/2364/attachment/import_sysmodel.xml)
 (26.4 kB; text/xml)


**Environment details**

OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads / no PBE )

**Steps followed & Observed behaviour**
1. Import attached xml
2. Bring up the attached NWAYACT.sh application
3. Execute attached campaign18.xml to upgrade the application

Campaign.xml is modeled to : Add more SIs and CSIs ( i.e work ) and assign it 
to SUs which can handle more work and also assign to spare SUs

Campaign.xml is successfully executed but after that both the payloads are 
continuously rebooted.


**Mar 11 17:04:45 NewSC1 osafamfd[3331]: NO Ordering reboot of 
'safAmfNode=PL-4,safAmfCluster=myAmfCluster' as node fail/switch-over repair 
action**
Mar 11 17:04:45 NewSC1 osaflogd[3295]: CR MDTM: undelivered message condition 
ancillary data: TIPC_RETDATA
|
|
Mar 11 17:04:45 NewSC1 osaflogd[3295]: NO Failed (2) to send of WRITE ack to: 
2030fac102024
Mar 11 17:04:45 NewSC1 osaflogd[3295]: NO Failed (2) to send of WRITE ack to: 
2030fac100022
**Mar 11 17:04:45 NewSC1 osafamfd[3331]: NO Ordering reboot of 
'safAmfNode=PL-3,safAmfCluster=myAmfCluster' as node fail/switch-over repair 
action**
Mar 11 17:04:45 NewSC1 osafamfd[3331]: NO Assigning due to dep 
'safSi=NWAYACTSI4,safApp=NWAYACTAPP'
Mar 11 17:04:45 NewSC1 osafamfd[3331]: NO Assigning due to dep 
'safSi=NWAYACTSI4,safApp=NWAYACTAPP'
Mar 11 17:04:46 NewSC1 osafamfd[3331]: NO 'safSi=NWAYACTSI7,safApp=NWAYACTAPP' 
could not be assigned to any SU
Mar 11 17:04:46 NewSC1 osafamfd[3331]: NO 'safSi=NWAYACTSI8,safApp=NWAYACTAPP' 
could not be assigned to any SU
Mar 11 17:04:46 NewSC1 osafamfd[3331]: NO 'safSi=NWAYACTSI9,safApp=NWAYACTAPP' 
could not be assigned to any SU
Mar 11 17:04:46 NewSC1 osafamfd[3331]: NO 'safSi=NWAYACTSI10,safApp=NWAYACTAPP' 
could not be assigned to any SU
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO PROC: Procedure wrapup actions 
completed
**Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO PROC: Upgrade procedure completed 
safSmfProc=AddSIAndCSIs**
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: Procedure 
safSmfProc=AddSIAndCSIs returned COMPLETED
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: All procedures executed, start 
wrapup
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO IMM PBE was not turned off at 
campaign start and was not turned on at PBE restore.
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: Start campaign complete actions 
(0)
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: Campaign complete actions 
completed
Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: Start wait to complete timer 
(not implemented yet)
**Mar 11 17:04:46 NewSC1 osafsmfd[3366]: NO CAMP: Upgrade campaign completed 
safSmfCampaign=campaign_18**


Note: syslogs and immnd/immd/smfnd/smfd/amfd traces are huge in size so will be 
shared offline when asked


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2343 IMM: immnd failed to spawn while starting opensaf on controller

[Neelakanta Reddy]

The problem looks to be similar to #2349. check if there is any link loass of 
SC1 from other nodes.
Share the following information of all the nodes in the cluster : syslog, immd 
and immnd traces.


---

** [tickets:#2343] IMM: immnd failed to spawn while starting opensaf on 
controller**

**Status:** assigned
**Milestone:** 5.2.RC1
**Created:** Fri Mar 03, 2017 11:46 AM UTC by Chani Srivastava
**Last Updated:** Mon Mar 13, 2017 10:02 AM UTC
**Owner:** Neelakanta Reddy


**Environment details**

OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads with 1PBE enabled )

Summary

immnd failed to spawn a number of times while starting openSaf on controller.
This issue is observed in various situations

1. While resetting cluster and starting OpenSaf again
2. While invoking continuous failovers.
3. While stoping and starting openSaf on standby controller.



Mar  3 15:45:49 OSAF-SC1 opensafd: Starting OpenSAF Services(5.2.FC - ) (Using 
TIPC)
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828240] TIPC: Activated (version 2.0.0)
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828391] NET: Registered protocol family 
30
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828393] TIPC: Started in single node 
mode
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.834836] TIPC: Started in network mode
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.834839] TIPC: Own node address <1.1.1>, 
network identity 4141
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.838982] TIPC: Enabled bearer 
, discovery domain <1.1.0>, priority 10
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.840611] TIPC: Established link 
<1.1.1:eth1-1.1.2:eth1> on network plane A
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.840688] TIPC: Established link 
<1.1.1:eth1-1.1.3:eth1> on network plane A
Mar  3 15:45:49 OSAF-SC1 osaftransportd[3854]: mkfifo already exists: 
/var/lib/opensaf/osaftransportd.fifo File exists
Mar  3 15:45:49 OSAF-SC1 osaftransportd[3854]: Started
Mar  3 15:45:49 OSAF-SC1 opensafd[3830]: NO Monitoring of TRANSPORT started
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: mkfifo already exists: 
/var/lib/opensaf/osafclmna.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: Started
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of CLMNA started
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: NO 
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Mar  3 15:45:50 OSAF-SC1 osafrded[3870]: mkfifo already exists: 
/var/lib/opensaf/osafrded.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafrded[3870]: Started
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: mkfifo already exists: 
/var/lib/opensaf/osaffmd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: Started
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: NO Remote fencing is disabled
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of HLFM started
Mar  3 15:45:50 OSAF-SC1 osafimmd[3889]: mkfifo already exists: 
/var/lib/opensaf/osafimmd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafimmd[3889]: Started
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of IMMD started
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: mkfifo already exists: 
/var/lib/opensaf/osafimmnd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: Started
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO Persistent Back-End capability 
configured, Pbe file:imm.db (suffix may get added)
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO IMMD service is UP ... 
ScAbsenseAllowed?:0 introduced?:0
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: IMM_SERVER_ANONYMOUS 
--> IMM_SERVER_CLUSTER_WAITING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_ISOLATED
Mar  3 15:45:51 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Mar  3 15:45:51 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: WA Global ABORT SYNC received for 
epoch 508
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: WA SERVER STATE: 
IMM_SERVER_SYNC_CLIENT --> IMM_SERVER_LOADING_PENDING (sync aborted)
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_UNKNOW 2827
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: NO Abort sync: Discarding synced 
objects
Mar  3 15:51:04 OSAF-SC1 osafimmnd[3900]: NO Abort sync: Discarding synced 
classes
Mar  3 15:51:04 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar  3 15:51:05 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_ISOLATED
Mar  3 15:51:06 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Mar  3 15:51:06 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar  3 15:51:41 OSAF-SC1 osafimmnd[3900]: NO Implement

[tickets] [opensaf:tickets] #2343 IMM: immnd failed to spawn while starting opensaf on controller

[Neelakanta Reddy]

- **status**: unassigned --> assigned
- **assigned_to**: Neelakanta Reddy



---

** [tickets:#2343] IMM: immnd failed to spawn while starting opensaf on 
controller**

**Status:** assigned
**Milestone:** 5.2.RC1
**Created:** Fri Mar 03, 2017 11:46 AM UTC by Chani Srivastava
**Last Updated:** Mon Mar 06, 2017 12:12 PM UTC
**Owner:** Neelakanta Reddy


**Environment details**

OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads with 1PBE enabled )

Summary

immnd failed to spawn a number of times while starting openSaf on controller.
This issue is observed in various situations

1. While resetting cluster and starting OpenSaf again
2. While invoking continuous failovers.
3. While stoping and starting openSaf on standby controller.



Mar  3 15:45:49 OSAF-SC1 opensafd: Starting OpenSAF Services(5.2.FC - ) (Using 
TIPC)
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828240] TIPC: Activated (version 2.0.0)
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828391] NET: Registered protocol family 
30
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828393] TIPC: Started in single node 
mode
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.834836] TIPC: Started in network mode
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.834839] TIPC: Own node address <1.1.1>, 
network identity 4141
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.838982] TIPC: Enabled bearer 
, discovery domain <1.1.0>, priority 10
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.840611] TIPC: Established link 
<1.1.1:eth1-1.1.2:eth1> on network plane A
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.840688] TIPC: Established link 
<1.1.1:eth1-1.1.3:eth1> on network plane A
Mar  3 15:45:49 OSAF-SC1 osaftransportd[3854]: mkfifo already exists: 
/var/lib/opensaf/osaftransportd.fifo File exists
Mar  3 15:45:49 OSAF-SC1 osaftransportd[3854]: Started
Mar  3 15:45:49 OSAF-SC1 opensafd[3830]: NO Monitoring of TRANSPORT started
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: mkfifo already exists: 
/var/lib/opensaf/osafclmna.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: Started
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of CLMNA started
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: NO 
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Mar  3 15:45:50 OSAF-SC1 osafrded[3870]: mkfifo already exists: 
/var/lib/opensaf/osafrded.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafrded[3870]: Started
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: mkfifo already exists: 
/var/lib/opensaf/osaffmd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: Started
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: NO Remote fencing is disabled
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of HLFM started
Mar  3 15:45:50 OSAF-SC1 osafimmd[3889]: mkfifo already exists: 
/var/lib/opensaf/osafimmd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafimmd[3889]: Started
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of IMMD started
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: mkfifo already exists: 
/var/lib/opensaf/osafimmnd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: Started
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO Persistent Back-End capability 
configured, Pbe file:imm.db (suffix may get added)
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO IMMD service is UP ... 
ScAbsenseAllowed?:0 introduced?:0
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: IMM_SERVER_ANONYMOUS 
--> IMM_SERVER_CLUSTER_WAITING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_ISOLATED
Mar  3 15:45:51 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Mar  3 15:45:51 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: WA Global ABORT SYNC received for 
epoch 508
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: WA SERVER STATE: 
IMM_SERVER_SYNC_CLIENT --> IMM_SERVER_LOADING_PENDING (sync aborted)
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_UNKNOW 2827
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: NO Abort sync: Discarding synced 
objects
Mar  3 15:51:04 OSAF-SC1 osafimmnd[3900]: NO Abort sync: Discarding synced 
classes
Mar  3 15:51:04 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar  3 15:51:05 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_ISOLATED
Mar  3 15:51:06 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Mar  3 15:51:06 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar  3 15:51:41 OSAF-SC1 osafimmnd[3900]: NO Implementer connected: 1223 
(RUNTIMEIMPL) <0, 2030f>
Mar  3 15:53:50 OSAF-SC1 opensafd[3830]: ER Timed-out for response from IM

[tickets] [opensaf:tickets] #2349 Immnd faild to load/sync during headless opeartion resulted opensaf failed to start on controller

[Neelakanta Reddy]

- **status**: assigned --> wontfix
- **Comment**:

There is link loss observed, that is the reason IMMND failed in sync.



---

** [tickets:#2349] Immnd faild to load/sync during headless opeartion resulted 
opensaf failed to start on controller**

**Status:** wontfix
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 10:06 AM UTC by Ritu Raj
**Last Updated:** Mon Mar 13, 2017 09:58 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[osafimmnd.tgz](https://sourceforge.net/p/opensaf/tickets/2349/attachment/osafimmnd.tgz)
 (1.0 MB; application/x-compressed-tar)


Environment details
OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
6 nodes setup(3 controller and 3 payload)

#Summary
Immnd faild to load/sync during headless opeartion resulted opensaf failed to 
start on controller

Steps followed & Observed behaviour
1. Invkoed headless 
2. after couple of headless opeartion immnd faild to load on one of the 
controller (SC-1) and later opensaf failed to start on same node.
 
 >> The issue is random
 
syslog--
Mar 10 16:52:40 suseR2-S1 **osafimmnd[2987]: ER Failed to load/sync. **Giving 
up after 51.061144 seconds, restarting..
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Could Not RESPAWN IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Failed   DESC:IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER FAILED TO RESPAWN
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER IMMND - Periodic server job failed
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER Failed, exiting...
Mar 10 16:52:40 suseR2-S1 osafimmd[2934]: NO MDS event from svc_id 25 
(change:4, dest:564118002024465)
Mar 10 16:52:41 suseR2-S1 osafclmna[2904]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osaffmd[2922]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osafimmd[2934]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osafrded[2913]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osaftransportd[2899]: exiting for shutdown
...
Mar 10 16:52:42 suseR2-S1 kernel: [354116.766597] TIPC: Deactivated
Mar 10 16:52:42 suseR2-S1 opensafd: Starting OpenSAF failed


Notes:
1. Immnd traces attched 


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2349 Immnd faild to load/sync during headless opeartion resulted opensaf failed to start on controller

[Neelakanta Reddy]

- **status**: unassigned --> assigned
- **assigned_to**: Neelakanta Reddy



---

** [tickets:#2349] Immnd faild to load/sync during headless opeartion resulted 
opensaf failed to start on controller**

**Status:** assigned
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 10:06 AM UTC by Ritu Raj
**Last Updated:** Thu Mar 09, 2017 02:30 PM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[osafimmnd.tgz](https://sourceforge.net/p/opensaf/tickets/2349/attachment/osafimmnd.tgz)
 (1.0 MB; application/x-compressed-tar)


Environment details
OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
6 nodes setup(3 controller and 3 payload)

#Summary
Immnd faild to load/sync during headless opeartion resulted opensaf failed to 
start on controller

Steps followed & Observed behaviour
1. Invkoed headless 
2. after couple of headless opeartion immnd faild to load on one of the 
controller (SC-1) and later opensaf failed to start on same node.
 
 >> The issue is random
 
syslog--
Mar 10 16:52:40 suseR2-S1 **osafimmnd[2987]: ER Failed to load/sync. **Giving 
up after 51.061144 seconds, restarting..
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Could Not RESPAWN IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Failed   DESC:IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER FAILED TO RESPAWN
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER IMMND - Periodic server job failed
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER Failed, exiting...
Mar 10 16:52:40 suseR2-S1 osafimmd[2934]: NO MDS event from svc_id 25 
(change:4, dest:564118002024465)
Mar 10 16:52:41 suseR2-S1 osafclmna[2904]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osaffmd[2922]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osafimmd[2934]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osafrded[2913]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osaftransportd[2899]: exiting for shutdown
...
Mar 10 16:52:42 suseR2-S1 kernel: [354116.766597] TIPC: Deactivated
Mar 10 16:52:42 suseR2-S1 opensafd: Starting OpenSAF failed


Notes:
1. Immnd traces attched 


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2366 AMF: Procedure safSmfProc=AddSIsAndCSIs failed while adding more SIs and CSIs to NWAY application

[Neelakanta Reddy]

- **assigned_to**: Neelakanta Reddy
- **Comment**:

This behaviour, is observed in older releases also.



---

** [tickets:#2366] AMF: Procedure safSmfProc=AddSIsAndCSIs failed while adding 
more SIs and CSIs to NWAY application**

**Status:** duplicate
**Milestone:** 5.2.RC1
**Created:** Sat Mar 11, 2017 05:10 PM UTC by Chani Srivastava
**Last Updated:** Mon Mar 13, 2017 07:54 AM UTC
**Owner:** Neelakanta Reddy


**Duplicate** https://sourceforge.net/p/opensaf/tickets/316/


**Environment details**

OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads / no PBE )

**Steps followed & Observed behaviour**
1. Import attached xml
2. Bring up the attached NWAY.sh application
3. Execute attached campaign8.xml to add more work to the application

NewSC1:/home/scale_scripts_rpms/x86_64 # smf-state camp
safSmfCampaign=Campaign_8,safApp=safSmfService
state=EXECUTION_FAILED(10)
error='Procedure safSmfProc=AddSIsAndCSIs failed'


SC-1 syslog
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: NO Fail to invoke admin operation, too 
many SA_AIS_ERR_TRY_AGAIN, giving up. 
dn=[safSu=SU5,safSg=SGONE,safApp=NWAYAPP], opId=[3]
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: NO adminOperation: 
immUtil.callAdminOperation() Fail SA_AIS_ERR_TRY_AGAIN (6), Failed unit is 
'safSu=SU5,safSg=SGONE,safApp=NWAYAPP'
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: NO lock_in: setAdminStateSUs() Fail 
SA_AIS_ERR_TRY_AGAIN (6)
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: ER Failed to Terminate activation units 
in step=safSmfStep=0005
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: ER Step undoing failed
**Oct  2 18:10:59 NewSC1 osafsmfd[16325]: NO Step safSmfStep=0005 in procedure 
safSmfProc=AddSIsAndCSIs failed, step result 5**
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: NO CAMP: Procedure 
safSmfProc=AddSIsAndCSIs returned FAILED


SC-1smfd trace:
Oct  2 18:10:59.817029 osafsmfd 
[16325:src/smf/smfd/SmfUpgradeProcedure.cc:0209] << changeState
Oct  2 18:10:59.817034 osafsmfd [16325:src/smf/smfd/SmfProcState.cc:0188] << 
changeState
Oct  2 18:10:59.817055 osafsmfd [16325:src/smf/smfd/SmfProcState.cc:0426] NO 
Step safSmfStep=0005 in procedure safSmfProc=AddSIsAndCSIs failed, step result 5
Oct  2 18:10:59.817062 osafsmfd [16325:src/smf/smfd/SmfProcState.cc:0428] << 
executeStep
Oct  2 18:10:59.817069 osafsmfd 
[16325:src/smf/smfd/SmfUpgradeProcedure.cc:4094] << executeStep
Oct  2 18:10:59.817076 osafsmfd [16325:src/smf/smfd/SmfProcedureThread.cc:0700] 
TR Sending procedure response 3 to campaign from safSmfProc=AddSIsAndCSIs
Oct  2 18:10:59.817083 osafsmfd [16325:src/smf/smfd/SmfCampaignThread.cc:0338] 
TR Campaign thread send event type 9
Oct  2 18:10:59.817108 osafsmfd [16325:src/smf/smfd/SmfCampaignThread.cc:0577] 
TR Campaign thread received event type 9
Oct  2 18:10:59.817119 osafsmfd [16325:src/smf/smfd/SmfCampaignThread.cc:0649] 
TR Procedure result from safSmfProc=AddSIsAndCSIs = 3
Oct  2 18:10:59.817126 osafsmfd [16325:src/smf/smfd/SmfUpgradeCampaign.cc:0950] 
>> procResult
Oct  2 18:10:59.817133 osafsmfd [16325:src/smf/smfd/SmfCampState.cc:0936] >> 
procResult
Oct  2 18:10:59.817148 osafsmfd [16325:src/smf/smfd/SmfCampState.cc:0944] NO 
CAMP: Procedure safSmfProc=AddSIsAndCSIs returned FAILED




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2366 SMF: Procedure safSmfProc=AddSIsAndCSIs failed while adding more SIs and CSIs to NWAY application

[Neelakanta Reddy]

- **Comment**:

Oct 2 18:10:59 NewSC1 osafsmfd[16325]: NO Fail to invoke admin operation, too 
many SA_AIS_ERR_TRY_AGAIN, giving up. 
dn=[safSu=SU5,safSg=SGONE,safApp=NWAYAPP], opId=[3]
Oct 2 18:10:59 NewSC1 osafsmfd[16325]: NO lock_in: setAdminStateSUs() Fail 
SA_AIS_ERR_TRY_AGAIN (6)
Oct 2 18:10:59 NewSC1 osafsmfd[16325]: ER Failed to Terminate activation units 
in step=safSmfStep=0005
Oct 2 18:10:59 NewSC1 osafsmfd[16325]: ER Step undoing failed
Oct 2 18:10:59 NewSC1 osafsmfd[16325]: NO Step safSmfStep=0005 in procedure 
safSmfProc=AddSIsAndCSIs failed, step result 5

check why lock_in is giving try again for the 
safSu=SU5,safSg=SGONE,safApp=NWAYAPP.
check if the application need to be corrected. share amfd  and immnd traces why 
lock_in can not be done on object safSu=SU5,safSg=SGONE,safApp=NWAYAPP



---

** [tickets:#2366] SMF: Procedure safSmfProc=AddSIsAndCSIs failed while adding 
more SIs and CSIs to NWAY application**

**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Sat Mar 11, 2017 05:10 PM UTC by Chani Srivastava
**Last Updated:** Sat Mar 11, 2017 05:13 PM UTC
**Owner:** nobody


**Environment details**

OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads / no PBE )

**Steps followed & Observed behaviour**
1. Import attached xml
2. Bring up the attached NWAY.sh application
3. Execute attached campaign8.xml to add more work to the application

NewSC1:/home/scale_scripts_rpms/x86_64 # smf-state camp
safSmfCampaign=Campaign_8,safApp=safSmfService
state=EXECUTION_FAILED(10)
error='Procedure safSmfProc=AddSIsAndCSIs failed'


SC-1 syslog
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: NO Fail to invoke admin operation, too 
many SA_AIS_ERR_TRY_AGAIN, giving up. 
dn=[safSu=SU5,safSg=SGONE,safApp=NWAYAPP], opId=[3]
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: NO adminOperation: 
immUtil.callAdminOperation() Fail SA_AIS_ERR_TRY_AGAIN (6), Failed unit is 
'safSu=SU5,safSg=SGONE,safApp=NWAYAPP'
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: NO lock_in: setAdminStateSUs() Fail 
SA_AIS_ERR_TRY_AGAIN (6)
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: ER Failed to Terminate activation units 
in step=safSmfStep=0005
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: ER Step undoing failed
**Oct  2 18:10:59 NewSC1 osafsmfd[16325]: NO Step safSmfStep=0005 in procedure 
safSmfProc=AddSIsAndCSIs failed, step result 5**
Oct  2 18:10:59 NewSC1 osafsmfd[16325]: NO CAMP: Procedure 
safSmfProc=AddSIsAndCSIs returned FAILED


SC-1smfd trace:
Oct  2 18:10:59.817029 osafsmfd 
[16325:src/smf/smfd/SmfUpgradeProcedure.cc:0209] << changeState
Oct  2 18:10:59.817034 osafsmfd [16325:src/smf/smfd/SmfProcState.cc:0188] << 
changeState
Oct  2 18:10:59.817055 osafsmfd [16325:src/smf/smfd/SmfProcState.cc:0426] NO 
Step safSmfStep=0005 in procedure safSmfProc=AddSIsAndCSIs failed, step result 5
Oct  2 18:10:59.817062 osafsmfd [16325:src/smf/smfd/SmfProcState.cc:0428] << 
executeStep
Oct  2 18:10:59.817069 osafsmfd 
[16325:src/smf/smfd/SmfUpgradeProcedure.cc:4094] << executeStep
Oct  2 18:10:59.817076 osafsmfd [16325:src/smf/smfd/SmfProcedureThread.cc:0700] 
TR Sending procedure response 3 to campaign from safSmfProc=AddSIsAndCSIs
Oct  2 18:10:59.817083 osafsmfd [16325:src/smf/smfd/SmfCampaignThread.cc:0338] 
TR Campaign thread send event type 9
Oct  2 18:10:59.817108 osafsmfd [16325:src/smf/smfd/SmfCampaignThread.cc:0577] 
TR Campaign thread received event type 9
Oct  2 18:10:59.817119 osafsmfd [16325:src/smf/smfd/SmfCampaignThread.cc:0649] 
TR Procedure result from safSmfProc=AddSIsAndCSIs = 3
Oct  2 18:10:59.817126 osafsmfd [16325:src/smf/smfd/SmfUpgradeCampaign.cc:0950] 
>> procResult
Oct  2 18:10:59.817133 osafsmfd [16325:src/smf/smfd/SmfCampState.cc:0936] >> 
procResult
Oct  2 18:10:59.817148 osafsmfd [16325:src/smf/smfd/SmfCampState.cc:0944] NO 
CAMP: Procedure safSmfProc=AddSIsAndCSIs returned FAILED



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2288 smf: admin owner err_exist on parallel procedures

[Neelakanta Reddy]

- **Comment**:

changeset:   8676:42aafcd3b614
branch:  opensaf-5.0.x
tag: tip
parent:  8671:bf11d1e7720a
user:Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Thu Mar 09 11:13:10 2017 +0530
summary: smf: admin owner err_exist on parallel procedures [#2288]




---

** [tickets:#2288] smf: admin owner err_exist on parallel procedures**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Fri Feb 03, 2017 01:42 PM UTC by Rafael
**Last Updated:** Tue Mar 07, 2017 07:36 AM UTC
**Owner:** Rafael


Create a campaign containing several single step procedures that install 
several bundles. If the procedures are on the same saSmfExecLevel the campaign 
will sometimes fail because of conflicting admin owner on IMM object. 

[SmfImmOperation.cc:0445] TR 
SmfImmCreateOperation::execute:saImmOmAdminOwnerSet failed SA_AIS_ERR_EXIST




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2330 imm: change the selection object indication while intializing with clm at payloads

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8663:995c22479c63
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Mar 07 16:45:58 2017 +0530
summary: imm:changing clm indicating object to CLMS node up [#2330]




---

** [tickets:#2330] imm: change the selection object indication while 
intializing with clm at payloads**

**Status:** fixed
**Milestone:** 5.2.RC1
**Created:** Thu Mar 02, 2017 09:39 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Mar 02, 2017 11:59 AM UTC
**Owner:** Neelakanta Reddy


when all the nodes are brought simultaneously, payloads will be in loading 
state than syncing state.
Presently indication to clm_init_sel_obj is given at 
immnd_evt_proc_finalize_sync. when all nodes are joined the indication to 
clm_init_sel_obj wil not happen.

Solution:
The payload IMMNDs will be subscribing to CLMS, and giving indication to 
clm_init_sel_obj.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2329 IMM: Output parameter *version is not updated with A, 2, 18 after calling saImmOmInitiailize()

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8667:d73c96e41323
tag: tip
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Mar 07 16:56:20 2017 +0530
summary: imm:updated the agent version to latest supported agent version 
[#2329]




---

** [tickets:#2329] IMM: Output parameter *version is not updated with A,2,18 
after calling saImmOmInitiailize()**

**Status:** fixed
**Milestone:** 5.2.RC1
**Created:** Thu Mar 02, 2017 08:54 AM UTC by Chani Srivastava
**Last Updated:** Mon Mar 06, 2017 11:25 AM UTC
**Owner:** Neelakanta Reddy


Changeset: 8634 5.2.FC
SLES four node cluster.

Issue Observed: Version param is returning A,2,17 on calling saImmOmInitialize()

Steps to reproduce:
1. Initialize ver with A,2,18
2. Call saImmOmInitialize(None, ver)
3. Print ver

Output:
{'majorVersion': 2, 'minorVersion': 17, 'releaseCode': 65}

Expected: Output parameter should be filled with version actually supported by 
IMM service.




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2288 smf: admin owner err_exist on parallel procedures

[Neelakanta Reddy]

changeset:   8617:37f663fdfaaa
branch:  opensaf-5.1.x
parent:  8606:f667c97dab51
user:Rafael Odzakow 
date:Fri Feb 24 10:27:59 2017 +0100
summary: smf: admin owner err_exist on parallel procedures [#2288]

changeset:   8612:12d8b8f1e182
user:Rafael Odzakow 
date:Thu Feb 23 13:37:46 2017 +0100
summary: smf: admin owner err_exist on parallel procedures [#2288]



---

** [tickets:#2288] smf: admin owner err_exist on parallel procedures**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Fri Feb 03, 2017 01:42 PM UTC by Rafael
**Last Updated:** Thu Feb 23, 2017 12:57 PM UTC
**Owner:** Rafael


Create a campaign containing several single step procedures that install 
several bundles. If the procedures are on the same saSmfExecLevel the campaign 
will sometimes fail because of conflicting admin owner on IMM object. 

[SmfImmOperation.cc:0445] TR 
SmfImmCreateOperation::execute:saImmOmAdminOwnerSet failed SA_AIS_ERR_EXIST




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2343 IMM: immnd failed to spawn while starting opensaf on controller

[Neelakanta Reddy]

share immnd, immd and mds.log 


---

** [tickets:#2343] IMM: immnd failed to spawn while starting opensaf on 
controller**

**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Fri Mar 03, 2017 11:46 AM UTC by Chani Srivastava
**Last Updated:** Fri Mar 03, 2017 11:46 AM UTC
**Owner:** nobody


**Environment details**

OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads with 1PBE enabled )

Summary

immnd failed to spawn a number of times while starting openSaf on controller.
This issue is observed in various situations

1. While resetting cluster and starting OpenSaf again
2. While invoking continuous failovers.
3. While stoping and starting openSaf on standby controller.



Mar  3 15:45:49 OSAF-SC1 opensafd: Starting OpenSAF Services(5.2.FC - ) (Using 
TIPC)
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828240] TIPC: Activated (version 2.0.0)
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828391] NET: Registered protocol family 
30
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.828393] TIPC: Started in single node 
mode
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.834836] TIPC: Started in network mode
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.834839] TIPC: Own node address <1.1.1>, 
network identity 4141
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.838982] TIPC: Enabled bearer 
, discovery domain <1.1.0>, priority 10
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.840611] TIPC: Established link 
<1.1.1:eth1-1.1.2:eth1> on network plane A
Mar  3 15:45:49 OSAF-SC1 kernel: [   43.840688] TIPC: Established link 
<1.1.1:eth1-1.1.3:eth1> on network plane A
Mar  3 15:45:49 OSAF-SC1 osaftransportd[3854]: mkfifo already exists: 
/var/lib/opensaf/osaftransportd.fifo File exists
Mar  3 15:45:49 OSAF-SC1 osaftransportd[3854]: Started
Mar  3 15:45:49 OSAF-SC1 opensafd[3830]: NO Monitoring of TRANSPORT started
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: mkfifo already exists: 
/var/lib/opensaf/osafclmna.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: Started
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of CLMNA started
Mar  3 15:45:50 OSAF-SC1 osafclmna[3861]: NO 
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Mar  3 15:45:50 OSAF-SC1 osafrded[3870]: mkfifo already exists: 
/var/lib/opensaf/osafrded.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafrded[3870]: Started
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: mkfifo already exists: 
/var/lib/opensaf/osaffmd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: Started
Mar  3 15:45:50 OSAF-SC1 osaffmd[3879]: NO Remote fencing is disabled
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of HLFM started
Mar  3 15:45:50 OSAF-SC1 osafimmd[3889]: mkfifo already exists: 
/var/lib/opensaf/osafimmd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafimmd[3889]: Started
Mar  3 15:45:50 OSAF-SC1 opensafd[3830]: NO Monitoring of IMMD started
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: mkfifo already exists: 
/var/lib/opensaf/osafimmnd.fifo File exists
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: Started
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO Persistent Back-End capability 
configured, Pbe file:imm.db (suffix may get added)
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO IMMD service is UP ... 
ScAbsenseAllowed?:0 introduced?:0
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: IMM_SERVER_ANONYMOUS 
--> IMM_SERVER_CLUSTER_WAITING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_CLUSTER_WAITING --> IMM_SERVER_LOADING_PENDING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar  3 15:45:50 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_ISOLATED
Mar  3 15:45:51 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Mar  3 15:45:51 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: WA Global ABORT SYNC received for 
epoch 508
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: WA SERVER STATE: 
IMM_SERVER_SYNC_CLIENT --> IMM_SERVER_LOADING_PENDING (sync aborted)
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_UNKNOW 2827
Mar  3 15:51:01 OSAF-SC1 osafimmnd[3900]: NO Abort sync: Discarding synced 
objects
Mar  3 15:51:04 OSAF-SC1 osafimmnd[3900]: NO Abort sync: Discarding synced 
classes
Mar  3 15:51:04 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_LOADING_PENDING --> IMM_SERVER_SYNC_PENDING
Mar  3 15:51:05 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_ISOLATED
Mar  3 15:51:06 OSAF-SC1 osafimmnd[3900]: NO NODE STATE-> IMM_NODE_W_AVAILABLE
Mar  3 15:51:06 OSAF-SC1 osafimmnd[3900]: NO SERVER STATE: 
IMM_SERVER_SYNC_PENDING --> IMM_SERVER_SYNC_CLIENT
Mar  3 15:51:41 OSAF-SC1 osafimmnd[3900]: NO Implementer connected: 1223 
(RUNTIMEIMPL) <0, 2030f>
Mar  3 15:53:50 OSAF-SC1 opensafd[3830]: ER Timed-out for response from IMMND
Mar  3 15:53:50 OSAF-SC1 opensafd[3830]: ER 
Mar  3 15:53:50 OSAF-SC1 opensafd[3830]: ER Going for recovery
Mar  3 

[tickets] [opensaf:tickets] #2349 Immnd faild to load/sync during headless opeartion resulted opensaf failed to start on controller

[Neelakanta Reddy]

share corrsponding immd traces and mds.log


---

** [tickets:#2349] Immnd faild to load/sync during headless opeartion resulted 
opensaf failed to start on controller**

**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Mon Mar 06, 2017 10:06 AM UTC by Ritu Raj
**Last Updated:** Mon Mar 06, 2017 12:04 PM UTC
**Owner:** nobody
**Attachments:**

- 
[osafimmnd.tgz](https://sourceforge.net/p/opensaf/tickets/2349/attachment/osafimmnd.tgz)
 (1.0 MB; application/x-compressed-tar)


Environment details
OS : Suse 64bit
Changeset : 8634 ( 5.2.FC)
6 nodes setup(3 controller and 3 payload)

#Summary
Immnd faild to load/sync during headless opeartion resulted opensaf failed to 
start on controller

Steps followed & Observed behaviour
1. Invkoed headless 
2. after couple of headless opeartion immnd faild to load on one of the 
controller (SC-1) and later opensaf failed to start on same node.
 
 >> The issue is random
 
syslog--
Mar 10 16:52:40 suseR2-S1 **osafimmnd[2987]: ER Failed to load/sync. **Giving 
up after 51.061144 seconds, restarting..
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Could Not RESPAWN IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER Failed   DESC:IMMND
Mar 10 16:52:40 suseR2-S1 opensafd[2873]: ER FAILED TO RESPAWN
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER IMMND - Periodic server job failed
Mar 10 16:52:40 suseR2-S1 osafimmnd[2987]: ER Failed, exiting...
Mar 10 16:52:40 suseR2-S1 osafimmd[2934]: NO MDS event from svc_id 25 
(change:4, dest:564118002024465)
Mar 10 16:52:41 suseR2-S1 osafclmna[2904]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osaffmd[2922]: exiting for shutdown
Mar 10 16:52:41 suseR2-S1 osafimmd[2934]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osafrded[2913]: exiting for shutdown
Mar 10 16:52:42 suseR2-S1 osaftransportd[2899]: exiting for shutdown
...
Mar 10 16:52:42 suseR2-S1 kernel: [354116.766597] TIPC: Deactivated
Mar 10 16:52:42 suseR2-S1 opensafd: Starting OpenSAF failed


Notes:
1. Immnd traces attched 


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2329 IMM: Output parameter *version is not updated with A, 2, 18 after calling saImmOmInitiailize()

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2329] IMM: Output parameter *version is not updated with A,2,18 
after calling saImmOmInitiailize()**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Thu Mar 02, 2017 08:54 AM UTC by Chani Srivastava
**Last Updated:** Mon Mar 06, 2017 11:24 AM UTC
**Owner:** Neelakanta Reddy


Changeset: 8634 5.2.FC
SLES four node cluster.

Issue Observed: Version param is returning A,2,17 on calling saImmOmInitialize()

Steps to reproduce:
1. Initialize ver with A,2,18
2. Call saImmOmInitialize(None, ver)
3. Print ver

Output:
{'majorVersion': 2, 'minorVersion': 17, 'releaseCode': 65}

Expected: Output parameter should be filled with version actually supported by 
IMM service.




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2329 IMM: Output parameter *version is not updated with A, 2, 18 after calling saImmOmInitiailize()

[Neelakanta Reddy]

- **status**: unassigned --> accepted
- **assigned_to**: Neelakanta Reddy
- **Part**: - --> lib
- **Version**:  --> 5.2



---

** [tickets:#2329] IMM: Output parameter *version is not updated with A,2,18 
after calling saImmOmInitiailize()**

**Status:** accepted
**Milestone:** 5.2.RC1
**Created:** Thu Mar 02, 2017 08:54 AM UTC by Chani Srivastava
**Last Updated:** Thu Mar 02, 2017 08:54 AM UTC
**Owner:** Neelakanta Reddy


Changeset: 8634 5.2.FC
SLES four node cluster.

Issue Observed: Version param is returning A,2,17 on calling saImmOmInitialize()

Steps to reproduce:
1. Initialize ver with A,2,18
2. Call saImmOmInitialize(None, ver)
3. Print ver

Output:
{'majorVersion': 2, 'minorVersion': 17, 'releaseCode': 65}

Expected: Output parameter should be filled with version actually supported by 
IMM service.




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2327 imm: deadlock between IMM and CLM when integrated with CLM

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8645:0932ee5e7481
tag: tip
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Fri Mar 03 17:04:15 2017 +0530
summary: imm: init CLM in seperate thread to avoid deadlock [#2327]





---

** [tickets:#2327] imm: deadlock between IMM and CLM when integrated with CLM**

**Status:** fixed
**Milestone:** 5.2.RC1
**Created:** Wed Mar 01, 2017 06:22 AM UTC by Srikanth R
**Last Updated:** Wed Mar 01, 2017 09:27 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[opensafStartup.tgz](https://sourceforge.net/p/opensaf/tickets/2327/attachment/opensafStartup.tgz)
 (1.4 MB; application/x-compressed-tar)


Changeset: 8634 5.2.FC
SLES single node TIPC setup.


Issue : opensafd failed to startup on active controller for the first time.

Below is the output from syslog

Mar  6 01:27:19 SUSE-S1-C1 opensafd[11180]: NO Monitoring of CLMD started
Mar  6 01:27:19 SUSE-S1-C1 osafclmna[11211]: NO 
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Mar  6 01:27:19 SUSE-S1-C1 osafamfd[11301]: Started
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: WA saClmInitialize_4 returned 5
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER saImmOiInitialize failed 5
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER avd_imm_init FAILED
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER initialize_for_assignment FAILED 
2
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER initialize failed, exiting
Mar  6 01:27:29 SUSE-S1-C1 opensafd[11180]: ER Failed   DESC:AMFD
Mar  6 01:27:29 SUSE-S1-C1 opensafd[11180]: ER Going for recovery

Below is the output from clmd.
Mar  6  1:27:29.273608 osafclmd [11291:src/clm/clmd/clms_mds.c:1194] << 
clms_mds_svc_event
Mar  6  1:27:29.273644 osafclmd [11291:src/mbc/mbcsv_mds.c:0420] << 
mbcsv_mds_evt: Msg is not from same vdest, discarding
Mar  6  1:27:29.269263 osafclmd [11291:src/imm/agent/imma_oi_api.cc:2783] << 
rt_object_update_common
Mar  6  1:27:29.273697 osafclmd [11291:src/clm/clmd/clms_imm.c:0842] IN 
saImmOiRtObjectUpdate failed for cluster object with rc = 5. Trying again
Mar  6  1:27:29.273709 osafclmd [11291:src/clm/clmd/clms_imm.c:0871] << 
clms_cluster_update_rattr


Traces of clmd,amfd,amfnd,immd and immnd along with mds.log and syslog are 
attached.

This issue is random. Observed two times out of three times when started on 
lone active controller.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2330 imm: change the selection object indication while intializing with clm at payloads

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2330] imm: change the selection object indication while 
intializing with clm at payloads**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Thu Mar 02, 2017 09:39 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Mar 02, 2017 09:57 AM UTC
**Owner:** Neelakanta Reddy


when all the nodes are brought simultaneously, payloads will be in loading 
state than syncing state.
Presently indication to clm_init_sel_obj is given at 
immnd_evt_proc_finalize_sync. when all nodes are joined the indication to 
clm_init_sel_obj wil not happen.

Solution:
The payload IMMNDs will be subscribing to CLMS, and giving indication to 
clm_init_sel_obj.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2330 imm: change the selection object indication while intializing with clm at payloads

[Neelakanta Reddy]

- Description has changed:

Diff:



--- old
+++ new
@@ -2,4 +2,4 @@
 Presently indication to clm_init_sel_obj is given at 
immnd_evt_proc_finalize_sync. when all nodes are joined the indication to 
clm_init_sel_obj wil not happen.
 
 Solution:
-The payload IMMNDs will be sunscribing CLMS, and giving indication to 
clm_init_sel_obj.
+The payload IMMNDs will be subscribing to CLMS, and giving indication to 
clm_init_sel_obj.






---

** [tickets:#2330] imm: change the selection object indication while 
intializing with clm at payloads**

**Status:** accepted
**Milestone:** 5.2.RC1
**Created:** Thu Mar 02, 2017 09:39 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Mar 02, 2017 09:39 AM UTC
**Owner:** Neelakanta Reddy


when all the nodes are brought simultaneously, payloads will be in loading 
state than syncing state.
Presently indication to clm_init_sel_obj is given at 
immnd_evt_proc_finalize_sync. when all nodes are joined the indication to 
clm_init_sel_obj wil not happen.

Solution:
The payload IMMNDs will be subscribing to CLMS, and giving indication to 
clm_init_sel_obj.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2330 imm: change the selection object indication while intializing with clm at payloads

[Neelakanta Reddy]

---

** [tickets:#2330] imm: change the selection object indication while 
intializing with clm at payloads**

**Status:** accepted
**Milestone:** 5.2.RC1
**Created:** Thu Mar 02, 2017 09:39 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Mar 02, 2017 09:39 AM UTC
**Owner:** Neelakanta Reddy


when all the nodes are brought simultaneously, payloads will be in loading 
state than syncing state.
Presently indication to clm_init_sel_obj is given at 
immnd_evt_proc_finalize_sync. when all nodes are joined the indication to 
clm_init_sel_obj wil not happen.

Solution:
The payload IMMNDs will be sunscribing CLMS, and giving indication to 
clm_init_sel_obj.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2327 imm: deadlock between IMM and CLM when integrated with CLM

[Neelakanta Reddy]

- **summary**: imm: deadlock between IMM when integrated with CLM --> imm: 
deadlock between IMM and CLM when integrated with CLM



---

** [tickets:#2327] imm: deadlock between IMM and CLM when integrated with CLM**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Wed Mar 01, 2017 06:22 AM UTC by Srikanth R
**Last Updated:** Wed Mar 01, 2017 09:16 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[opensafStartup.tgz](https://sourceforge.net/p/opensaf/tickets/2327/attachment/opensafStartup.tgz)
 (1.4 MB; application/x-compressed-tar)


Changeset: 8634 5.2.FC
SLES single node TIPC setup.


Issue : opensafd failed to startup on active controller for the first time.

Below is the output from syslog

Mar  6 01:27:19 SUSE-S1-C1 opensafd[11180]: NO Monitoring of CLMD started
Mar  6 01:27:19 SUSE-S1-C1 osafclmna[11211]: NO 
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Mar  6 01:27:19 SUSE-S1-C1 osafamfd[11301]: Started
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: WA saClmInitialize_4 returned 5
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER saImmOiInitialize failed 5
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER avd_imm_init FAILED
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER initialize_for_assignment FAILED 
2
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER initialize failed, exiting
Mar  6 01:27:29 SUSE-S1-C1 opensafd[11180]: ER Failed   DESC:AMFD
Mar  6 01:27:29 SUSE-S1-C1 opensafd[11180]: ER Going for recovery

Below is the output from clmd.
Mar  6  1:27:29.273608 osafclmd [11291:src/clm/clmd/clms_mds.c:1194] << 
clms_mds_svc_event
Mar  6  1:27:29.273644 osafclmd [11291:src/mbc/mbcsv_mds.c:0420] << 
mbcsv_mds_evt: Msg is not from same vdest, discarding
Mar  6  1:27:29.269263 osafclmd [11291:src/imm/agent/imma_oi_api.cc:2783] << 
rt_object_update_common
Mar  6  1:27:29.273697 osafclmd [11291:src/clm/clmd/clms_imm.c:0842] IN 
saImmOiRtObjectUpdate failed for cluster object with rc = 5. Trying again
Mar  6  1:27:29.273709 osafclmd [11291:src/clm/clmd/clms_imm.c:0871] << 
clms_cluster_update_rattr


Traces of clmd,amfd,amfnd,immd and immnd along with mds.log and syslog are 
attached.

This issue is random. Observed two times out of three times when started on 
lone active controller.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2327 imm: deadlock between IMM when integrated with CLM

[Neelakanta Reddy]

- **summary**: Opensaf failed to start on active controller  ( random) --> imm: 
deadlock between IMM when integrated with CLM
- **status**: accepted --> review



---

** [tickets:#2327] imm: deadlock between IMM when integrated with CLM**

**Status:** review
**Milestone:** 5.2.RC1
**Created:** Wed Mar 01, 2017 06:22 AM UTC by Srikanth R
**Last Updated:** Wed Mar 01, 2017 08:42 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[opensafStartup.tgz](https://sourceforge.net/p/opensaf/tickets/2327/attachment/opensafStartup.tgz)
 (1.4 MB; application/x-compressed-tar)


Changeset: 8634 5.2.FC
SLES single node TIPC setup.


Issue : opensafd failed to startup on active controller for the first time.

Below is the output from syslog

Mar  6 01:27:19 SUSE-S1-C1 opensafd[11180]: NO Monitoring of CLMD started
Mar  6 01:27:19 SUSE-S1-C1 osafclmna[11211]: NO 
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Mar  6 01:27:19 SUSE-S1-C1 osafamfd[11301]: Started
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: WA saClmInitialize_4 returned 5
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER saImmOiInitialize failed 5
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER avd_imm_init FAILED
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER initialize_for_assignment FAILED 
2
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER initialize failed, exiting
Mar  6 01:27:29 SUSE-S1-C1 opensafd[11180]: ER Failed   DESC:AMFD
Mar  6 01:27:29 SUSE-S1-C1 opensafd[11180]: ER Going for recovery

Below is the output from clmd.
Mar  6  1:27:29.273608 osafclmd [11291:src/clm/clmd/clms_mds.c:1194] << 
clms_mds_svc_event
Mar  6  1:27:29.273644 osafclmd [11291:src/mbc/mbcsv_mds.c:0420] << 
mbcsv_mds_evt: Msg is not from same vdest, discarding
Mar  6  1:27:29.269263 osafclmd [11291:src/imm/agent/imma_oi_api.cc:2783] << 
rt_object_update_common
Mar  6  1:27:29.273697 osafclmd [11291:src/clm/clmd/clms_imm.c:0842] IN 
saImmOiRtObjectUpdate failed for cluster object with rc = 5. Trying again
Mar  6  1:27:29.273709 osafclmd [11291:src/clm/clmd/clms_imm.c:0871] << 
clms_cluster_update_rattr


Traces of clmd,amfd,amfnd,immd and immnd along with mds.log and syslog are 
attached.

This issue is random. Observed two times out of three times when started on 
lone active controller.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2327 Opensaf failed to start on active controller ( random)

[Neelakanta Reddy]

The case is similar to #1731, when NTF is integrated with CLM


---

** [tickets:#2327] Opensaf failed to start on active controller  ( random)**

**Status:** accepted
**Milestone:** 5.2.RC1
**Created:** Wed Mar 01, 2017 06:22 AM UTC by Srikanth R
**Last Updated:** Wed Mar 01, 2017 07:28 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[opensafStartup.tgz](https://sourceforge.net/p/opensaf/tickets/2327/attachment/opensafStartup.tgz)
 (1.4 MB; application/x-compressed-tar)


Changeset: 8634 5.2.FC
SLES single node TIPC setup.


Issue : opensafd failed to startup on active controller for the first time.

Below is the output from syslog

Mar  6 01:27:19 SUSE-S1-C1 opensafd[11180]: NO Monitoring of CLMD started
Mar  6 01:27:19 SUSE-S1-C1 osafclmna[11211]: NO 
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Mar  6 01:27:19 SUSE-S1-C1 osafamfd[11301]: Started
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: WA saClmInitialize_4 returned 5
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER saImmOiInitialize failed 5
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER avd_imm_init FAILED
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER initialize_for_assignment FAILED 
2
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER initialize failed, exiting
Mar  6 01:27:29 SUSE-S1-C1 opensafd[11180]: ER Failed   DESC:AMFD
Mar  6 01:27:29 SUSE-S1-C1 opensafd[11180]: ER Going for recovery

Below is the output from clmd.
Mar  6  1:27:29.273608 osafclmd [11291:src/clm/clmd/clms_mds.c:1194] << 
clms_mds_svc_event
Mar  6  1:27:29.273644 osafclmd [11291:src/mbc/mbcsv_mds.c:0420] << 
mbcsv_mds_evt: Msg is not from same vdest, discarding
Mar  6  1:27:29.269263 osafclmd [11291:src/imm/agent/imma_oi_api.cc:2783] << 
rt_object_update_common
Mar  6  1:27:29.273697 osafclmd [11291:src/clm/clmd/clms_imm.c:0842] IN 
saImmOiRtObjectUpdate failed for cluster object with rc = 5. Trying again
Mar  6  1:27:29.273709 osafclmd [11291:src/clm/clmd/clms_imm.c:0871] << 
clms_cluster_update_rattr


Traces of clmd,amfd,amfnd,immd and immnd along with mds.log and syslog are 
attached.

This issue is random. Observed two times out of three times when started on 
lone active controller.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2327 Opensaf failed to start on active controller ( random)

[Neelakanta Reddy]

- **status**: invalid --> accepted
- **assigned_to**: Neelakanta Reddy
- **Component**: unknown --> imm
- **Part**: - --> nd
- **Comment**:

IMMND is waiting for CLM and CLM is waiting for IMMND, there is a deadlock

Mar  6  1:27:19.253312 osafimmnd [11250:src/imm/immnd/immnd_mds.c:0656] << 
immnd_mds_svc_evt 
Mar  6  1:27:19.253739 osafimmnd [11250:src/base/osaf_secutil.c:0068] >> 
handle_new_connection 
Mar  6  1:27:19.253766 osafimmnd [11250:src/mds/mds_main.c:0135] >> 
mds_register_callback: fd:24, pid:11301
Mar  6  1:27:19.253778 osafimmnd [11250:src/mds/mds_main.c:0153] TR MDS: 
received 77 from 2010f0690c01f, pid 11301
Mar  6  1:27:19.253789 osafimmnd [11250:src/mds/mds_c_db.c:2516] >> 
mds_process_info_add: dest:2010f0690c01f, pid:11301, svc:27
Mar  6  1:27:19.253875 osafimmnd [11250:src/mds/mds_main.c:0211] << 
mds_register_callback 
Mar  6  1:27:19.253894 osafimmnd [11250:src/base/osaf_secutil.c:0104] << 
handle_new_connection 
Mar  6  1:27:29.050878 osafimmnd [11250:src/mds/mds_dt_common.c:0861] TR 
TIMEOUT, deleting entry for 2010f0690c013, pid:11257
Mar  6  1:27:29.050976 osafimmnd [11250:src/mds/mds_c_db.c:2527] >> 
mds_process_info_del: dest:2010f0690c013, pid:11257, svc:26
Mar  6  1:27:29.265643 osafimmnd [11250:src/clm/agent/clma_mds.c:1251] TR 
clma_mds_msg_sync_send FAILED
Mar  6  1:27:29.265668 osafimmnd [11250:src/clm/agent/clma_mds.c:1253] << 
clma_mds_msg_sync_send 
Mar  6  1:27:29.265683 osafimmnd [11250:src/clm/agent/clma_api.c:0623] TR 
clma_mds_msg_sync_send FAILED: 5
Mar  6  1:27:29.265696 osafimmnd [11250:src/clm/agent/clma_api.c:0662] T2 CLMA 
INIT FAILED
Mar  6  1:27:29.265709 osafimmnd [11250:src/clm/agent/clma_util.c:0133] >> 
clma_shutdown: clma_use_count: 1

Solution :
These deadlock can be removed when clmInitialize is done in seperate thread.




---

** [tickets:#2327] Opensaf failed to start on active controller  ( random)**

**Status:** accepted
**Milestone:** 5.2.RC1
**Created:** Wed Mar 01, 2017 06:22 AM UTC by Srikanth R
**Last Updated:** Wed Mar 01, 2017 07:16 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[opensafStartup.tgz](https://sourceforge.net/p/opensaf/tickets/2327/attachment/opensafStartup.tgz)
 (1.4 MB; application/x-compressed-tar)


Changeset: 8634 5.2.FC
SLES single node TIPC setup.


Issue : opensafd failed to startup on active controller for the first time.

Below is the output from syslog

Mar  6 01:27:19 SUSE-S1-C1 opensafd[11180]: NO Monitoring of CLMD started
Mar  6 01:27:19 SUSE-S1-C1 osafclmna[11211]: NO 
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Mar  6 01:27:19 SUSE-S1-C1 osafamfd[11301]: Started
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: WA saClmInitialize_4 returned 5
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER saImmOiInitialize failed 5
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER avd_imm_init FAILED
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER initialize_for_assignment FAILED 
2
Mar  6 01:27:29 SUSE-S1-C1 osafamfd[11301]: ER initialize failed, exiting
Mar  6 01:27:29 SUSE-S1-C1 opensafd[11180]: ER Failed   DESC:AMFD
Mar  6 01:27:29 SUSE-S1-C1 opensafd[11180]: ER Going for recovery

Below is the output from clmd.
Mar  6  1:27:29.273608 osafclmd [11291:src/clm/clmd/clms_mds.c:1194] << 
clms_mds_svc_event
Mar  6  1:27:29.273644 osafclmd [11291:src/mbc/mbcsv_mds.c:0420] << 
mbcsv_mds_evt: Msg is not from same vdest, discarding
Mar  6  1:27:29.269263 osafclmd [11291:src/imm/agent/imma_oi_api.cc:2783] << 
rt_object_update_common
Mar  6  1:27:29.273697 osafclmd [11291:src/clm/clmd/clms_imm.c:0842] IN 
saImmOiRtObjectUpdate failed for cluster object with rc = 5. Trying again
Mar  6  1:27:29.273709 osafclmd [11291:src/clm/clmd/clms_imm.c:0871] << 
clms_cluster_update_rattr


Traces of clmd,amfd,amfnd,immd and immnd along with mds.log and syslog are 
attached.

This issue is random. Observed two times out of three times when started on 
lone active controller.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1640 Integrate IMM service with CLM

[Neelakanta Reddy]

- **Comment**:

changeset:   8626:c5eee2837fcd
tag: tip
user:Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Feb 28 06:35:03 2017 +0530
summary: imm:Adding immnd_clm file for  IMM service with CLM [#1640]




---

** [tickets:#1640] Integrate IMM service with CLM**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Tue Dec 15, 2015 08:32 AM UTC by Mathi Naickan
**Last Updated:** Tue Feb 28, 2017 01:49 AM UTC
**Owner:** Neelakanta Reddy


IMM Behavior of CLM integration:
1.  section 3.3 of IMM Spec (A.02.01).
2.  SA_AIS_ERR_UNAVAILABLE return code for APIs in IMM Spec.

IMMA:
New IMMA version A.2.18 wil be introduced for the CLMS integration with IMMA.
SA_AIS_ERR_UNAVAILABLE will be returned when the CLMS service is not available,
as per the IMM specification.

IMMND:
Register for CLM Track callback. From the callback, CLM status information
will be sent to IMMA.

IMMD:
Register for CLM Track callback. When the CLM node leaves the cluster, the 
IMMND is 
removed from the IMMD internal database. IMMND node down is broadcasted to 
remaining 
IMMNDs in the cluster.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1640 Integrate IMM service with CLM

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8625:e5ff49d5052d
tag: tip
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Feb 28 06:22:42 2017 +0530
summary: imm:Integration of IMM service with CLM [#1640]




---

** [tickets:#1640] Integrate IMM service with CLM**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Tue Dec 15, 2015 08:32 AM UTC by Mathi Naickan
**Last Updated:** Tue Feb 21, 2017 06:05 AM UTC
**Owner:** Neelakanta Reddy


IMM Behavior of CLM integration:
1.  section 3.3 of IMM Spec (A.02.01).
2.  SA_AIS_ERR_UNAVAILABLE return code for APIs in IMM Spec.

IMMA:
New IMMA version A.2.18 wil be introduced for the CLMS integration with IMMA.
SA_AIS_ERR_UNAVAILABLE will be returned when the CLMS service is not available,
as per the IMM specification.

IMMND:
Register for CLM Track callback. From the callback, CLM status information
will be sent to IMMA.

IMMD:
Register for CLM Track callback. When the CLM node leaves the cluster, the 
IMMND is 
removed from the IMMD internal database. IMMND node down is broadcasted to 
remaining 
IMMNDs in the cluster.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2004 SMF: smfd crashed when triggered campaign with gcc 6.1

[Neelakanta Reddy]

- **Comment**:

Tried to reproduce with chengeset 8611 anf 6.1.0 GCC by running 2N application 
campaign.
I did not observe any crash.



---

** [tickets:#2004] SMF: smfd crashed when triggered campaign with gcc 6.1**

**Status:** unassigned
**Milestone:** 5.0.2
**Created:** Tue Sep 06, 2016 08:35 AM UTC by Madhurika Koppula
**Last Updated:** Thu Jan 05, 2017 06:48 AM UTC
**Owner:** nobody
**Attachments:**

- [smf.tgz](https://sourceforge.net/p/opensaf/tickets/2004/attachment/smf.tgz) 
(1.6 MB; application/octet-stream)


**Environment Details:**

OS : Suse 64bit
Changeset : 7997 ( 5.1.FC)
Setup : 4 nodes ( 2 controllers and 2 payloads with headless feature disabled & 
1PBE enabled ).
GCC version : 6.1

**Note: Crash not observed with gcc 4.8 compiled rpms**

**summary:**

smfd got crashed due to segfault on active controller.

**Steps followed & Observed behaviour:**

Test SGupgrade of 2N model with valid configurations.

**Observations:**

Active controller went for reboot due to avadown for smfd.

Below is the snippet of syslog on active controller:

Sep  6 11:52:19 SLES-M-SLOT-1 osafsmfd[3745]: NO 
SmfProcedureThread::getImmProcedure, IMM data for procedure 
safSmfProc=amfClusterProc-1,safSmfCampaign=Campaign2,safApp=safSmfService not 
found
Sep  6 11:52:19 SLES-M-SLOT-1 osafimmnd[3661]: NO Implementer connected: 20 
(safSmfProc1) <662, 2010f>
Sep  6 11:52:19 SLES-M-SLOT-1 osafsmfd[3745]: NO PROC: Start upgrade procedure 
safSmfProc=amfClusterProc-1
Sep  6 11:52:19 SLES-M-SLOT-1 osafsmfd[3745]: NO PROC: Start procedure init 
actions

Sep  6 11:52:19 SLES-M-SLOT-1 osafamfnd[3726]: NO 
'safComp=SMF,safSu=SC-1,safSg=2N,safApp=OpenSAF' faulted due to 'avaDown' : 
Recovery is 'nodeFailfast'

**Sep  6 11:52:19 SLES-M-SLOT-1 osafamfnd[3726]: ER 
safComp=SMF,safSu=SC-1,safSg=2N,safApp=OpenSAF Faulted due to:avaDown Recovery 
is:nodeFailfast**

Sep  6 11:52:19 SLES-M-SLOT-1 osafamfnd[3726]: Rebooting OpenSAF NodeId = 
131343 EE Name = , Reason: Component faulted: recovery is node failfast, 
OwnNodeId = 131343, SupervisionTime = 60

Below is the snippet of osafsmfd trace on active controller:

Sep  6 11:52:19.808986 osafsmfd [3745:SmfUpgradeProcedure.cc:0741] TR 
SmfUpgradeProcedure::calculateRollingSteps:calculateRollingSteps new SW install 
step added safSmfStep=0003 (with no act/deact unit) for node 
safAmfNode=PL-4,safAmfCluster=myAmfCluster
Sep  6 11:52:19.808995 osafsmfd [3745:SmfUpgradeProcedure.cc:1876] >> 
addStepModifications
Sep  6 11:52:19.809002 osafsmfd [3745:SmfUpgradeProcedure.cc:1931] >> 
addStepModificationsNode
Sep  6 11:52:19.809008 osafsmfd [3745:imma_om_api.c:0160] >> saImmOmInitialize
Sep  6 11:52:19.809015 osafsmfd [3745:imma_om_api.c:0186] TR OM client version 
A.2.1
Sep  6 11:52:19.809021 osafsmfd [3745:imma_om_api.c:0228] >> initialize_common
Sep  6 11:52:19.809026 osafsmfd [3745:imma_init.c:0275] >> imma_startup: use 
count 1
Sep  6 11:52:19.809032 osafsmfd [3745:imma_init.c:0298] << imma_startup: use 
count 2
Sep  6 11:52:19.809040 osafsmfd [3745:imma_om_api.c:0246] T2 IMMA library 
syncronous timeout set to:3
Sep  6 11:52:19.809263 osafsmfd [3745:imma_om_api.c:0349] T1 Trying to add OM 
client id:727 node:2010f
Sep  6 11:52:19.809280 osafsmfd [3745:imma_om_api.c:0442] << initialize_common
Sep  6 11:52:19.809287 osafsmfd [3745:imma_om_api.c:0214] << saImmOmInitialize
Sep  6 11:52:19.809293 osafsmfd [3745:imma_om_api.c:0931] >> 
saImmOmAdminOwnerInitialize
Sep  6 11:52:19.811060 osafsmfd [3745:imma_om_api.c:1143] T1 Admin owner init 
successful
Sep  6 11:52:19.811076 osafsmfd [3745:imma_om_api.c:1144] << 
saImmOmAdminOwnerInitialize
Sep  6 11:52:19.811083 osafsmfd [3745:imma_om_api.c:5528] >> 
saImmOmAccessorInitialize
Sep  6 11:52:19.811091 osafsmfd [3745:imma_om_api.c:5626] << 
saImmOmAccessorInitialize
Sep  6 12:21:09.873661 osafsmfd [2421:ncs_main_pub.c:0220] TR
NCS:PROCESS_ID=2421

Attachments:
Active Controller:
1)syslog
2)osafsmfd, osafsmfnd traces.
3)osafimmnd traces.



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1640 Integrate IMM service with CLM

[Neelakanta Reddy]

- **status**: accepted --> review
- **Comment**:

https://sourceforge.net/p/opensaf/mailman/message/35678680/



---

** [tickets:#1640] Integrate IMM service with CLM**

**Status:** review
**Milestone:** 5.2.FC
**Created:** Tue Dec 15, 2015 08:32 AM UTC by Mathi Naickan
**Last Updated:** Mon Jan 16, 2017 06:14 AM UTC
**Owner:** Neelakanta Reddy


IMM Behavior of CLM integration:
1.  section 3.3 of IMM Spec (A.02.01).
2.  SA_AIS_ERR_UNAVAILABLE return code for APIs in IMM Spec.

IMMA:
New IMMA version A.2.18 wil be introduced for the CLMS integration with IMMA.
SA_AIS_ERR_UNAVAILABLE will be returned when the CLMS service is not available,
as per the IMM specification.

IMMND:
Register for CLM Track callback. From the callback, CLM status information
will be sent to IMMA.

IMMD:
Register for CLM Track callback. When the CLM node leaves the cluster, the 
IMMND is 
removed from the IMMD internal database. IMMND node down is broadcasted to 
remaining 
IMMNDs in the cluster.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2277 smf: smf failed to set saAmfSUMaintenanceCampaign set , when ccb is aborted due to immnd sync

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8552:63084c85e928
tag: tip
parent:  8549:346005001e6f
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Wed Feb 01 16:25:33 2017 +0530
summary: smf: retry the ccb modify operation when the ccb is aborted with 
resource abort [#2277]

changeset:   8551:2aea0b91ae5a
branch:  opensaf-5.1.x
parent:  8547:12e6a9128684
user:Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Wed Feb 01 16:14:06 2017 +0530
summary: smf: retry the ccb modify operation when the ccb is aborted with 
resource abort [#2277]

changeset:   8550:431ac44d8ee4
branch:  opensaf-5.0.x
parent:  8546:8543ff234ae2
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Wed Feb 01 16:14:06 2017 +0530
summary: smf: retry the ccb modify operation when the ccb is aborted with 
resource abort [#2277]




---

** [tickets:#2277] smf: smf failed to set saAmfSUMaintenanceCampaign  set , 
when ccb is aborted due to immnd sync**

**Status:** fixed
**Milestone:** 5.0.2
**Created:** Wed Jan 25, 2017 11:25 AM UTC by Neelakanta Reddy
**Last Updated:** Mon Jan 30, 2017 01:27 PM UTC
**Owner:** Neelakanta Reddy


Jan 19 06:01:25 sc2 osafsmfd[6110]: NO CAMP: Campaign wrapup, reset 
saAmfSUMaintenanceCampaign flags
Jan 19 06:01:25 sc2 osafimmd[5983]: NO Node 2030f request sync sync-pid:3965 
epoch:0
Jan 19 06:01:25 sc2 osafimmnd[6000]: NO Announce sync, epoch:52
Jan 19 06:01:25 sc2 osafimmnd[6000]: NO SERVER STATE: IMM_SERVER_READY --> 
IMM_SERVER_SYNC_SERVER
Jan 19 06:01:25 sc2 osafimmnd[6000]: NO NODE STATE-> IMM_NODE_R_AVAILABLE
Jan 19 06:01:29 sc2 osafimmnd[6000]: NO Precheck of fevs message of type <33> 
failed with ERROR:18
Jan 19 06:01:30 sc2 osafimmnd[6000]: WA Aborting ccbId  59 to start sync
Jan 19 06:01:30 sc2 osafimmnd[6000]: NO Ccb 59 ABORTED (SMFSERVICE)
Jan 19 06:01:30 sc2 osafsmfd[6110]: NO saImmOmCcbApply failed 
rc=SA_AIS_ERR_FAILED_OPERATION (21)

The campaign is cmmited sucefully, but when another campaign is executed, 
failed with error:
ER Failed to set maintenance state in step=safSmfStep=0001

solution:
use  saImmOmCcbGetErrorStrings, to find VALIDATION/RESOURCE ABORT.
If it is RESOURCE ABORT retry reset saAmfSUMaintenanceCampaign



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2284 IMM: Improper return code without any error string while deleting large number of objects

[Neelakanta Reddy]

The IMM service, says that the default number of supported objects is 1 for 
one CCB., Beyond which there may be corruptuion.in IMM.  if your environment 
can support,  then the limit of  IMMSV_MAX_OBJECTS can be increased  grater 
than 1.


---

** [tickets:#2284] IMM: Improper return code without any error string while 
deleting large number of objects**

**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Wed Feb 01, 2017 07:13 AM UTC by Chani Srivastava
**Last Updated:** Wed Feb 01, 2017 08:34 AM UTC
**Owner:** nobody


Steps to reproduce:

1. Bring up opensaf on a cluster
2. Create around 10k objects
3. Try deleating these objects in one immcfg operation

Output:
Error Returned - error - saImmOmAdminOwnerSet FAILED: SA_AIS_ERR_LIBRARY (2)

No error string stating the cause of failure is returned.

Syslog - immcfg: ER TOO MANY Object Names line:733

Expected behavior - Proper return code with error string should be returned 


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2284 IMM: Improper return code without any error string while deleting large number of objects

[Neelakanta Reddy]

- **Comment**:

>From the IMM README:

Only errors that could be returned, directly or indirectly
by an OI, such as FAILED_OPERATION or BAD_OPERATION should
be expected to possibly have an error string.




---

** [tickets:#2284] IMM: Improper return code without any error string while 
deleting large number of objects**

**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Wed Feb 01, 2017 07:13 AM UTC by Chani Srivastava
**Last Updated:** Wed Feb 01, 2017 07:13 AM UTC
**Owner:** nobody


Steps to reproduce:

1. Bring up opensaf on a cluster
2. Create around 10k objects
3. Try deleating these objects in one immcfg operation

Output:
Error Returned - error - saImmOmAdminOwnerSet FAILED: SA_AIS_ERR_LIBRARY (2)

No error string stating the cause of failure is returned.

Syslog - immcfg: ER TOO MANY Object Names line:733

Expected behavior - Proper error string should be returned 


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2277 smf: smf failed to set saAmfSUMaintenanceCampaign set , when ccb is aborted due to immnd sync

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2277] smf: smf failed to set saAmfSUMaintenanceCampaign  set , 
when ccb is aborted due to immnd sync**

**Status:** review
**Milestone:** 5.0.2
**Created:** Wed Jan 25, 2017 11:25 AM UTC by Neelakanta Reddy
**Last Updated:** Wed Jan 25, 2017 11:25 AM UTC
**Owner:** Neelakanta Reddy


Jan 19 06:01:25 sc2 osafsmfd[6110]: NO CAMP: Campaign wrapup, reset 
saAmfSUMaintenanceCampaign flags
Jan 19 06:01:25 sc2 osafimmd[5983]: NO Node 2030f request sync sync-pid:3965 
epoch:0
Jan 19 06:01:25 sc2 osafimmnd[6000]: NO Announce sync, epoch:52
Jan 19 06:01:25 sc2 osafimmnd[6000]: NO SERVER STATE: IMM_SERVER_READY --> 
IMM_SERVER_SYNC_SERVER
Jan 19 06:01:25 sc2 osafimmnd[6000]: NO NODE STATE-> IMM_NODE_R_AVAILABLE
Jan 19 06:01:29 sc2 osafimmnd[6000]: NO Precheck of fevs message of type <33> 
failed with ERROR:18
Jan 19 06:01:30 sc2 osafimmnd[6000]: WA Aborting ccbId  59 to start sync
Jan 19 06:01:30 sc2 osafimmnd[6000]: NO Ccb 59 ABORTED (SMFSERVICE)
Jan 19 06:01:30 sc2 osafsmfd[6110]: NO saImmOmCcbApply failed 
rc=SA_AIS_ERR_FAILED_OPERATION (21)

The campaign is cmmited sucefully, but when another campaign is executed, 
failed with error:
ER Failed to set maintenance state in step=safSmfStep=0001

solution:
use  saImmOmCcbGetErrorStrings, to find VALIDATION/RESOURCE ABORT.
If it is RESOURCE ABORT retry reset saAmfSUMaintenanceCampaign



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2277 smf: smf failed to set saAmfSUMaintenanceCampaign set , when ccb is aborted due to immnd sync

[Neelakanta Reddy]

---

** [tickets:#2277] smf: smf failed to set saAmfSUMaintenanceCampaign  set , 
when ccb is aborted due to immnd sync**

**Status:** accepted
**Milestone:** 5.0.2
**Created:** Wed Jan 25, 2017 11:25 AM UTC by Neelakanta Reddy
**Last Updated:** Wed Jan 25, 2017 11:25 AM UTC
**Owner:** Neelakanta Reddy


Jan 19 06:01:25 sc2 osafsmfd[6110]: NO CAMP: Campaign wrapup, reset 
saAmfSUMaintenanceCampaign flags
Jan 19 06:01:25 sc2 osafimmd[5983]: NO Node 2030f request sync sync-pid:3965 
epoch:0
Jan 19 06:01:25 sc2 osafimmnd[6000]: NO Announce sync, epoch:52
Jan 19 06:01:25 sc2 osafimmnd[6000]: NO SERVER STATE: IMM_SERVER_READY --> 
IMM_SERVER_SYNC_SERVER
Jan 19 06:01:25 sc2 osafimmnd[6000]: NO NODE STATE-> IMM_NODE_R_AVAILABLE
Jan 19 06:01:29 sc2 osafimmnd[6000]: NO Precheck of fevs message of type <33> 
failed with ERROR:18
Jan 19 06:01:30 sc2 osafimmnd[6000]: WA Aborting ccbId  59 to start sync
Jan 19 06:01:30 sc2 osafimmnd[6000]: NO Ccb 59 ABORTED (SMFSERVICE)
Jan 19 06:01:30 sc2 osafsmfd[6110]: NO saImmOmCcbApply failed 
rc=SA_AIS_ERR_FAILED_OPERATION (21)

The campaign is cmmited sucefully, but when another campaign is executed, 
failed with error:
ER Failed to set maintenance state in step=safSmfStep=0001

solution:
use  saImmOmCcbGetErrorStrings, to find VALIDATION/RESOURCE ABORT.
If it is RESOURCE ABORT retry reset saAmfSUMaintenanceCampaign



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1791 smf: use CLM cluster tracking instead of reading per node up for SMFND

[Neelakanta Reddy]

- **Milestone**: 5.2.FC --> future



---

** [tickets:#1791] smf: use CLM cluster tracking instead of reading per node up 
for SMFND**

**Status:** accepted
**Milestone:** future
**Labels:** cluster tracking avoidnodeget spare adminlock 
**Created:** Thu Apr 28, 2016 02:49 PM UTC by Mathi Naickan
**Last Updated:** Fri Nov 11, 2016 11:35 AM UTC
**Owner:** Neelakanta Reddy


SMF is currently using saClmClusterNodeGet() for every SMFND_UP that it 
receives.
In the context of issues like ticket #1781, SMF should be made to handle 
ERR_UNAVAILABLE error code and to be able to make use the saClmClusterTrack() 
API.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1209 IMM: OI callback timer should be restored after a ccb-augment is closed

[Neelakanta Reddy]

- **Milestone**: 5.2.FC --> future



---

** [tickets:#1209] IMM: OI callback timer should be restored after a 
ccb-augment is closed**

**Status:** assigned
**Milestone:** future
**Created:** Tue Nov 11, 2014 12:49 PM UTC by Anders Bjornerstedt
**Last Updated:** Mon Aug 29, 2016 08:13 PM UTC
**Owner:** Neelakanta Reddy


This is related to ticket #1208.

http://sourceforge.net/p/opensaf/tickets/1208/

After an OI has closed a ccb-augmentation, the callback timer monitoring 
the liveness of the OI in that callback, should be restored. 

This requires the addition of a new message type to the IMMA->IMMND protocol.



---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1640 Integrate IMM service with CLM

[Neelakanta Reddy]

- Description has changed:

Diff:



--- old
+++ new
@@ -1 +1,17 @@
-More details TBD
+IMM Behavior of CLM integration:
+1.  section 3.3 of IMM Spec (A.02.01).
+2.  SA_AIS_ERR_UNAVAILABLE return code for APIs in IMM Spec.
+
+IMMA:
+New IMMA version A.2.18 wil be introduced for the CLMS integration with IMMA.
+SA_AIS_ERR_UNAVAILABLE will be returned when the CLMS service is not available,
+as per the IMM specification.
+
+IMMND:
+Register for CLM Track callback. From the callback, CLM status information
+will be sent to IMMA.
+
+IMMD:
+Register for CLM Track callback. When the CLM node leaves the cluster, the 
IMMND is 
+removed from the IMMD internal database. IMMND node down is broadcasted to 
remaining 
+IMMNDs in the cluster.






---

** [tickets:#1640] Integrate IMM service with CLM**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Tue Dec 15, 2015 08:32 AM UTC by Mathi Naickan
**Last Updated:** Mon Oct 17, 2016 06:27 AM UTC
**Owner:** Neelakanta Reddy


IMM Behavior of CLM integration:
1.  section 3.3 of IMM Spec (A.02.01).
2.  SA_AIS_ERR_UNAVAILABLE return code for APIs in IMM Spec.

IMMA:
New IMMA version A.2.18 wil be introduced for the CLMS integration with IMMA.
SA_AIS_ERR_UNAVAILABLE will be returned when the CLMS service is not available,
as per the IMM specification.

IMMND:
Register for CLM Track callback. From the callback, CLM status information
will be sent to IMMA.

IMMD:
Register for CLM Track callback. When the CLM node leaves the cluster, the 
IMMND is 
removed from the IMMD internal database. IMMND node down is broadcasted to 
remaining 
IMMNDs in the cluster.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2229 imm:disable pbe should honor critical ccbs

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8497:110fe121d8e2
tag: tip
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Fri Jan 06 12:25:53 2017 +0530
summary: imm: return TRY_AGAIN when RepositoryInit mode is chaged to file, 
during the CCB PBE disable processing [#2229]




---

** [tickets:#2229] imm:disable pbe should honor critical ccbs**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Wed Dec 14, 2016 09:29 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Dec 22, 2016 09:51 AM UTC
**Owner:** Neelakanta Reddy


reproducible steps:
1. Bring up the cluster with PBE configured.
2. enable PBE
3. parallely run multiple ccb operations
4. disable PBE
5. in one of the payload/controller restart the immnd/node
6. sync wil be aboreted with following messages 
 WA PBE has been disabled with ccbs in critical state - To resolve: Enable PBE 
or resart/reload the cluster
  NO Still waiting for existing Ccbs to terminate after 20.027520 seconds. 
Aborting this sync attempt
7. The IMMND will never get synced untill cluster restart

The problem is observed, when the node is not joining in middleware upgrade, 
and evetually upgrade fails.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2229 imm:disable pbe should honor critical ccbs

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2229] imm:disable pbe should honor critical ccbs**

**Status:** review
**Milestone:** 5.2.FC
**Created:** Wed Dec 14, 2016 09:29 AM UTC by Neelakanta Reddy
**Last Updated:** Fri Dec 16, 2016 09:55 AM UTC
**Owner:** Neelakanta Reddy


reproducible steps:
1. Bring up the cluster with PBE configured.
2. enable PBE
3. parallely run multiple ccb operations
4. disable PBE
5. in one of the payload/controller restart the immnd/node
6. sync wil be aboreted with following messages 
 WA PBE has been disabled with ccbs in critical state - To resolve: Enable PBE 
or resart/reload the cluster
  NO Still waiting for existing Ccbs to terminate after 20.027520 seconds. 
Aborting this sync attempt
7. The IMMND will never get synced untill cluster restart

The problem is observed, when the node is not joining in middleware upgrade, 
and evetually upgrade fails.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2229 imm:disable pbe should honor critical ccbs

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2229] imm:disable pbe should honor critical ccbs**

**Status:** review
**Milestone:** 5.2.FC
**Created:** Wed Dec 14, 2016 09:29 AM UTC by Neelakanta Reddy
**Last Updated:** Wed Dec 14, 2016 09:30 AM UTC
**Owner:** Neelakanta Reddy


reproducible steps:
1. Bring up the cluster with PBE configured.
2. enable PBE
3. parallely run multiple ccb operations
4. disable PBE
5. in one of the payload/controller restart the immnd/node
6. sync wil be aboreted with following messages 
 WA PBE has been disabled with ccbs in critical state - To resolve: Enable PBE 
or resart/reload the cluster
  NO Still waiting for existing Ccbs to terminate after 20.027520 seconds. 
Aborting this sync attempt
7. The IMMND will never get synced untill cluster restart

The problem is observed, when the node is not joining in middleware upgrade, 
and evetually upgrade fails.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2229 imm:disable pbe should honor critical ccbs

[Neelakanta Reddy]

- **summary**: imm:disable pbe should be honor critical ccbs --> imm:disable 
pbe should honor critical ccbs



---

** [tickets:#2229] imm:disable pbe should honor critical ccbs**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Wed Dec 14, 2016 09:29 AM UTC by Neelakanta Reddy
**Last Updated:** Wed Dec 14, 2016 09:29 AM UTC
**Owner:** Neelakanta Reddy


reproducible steps:
1. Bring up the cluster with PBE configured.
2. enable PBE
3. parallely run multiple ccb operations
4. disable PBE
5. in one of the payload/controller restart the immnd/node
6. sync wil be aboreted with following messages 
 WA PBE has been disabled with ccbs in critical state - To resolve: Enable PBE 
or resart/reload the cluster
  NO Still waiting for existing Ccbs to terminate after 20.027520 seconds. 
Aborting this sync attempt
7. The IMMND will never get synced untill cluster restart

The problem is observed, when the node is not joining in middleware upgrade, 
and evetually upgrade fails.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2229 imm:disable pbe should be honor critical ccbs

[Neelakanta Reddy]

---

** [tickets:#2229] imm:disable pbe should be honor critical ccbs**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Wed Dec 14, 2016 09:29 AM UTC by Neelakanta Reddy
**Last Updated:** Wed Dec 14, 2016 09:29 AM UTC
**Owner:** Neelakanta Reddy


reproducible steps:
1. Bring up the cluster with PBE configured.
2. enable PBE
3. parallely run multiple ccb operations
4. disable PBE
5. in one of the payload/controller restart the immnd/node
6. sync wil be aboreted with following messages 
 WA PBE has been disabled with ccbs in critical state - To resolve: Enable PBE 
or resart/reload the cluster
  NO Still waiting for existing Ccbs to terminate after 20.027520 seconds. 
Aborting this sync attempt
7. The IMMND will never get synced untill cluster restart

The problem is observed, when the node is not joining in middleware upgrade, 
and evetually upgrade fails.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2227 smf:ONE-STEP upgrade failed due to duplicated entities in comp and SU

[Neelakanta Reddy]

---

** [tickets:#2227] smf:ONE-STEP upgrade failed due to duplicated entities in 
comp and SU**

**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Tue Dec 13, 2016 06:16 AM UTC by Neelakanta Reddy
**Last Updated:** Tue Dec 13, 2016 06:16 AM UTC
**Owner:** nobody


This Ticket is extension of #2209.
In #2209 if a campaign contains both rolling and singlestep.
The singlestep contains duplicated node forAddremove AU/DU present in the 
rolling upgrad also.

This ticket is related to duplcated entities SU and comp present in 
forAddRemove and rolling procedure.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2209 SMF: ONE-STEP upgrade failed due to duplicated entities in AU/DU

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8429:91b55c7c9848
branch:  opensaf-5.0.x
parent:  8426:e44bf1a904b6
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Mon Dec 12 11:06:08 2016 +0530
summary: smf:Allow optimization at node level forAddRemove in 
mergeStepIntoSingle[#2209]

changeset:   8430:3f26fac74227
branch:  opensaf-5.1.x
parent:  8427:bff64f77344b
user:Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Mon Dec 12 11:06:08 2016 +0530
summary: smf:Allow optimization at node level forAddRemove in 
mergeStepIntoSingle[#2209]

changeset:   8431:22a441efda14
tag: tip
parent:  8428:140770d51110
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Mon Dec 12 11:06:08 2016 +0530
summary: smf:Allow optimization at node level forAddRemove in 
mergeStepIntoSingle[#2209]





---

** [tickets:#2209] SMF: ONE-STEP upgrade failed due to duplicated entities in 
AU/DU**

**Status:** fixed
**Milestone:** 5.1.1
**Created:** Mon Nov 28, 2016 07:01 AM UTC by Tai Dinh
**Last Updated:** Fri Dec 02, 2016 12:31 PM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[one_step_upgrade_fix.patch](https://sourceforge.net/p/opensaf/tickets/2209/attachment/one_step_upgrade_fix.patch)
 (3.0 kB; application/octet-stream)


Execution of ONE-STEP upgrade will fail if the original campaign contains 
forAddRemove Single Step procedure that have duplicated entities with another 
procedure.

Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO STEP: Lock deactivation units
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO createNodeGroup: saImmOmCcbApply() 
Fail 'SA_AIS_ERR_FAILED_OPERATION (21)'
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO changeNodeGroupAdminState: 
createNodeGroup() Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO lock: changeNodeGroupAdminState() 
Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Failed to Lock deactivation units in 
step=safSmfStep=0001
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step execution failed, Try undoing 
the step
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO SmfStepStateUndoing::execute start 
undoing step.
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Rollback of cluster reboot activate 
step is not implemented
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step undoing failed
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO Step safSmfStep=0001 in procedure 
safSmfProc=SmfSSMergedProc failed, step result 5
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO CAMP: Procedure 
safSmfProc=SmfSSMergedProc returned FAILED
Nov 26 18:30:11 SC-2-2 osafsmfd[4929]: ER Failed to rollback campaign, wrong 
state 10

The reason of this is because during calculating/optimizing the AU/DU of the 
merged procedure, the original AU/DU of that single step procedure is always 
appended into the result procedure without checking for duplicated entities.

This need to be fixed by removing any duplicated entities that is already 
presented in the tmpDU before optimization.

See attachment for a proposed fix.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #1956 IMM: AugmentCcbInitialize crashed when called inside completed callback

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8426:e44bf1a904b6
branch:  opensaf-5.0.x
parent:  8423:a85ab2a8baa4
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Mon Dec 12 10:27:44 2016 +0530
summary: imm:allow augumentCcbInit with ROF as false in completed 
callback[#1956]

changeset:   8427:bff64f77344b
branch:  opensaf-5.1.x
parent:  8424:962b79041a18
user:Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Mon Dec 12 10:27:44 2016 +0530
summary: imm:allow augumentCcbInit with ROF as false in completed 
callback[#1956]

changeset:   8428:140770d51110
tag: tip
parent:  8425:cf977e804025
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Mon Dec 12 10:27:44 2016 +0530
summary: imm:allow augumentCcbInit with ROF as false in completed 
callback[#1956]




---

** [tickets:#1956] IMM: AugmentCcbInitialize crashed when called inside 
completed callback**

**Status:** fixed
**Milestone:** 5.0.2
**Created:** Wed Aug 17, 2016 12:22 PM UTC by Chani Srivastava
**Last Updated:** Fri Nov 18, 2016 02:55 PM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[AugInit.7z](https://sourceforge.net/p/opensaf/tickets/1956/attachment/AugInit.7z)
 (1.3 MB; application/octet-stream)


Opensaf Version 5.0
immnd traces and coredump attached

###0  0x7fa056226b55 in raise () from /lib64/libc.so.6
###1  0x7fa056228131 in abort () from /lib64/libc.so.6
###2  0x7fa0559ac08e in getAdmoName () from /usr/lib64/libSaImmOi.so.0
###3  0x7fa0559acb48 in saImmOiAugmentCcbInitialize () from 
/usr/lib64/libSaImmOi.so.0
###4  0x7fa055fda86f in _wrap_saImmOiAugmentCcbInitialize () at 
saImmOiA211_wrap.c:5917
###5  0x00418243 in PyObject_Call (func=0x4d8f, arg=0x4d8f, kw=0x6) at 
Objects/abstract.c:1860
###6  0x00487437 in ext_do_call (nk=, na=, flags=, pp_stack=, func=)
at Python/ceval.c:3846




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2209 SMF: ONE-STEP upgrade failed due to duplicated entities in AU/DU

[Neelakanta Reddy]

https://sourceforge.net/p/opensaf/mailman/message/35527389/


---

** [tickets:#2209] SMF: ONE-STEP upgrade failed due to duplicated entities in 
AU/DU**

**Status:** review
**Milestone:** 5.1.1
**Created:** Mon Nov 28, 2016 07:01 AM UTC by Tai Dinh
**Last Updated:** Fri Dec 02, 2016 10:53 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[one_step_upgrade_fix.patch](https://sourceforge.net/p/opensaf/tickets/2209/attachment/one_step_upgrade_fix.patch)
 (3.0 kB; application/octet-stream)


Execution of ONE-STEP upgrade will fail if the original campaign contains 
forAddRemove Single Step procedure that have duplicated entities with another 
procedure.

Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO STEP: Lock deactivation units
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO createNodeGroup: saImmOmCcbApply() 
Fail 'SA_AIS_ERR_FAILED_OPERATION (21)'
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO changeNodeGroupAdminState: 
createNodeGroup() Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO lock: changeNodeGroupAdminState() 
Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Failed to Lock deactivation units in 
step=safSmfStep=0001
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step execution failed, Try undoing 
the step
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO SmfStepStateUndoing::execute start 
undoing step.
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Rollback of cluster reboot activate 
step is not implemented
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step undoing failed
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO Step safSmfStep=0001 in procedure 
safSmfProc=SmfSSMergedProc failed, step result 5
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO CAMP: Procedure 
safSmfProc=SmfSSMergedProc returned FAILED
Nov 26 18:30:11 SC-2-2 osafsmfd[4929]: ER Failed to rollback campaign, wrong 
state 10

The reason of this is because during calculating/optimizing the AU/DU of the 
merged procedure, the original AU/DU of that single step procedure is always 
appended into the result procedure without checking for duplicated entities.

This need to be fixed by removing any duplicated entities that is already 
presented in the tmpDU before optimization.

See attachment for a proposed fix.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2209 SMF: ONE-STEP upgrade failed due to duplicated entities in AU/DU

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2209] SMF: ONE-STEP upgrade failed due to duplicated entities in 
AU/DU**

**Status:** review
**Milestone:** 5.1.1
**Created:** Mon Nov 28, 2016 07:01 AM UTC by Tai Dinh
**Last Updated:** Fri Dec 02, 2016 10:15 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[one_step_upgrade_fix.patch](https://sourceforge.net/p/opensaf/tickets/2209/attachment/one_step_upgrade_fix.patch)
 (3.0 kB; application/octet-stream)


Execution of ONE-STEP upgrade will fail if the original campaign contains 
forAddRemove Single Step procedure that have duplicated entities with another 
procedure.

Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO STEP: Lock deactivation units
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO createNodeGroup: saImmOmCcbApply() 
Fail 'SA_AIS_ERR_FAILED_OPERATION (21)'
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO changeNodeGroupAdminState: 
createNodeGroup() Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO lock: changeNodeGroupAdminState() 
Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Failed to Lock deactivation units in 
step=safSmfStep=0001
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step execution failed, Try undoing 
the step
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO SmfStepStateUndoing::execute start 
undoing step.
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Rollback of cluster reboot activate 
step is not implemented
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step undoing failed
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO Step safSmfStep=0001 in procedure 
safSmfProc=SmfSSMergedProc failed, step result 5
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO CAMP: Procedure 
safSmfProc=SmfSSMergedProc returned FAILED
Nov 26 18:30:11 SC-2-2 osafsmfd[4929]: ER Failed to rollback campaign, wrong 
state 10

The reason of this is because during calculating/optimizing the AU/DU of the 
merged procedure, the original AU/DU of that single step procedure is always 
appended into the result procedure without checking for duplicated entities.

This need to be fixed by removing any duplicated entities that is already 
presented in the tmpDU before optimization.

See attachment for a proposed fix.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2209 SMF: ONE-STEP upgrade failed due to duplicated entities in AU/DU

[Neelakanta Reddy]

For the ONE STEP Upgrade, while mergeStepIntoSingleStep, 

If the campaign has singlestep procedure with AddRemove AU/DU at node level. 
The the node level AU/DU can be optimized with other rolling/formodify 
proceduers Because node will never be optimized away.

But AU/DU  at SU/Comp will not be optimized for AddRemove and will be As is 
Because there is a chance that Su/comp can be removed if they are in the scope 
of the node/Su.


---

** [tickets:#2209] SMF: ONE-STEP upgrade failed due to duplicated entities in 
AU/DU**

**Status:** accepted
**Milestone:** 5.1.1
**Created:** Mon Nov 28, 2016 07:01 AM UTC by Tai Dinh
**Last Updated:** Fri Dec 02, 2016 02:33 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[one_step_upgrade_fix.patch](https://sourceforge.net/p/opensaf/tickets/2209/attachment/one_step_upgrade_fix.patch)
 (3.0 kB; application/octet-stream)


Execution of ONE-STEP upgrade will fail if the original campaign contains 
forAddRemove Single Step procedure that have duplicated entities with another 
procedure.

Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO STEP: Lock deactivation units
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO createNodeGroup: saImmOmCcbApply() 
Fail 'SA_AIS_ERR_FAILED_OPERATION (21)'
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO changeNodeGroupAdminState: 
createNodeGroup() Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO lock: changeNodeGroupAdminState() 
Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Failed to Lock deactivation units in 
step=safSmfStep=0001
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step execution failed, Try undoing 
the step
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO SmfStepStateUndoing::execute start 
undoing step.
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Rollback of cluster reboot activate 
step is not implemented
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step undoing failed
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO Step safSmfStep=0001 in procedure 
safSmfProc=SmfSSMergedProc failed, step result 5
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO CAMP: Procedure 
safSmfProc=SmfSSMergedProc returned FAILED
Nov 26 18:30:11 SC-2-2 osafsmfd[4929]: ER Failed to rollback campaign, wrong 
state 10

The reason of this is because during calculating/optimizing the AU/DU of the 
merged procedure, the original AU/DU of that single step procedure is always 
appended into the result procedure without checking for duplicated entities.

This need to be fixed by removing any duplicated entities that is already 
presented in the tmpDU before optimization.

See attachment for a proposed fix.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2209 SMF: ONE-STEP upgrade failed due to duplicated entities in AU/DU

[Neelakanta Reddy]

Hi Tai,

can you share the campaign

Thanks,
Neel.


---

** [tickets:#2209] SMF: ONE-STEP upgrade failed due to duplicated entities in 
AU/DU**

**Status:** accepted
**Milestone:** 5.1.1
**Created:** Mon Nov 28, 2016 07:01 AM UTC by Tai Dinh
**Last Updated:** Thu Dec 01, 2016 07:06 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[one_step_upgrade_fix.patch](https://sourceforge.net/p/opensaf/tickets/2209/attachment/one_step_upgrade_fix.patch)
 (3.0 kB; application/octet-stream)


Execution of ONE-STEP upgrade will fail if the original campaign contains 
forAddRemove Single Step procedure that have duplicated entities with another 
procedure.

Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO STEP: Lock deactivation units
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO createNodeGroup: saImmOmCcbApply() 
Fail 'SA_AIS_ERR_FAILED_OPERATION (21)'
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO changeNodeGroupAdminState: 
createNodeGroup() Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO lock: changeNodeGroupAdminState() 
Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Failed to Lock deactivation units in 
step=safSmfStep=0001
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step execution failed, Try undoing 
the step
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO SmfStepStateUndoing::execute start 
undoing step.
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Rollback of cluster reboot activate 
step is not implemented
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step undoing failed
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO Step safSmfStep=0001 in procedure 
safSmfProc=SmfSSMergedProc failed, step result 5
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO CAMP: Procedure 
safSmfProc=SmfSSMergedProc returned FAILED
Nov 26 18:30:11 SC-2-2 osafsmfd[4929]: ER Failed to rollback campaign, wrong 
state 10

The reason of this is because during calculating/optimizing the AU/DU of the 
merged procedure, the original AU/DU of that single step procedure is always 
appended into the result procedure without checking for duplicated entities.

This need to be fixed by removing any duplicated entities that is already 
presented in the tmpDU before optimization.

See attachment for a proposed fix.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2211 SMF: Unnecessary sleep during callAdminOperation causes too much traffic outage during upgrade

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8398:bc37759532ea
branch:  opensaf-5.0.x
parent:  8384:441994664aec
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Thu Dec 01 16:36:33 2016 +0530
summary: smf: Avoid unconditional sleep when calling adminoperation[#2211]

changeset:   8399:c493dfa77eab
branch:  opensaf-5.1.x
parent:  8396:7c92427bfd93
user:Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Thu Dec 01 16:36:33 2016 +0530
summary: smf: Avoid unconditional sleep when calling adminoperation[#2211]

changeset:   8400:8fa2efee5365
tag: tip
parent:  8397:21094b948d29
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Thu Dec 01 16:36:33 2016 +0530
summary: smf: Avoid unconditional sleep when calling adminoperation[#2211]




---

** [tickets:#2211] SMF: Unnecessary sleep during callAdminOperation causes too 
much traffic outage during upgrade**

**Status:** fixed
**Milestone:** 5.2.FC
**Created:** Wed Nov 30, 2016 06:17 AM UTC by Tai Dinh
**Last Updated:** Wed Nov 30, 2016 07:53 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[smfd_unnecessary_sleep.patch](https://sourceforge.net/p/opensaf/tickets/2211/attachment/smfd_unnecessary_sleep.patch)
 (1.1 kB; application/octet-stream)


SmfImmUtils::callAdminOperation currently has a 2 seconds sleep at the end of 
each admin operation.
The initial purpose of this is to provdie a short breath for the system before 
retrying again on the failure case.

But unconditional sleep also slowdown the function call lead to longer time for 
the service to be up.

In case of single step campaign, where the service is only activated at 
procWrapup action, if we have about 300 SUs then we'll have more 20 minutes 
servcie outage which is not acceptable.

Sleep should only be done at retry.

See attached patch for more information.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2209 SMF: ONE-STEP upgrade failed due to duplicated entities in AU/DU

[Neelakanta Reddy]

Hi Tai,

Does your campaign for ForAddRemove has only AU/DU an node leve or SU/comp 
level also?
can you share the campaign?

Thanks,
Neel.



---

** [tickets:#2209] SMF: ONE-STEP upgrade failed due to duplicated entities in 
AU/DU**

**Status:** accepted
**Milestone:** 5.1.1
**Created:** Mon Nov 28, 2016 07:01 AM UTC by Tai Dinh
**Last Updated:** Thu Dec 01, 2016 05:23 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[one_step_upgrade_fix.patch](https://sourceforge.net/p/opensaf/tickets/2209/attachment/one_step_upgrade_fix.patch)
 (3.0 kB; application/octet-stream)


Execution of ONE-STEP upgrade will fail if the original campaign contains 
forAddRemove Single Step procedure that have duplicated entities with another 
procedure.

Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO STEP: Lock deactivation units
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO createNodeGroup: saImmOmCcbApply() 
Fail 'SA_AIS_ERR_FAILED_OPERATION (21)'
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO changeNodeGroupAdminState: 
createNodeGroup() Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO lock: changeNodeGroupAdminState() 
Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Failed to Lock deactivation units in 
step=safSmfStep=0001
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step execution failed, Try undoing 
the step
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO SmfStepStateUndoing::execute start 
undoing step.
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Rollback of cluster reboot activate 
step is not implemented
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step undoing failed
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO Step safSmfStep=0001 in procedure 
safSmfProc=SmfSSMergedProc failed, step result 5
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO CAMP: Procedure 
safSmfProc=SmfSSMergedProc returned FAILED
Nov 26 18:30:11 SC-2-2 osafsmfd[4929]: ER Failed to rollback campaign, wrong 
state 10

The reason of this is because during calculating/optimizing the AU/DU of the 
merged procedure, the original AU/DU of that single step procedure is always 
appended into the result procedure without checking for duplicated entities.

This need to be fixed by removing any duplicated entities that is already 
presented in the tmpDU before optimization.

See attachment for a proposed fix.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2209 SMF: ONE-STEP upgrade failed due to duplicated entities in AU/DU

[Neelakanta Reddy]

- **status**: unassigned --> accepted
- **assigned_to**: Neelakanta Reddy



---

** [tickets:#2209] SMF: ONE-STEP upgrade failed due to duplicated entities in 
AU/DU**

**Status:** accepted
**Milestone:** 5.1.1
**Created:** Mon Nov 28, 2016 07:01 AM UTC by Tai Dinh
**Last Updated:** Wed Nov 30, 2016 09:07 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[one_step_upgrade_fix.patch](https://sourceforge.net/p/opensaf/tickets/2209/attachment/one_step_upgrade_fix.patch)
 (3.0 kB; application/octet-stream)


Execution of ONE-STEP upgrade will fail if the original campaign contains 
forAddRemove Single Step procedure that have duplicated entities with another 
procedure.

Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO STEP: Lock deactivation units
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO createNodeGroup: saImmOmCcbApply() 
Fail 'SA_AIS_ERR_FAILED_OPERATION (21)'
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO changeNodeGroupAdminState: 
createNodeGroup() Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO lock: changeNodeGroupAdminState() 
Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Failed to Lock deactivation units in 
step=safSmfStep=0001
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step execution failed, Try undoing 
the step
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO SmfStepStateUndoing::execute start 
undoing step.
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Rollback of cluster reboot activate 
step is not implemented
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step undoing failed
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO Step safSmfStep=0001 in procedure 
safSmfProc=SmfSSMergedProc failed, step result 5
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO CAMP: Procedure 
safSmfProc=SmfSSMergedProc returned FAILED
Nov 26 18:30:11 SC-2-2 osafsmfd[4929]: ER Failed to rollback campaign, wrong 
state 10

The reason of this is because during calculating/optimizing the AU/DU of the 
merged procedure, the original AU/DU of that single step procedure is always 
appended into the result procedure without checking for duplicated entities.

This need to be fixed by removing any duplicated entities that is already 
presented in the tmpDU before optimization.

See attachment for a proposed fix.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2212 smf: avoid unpredictable timeout for adminoperations

[Neelakanta Reddy]

---

** [tickets:#2212] smf: avoid unpredictable timeout for adminoperations**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Thu Dec 01, 2016 05:06 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Dec 01, 2016 05:06 AM UTC
**Owner:** Neelakanta Reddy


SmfImmUtils AdminOperation can be changed to avoid unpredictable timeout 
similar to adminoperation in nodegroup.

call the nodegroup adminoperation using SmfImmUtils




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2211 SMF: Unnecessary sleep during callAdminOperation causes too much traffic outage during upgrade

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2211] SMF: Unnecessary sleep during callAdminOperation causes too 
much traffic outage during upgrade**

**Status:** review
**Milestone:** 5.2.FC
**Created:** Wed Nov 30, 2016 06:17 AM UTC by Tai Dinh
**Last Updated:** Wed Nov 30, 2016 07:05 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[smfd_unnecessary_sleep.patch](https://sourceforge.net/p/opensaf/tickets/2211/attachment/smfd_unnecessary_sleep.patch)
 (1.1 kB; application/octet-stream)


SmfImmUtils::callAdminOperation currently has a 2 seconds sleep at the end of 
each admin operation.
The initial purpose of this is to provdie a short breath for the system before 
retrying again on the failure case.

But unconditional sleep also slowdown the function call lead to longer time for 
the service to be up.

In case of single step campaign, where the service is only activated at 
procWrapup action, if we have about 300 SUs then we'll have more 20 minutes 
servcie outage which is not acceptable.

Sleep should only be done at retry.

See attached patch for more information.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2211 SMF: Unnecessary sleep during callAdminOperation causes too much traffic outage during upgrade

[Neelakanta Reddy]

- **status**: unassigned --> accepted
- **assigned_to**: Neelakanta Reddy



---

** [tickets:#2211] SMF: Unnecessary sleep during callAdminOperation causes too 
much traffic outage during upgrade**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Wed Nov 30, 2016 06:17 AM UTC by Tai Dinh
**Last Updated:** Wed Nov 30, 2016 06:29 AM UTC
**Owner:** Neelakanta Reddy
**Attachments:**

- 
[smfd_unnecessary_sleep.patch](https://sourceforge.net/p/opensaf/tickets/2211/attachment/smfd_unnecessary_sleep.patch)
 (1.1 kB; application/octet-stream)


SmfImmUtils::callAdminOperation currently has a 2 seconds sleep at the end of 
each admin operation.
The initial purpose of this is to provdie a short breath for the system before 
retrying again on the failure case.

But unconditional sleep also slowdown the function call lead to longer time for 
the service to be up.

In case of single step campaign, where the service is only activated at 
procWrapup action, if we have about 300 SUs then we'll have more 20 minutes 
servcie outage which is not acceptable.

Sleep should only be done at retry.

See attached patch for more information.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2209 SMF: ONE-STEP upgrade failed due to duplicated entities in AU/DU

[Neelakanta Reddy]

- **Comment**:

The reason for AddRemove not included as a part of optimization because they 
are not symmetric compared to rolling and for Modify.



---

** [tickets:#2209] SMF: ONE-STEP upgrade failed due to duplicated entities in 
AU/DU**

**Status:** unassigned
**Milestone:** 5.1.1
**Created:** Mon Nov 28, 2016 07:01 AM UTC by Tai Dinh
**Last Updated:** Mon Nov 28, 2016 11:32 AM UTC
**Owner:** nobody
**Attachments:**

- 
[one_step_upgrade_fix.patch](https://sourceforge.net/p/opensaf/tickets/2209/attachment/one_step_upgrade_fix.patch)
 (3.0 kB; application/octet-stream)


Execution of ONE-STEP upgrade will fail if the original campaign contains 
forAddRemove Single Step procedure that have duplicated entities with another 
procedure.

Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO STEP: Lock deactivation units
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO createNodeGroup: saImmOmCcbApply() 
Fail 'SA_AIS_ERR_FAILED_OPERATION (21)'
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO changeNodeGroupAdminState: 
createNodeGroup() Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO lock: changeNodeGroupAdminState() 
Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Failed to Lock deactivation units in 
step=safSmfStep=0001
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step execution failed, Try undoing 
the step
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO SmfStepStateUndoing::execute start 
undoing step.
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Rollback of cluster reboot activate 
step is not implemented
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step undoing failed
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO Step safSmfStep=0001 in procedure 
safSmfProc=SmfSSMergedProc failed, step result 5
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO CAMP: Procedure 
safSmfProc=SmfSSMergedProc returned FAILED
Nov 26 18:30:11 SC-2-2 osafsmfd[4929]: ER Failed to rollback campaign, wrong 
state 10

The reason of this is because during calculating/optimizing the AU/DU of the 
merged procedure, the original AU/DU of that single step procedure is always 
appended into the result procedure without checking for duplicated entities.

This need to be fixed by removing any duplicated entities that is already 
presented in the tmpDU before optimization.

See attachment for a proposed fix.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2209 SMF: ONE-STEP upgrade failed due to duplicated entities in AU/DU

[Neelakanta Reddy]

Hi Tai,

The patch looks good,
But in The SMF PR document The following has been 

For rolling and single step/forModify procedures:
-all deactivation units (DU) will be collected and redundant and overlapping 
DU's will be 
 removed e.g. an SU from one procedure which is within a node from another 
procedure 
 will be removed.
-deactivation/activation units (DU/AU) are symmetrical i.e. DU will also be 
used as AU.
For single step/forAddRemove procedures:
- DU/AU will be used as specified in the original procedure.


---

** [tickets:#2209] SMF: ONE-STEP upgrade failed due to duplicated entities in 
AU/DU**

**Status:** unassigned
**Milestone:** 5.1.1
**Created:** Mon Nov 28, 2016 07:01 AM UTC by Tai Dinh
**Last Updated:** Mon Nov 28, 2016 07:01 AM UTC
**Owner:** nobody
**Attachments:**

- 
[one_step_upgrade_fix.patch](https://sourceforge.net/p/opensaf/tickets/2209/attachment/one_step_upgrade_fix.patch)
 (3.0 kB; application/octet-stream)


Execution of ONE-STEP upgrade will fail if the original campaign contains 
forAddRemove Single Step procedure that have duplicated entities with another 
procedure.

Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO STEP: Lock deactivation units
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO createNodeGroup: saImmOmCcbApply() 
Fail 'SA_AIS_ERR_FAILED_OPERATION (21)'
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO changeNodeGroupAdminState: 
createNodeGroup() Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO lock: changeNodeGroupAdminState() 
Fail SA_AIS_ERR_FAILED_OPERATION (21)
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Failed to Lock deactivation units in 
step=safSmfStep=0001
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step execution failed, Try undoing 
the step
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO SmfStepStateUndoing::execute start 
undoing step.
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Rollback of cluster reboot activate 
step is not implemented
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: ER Step undoing failed
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO Step safSmfStep=0001 in procedure 
safSmfProc=SmfSSMergedProc failed, step result 5
Nov 26 18:30:02 SC-2-2 osafsmfd[4929]: NO CAMP: Procedure 
safSmfProc=SmfSSMergedProc returned FAILED
Nov 26 18:30:11 SC-2-2 osafsmfd[4929]: ER Failed to rollback campaign, wrong 
state 10

The reason of this is because during calculating/optimizing the AU/DU of the 
merged procedure, the original AU/DU of that single step procedure is always 
appended into the result procedure without checking for duplicated entities.

This need to be fixed by removing any duplicated entities that is already 
presented in the tmpDU before optimization.

See attachment for a proposed fix.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2195 imm: avoid flooding of syslog when default_removed flag is set

[Neelakanta Reddy]

changeset:   8345:f13d30b21ff1
branch:  opensaf-5.0.x
parent:  8342:7fe8f93df580
user:Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Nov 22 18:01:42 2016 +0530
summary: imm: update README, regarding convertion of notice to trace[#2195]

changeset:   8346:d9fb3328bfe4
branch:  opensaf-5.1.x
parent:  8343:1b47c5041e28
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Nov 22 18:01:42 2016 +0530
summary: imm: update README, regarding convertion of notice to trace[#2195]

changeset:   8347:3349f08887c3
tag: tip
parent:  8344:ffea60ac35cd
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Nov 22 18:01:42 2016 +0530
summary: imm: update README, regarding convertion of notice to trace[#2195]



---

** [tickets:#2195] imm: avoid flooding of syslog  when default_removed flag is 
set**

**Status:** fixed
**Milestone:** 5.0.2
**Created:** Tue Nov 22, 2016 09:48 AM UTC by Neelakanta Reddy
**Last Updated:** Tue Nov 22, 2016 12:23 PM UTC
**Owner:** Neelakanta Reddy


At the time of loading when attribute has SA_IMM_ATTR_DEFAULT_REMOVED, then the 
syslog will be flodded with the message 

LOG_NO("Attribute %s has a removed default, the value will be empty"

This has to be coverted to trace




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2195 imm: avoid flooding of syslog when default_removed flag is set

[Neelakanta Reddy]

- **status**: review --> fixed
- **Comment**:

changeset:   8342:7fe8f93df580
branch:  opensaf-5.0.x
parent:  8339:179800b55bf2
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Nov 22 17:48:14 2016 +0530
summary: imm:converted notice to trace when default_removed flag is set at 
the time of loading to avoid flooding[#2195]

changeset:   8343:1b47c5041e28
branch:  opensaf-5.1.x
parent:  8340:0f85e60fcc44
user:Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Nov 22 17:48:14 2016 +0530
summary: imm:converted notice to trace when default_removed flag is set at 
the time of loading to avoid flooding[#2195]

changeset:   8344:ffea60ac35cd
tag: tip
parent:  8341:c25afc13baf0
user:    Neelakanta Reddy <reddy.neelaka...@oracle.com>
date:Tue Nov 22 17:48:14 2016 +0530
summary: imm:converted notice to trace when default_removed flag is set at 
the time of loading to avoid flooding[#2195]





---

** [tickets:#2195] imm: avoid flooding of syslog  when default_removed flag is 
set**

**Status:** fixed
**Milestone:** 5.0.2
**Created:** Tue Nov 22, 2016 09:48 AM UTC by Neelakanta Reddy
**Last Updated:** Tue Nov 22, 2016 10:05 AM UTC
**Owner:** Neelakanta Reddy


At the time of loading when attribute has SA_IMM_ATTR_DEFAULT_REMOVED, then the 
syslog will be flodded with the message 

LOG_NO("Attribute %s has a removed default, the value will be empty"

This has to be coverted to trace




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2195 imm: avoid flooding of syslog when default_removed flag is set

[Neelakanta Reddy]

- **status**: accepted --> review



---

** [tickets:#2195] imm: avoid flooding of syslog  when default_removed flag is 
set**

**Status:** review
**Milestone:** 5.0.2
**Created:** Tue Nov 22, 2016 09:48 AM UTC by Neelakanta Reddy
**Last Updated:** Tue Nov 22, 2016 09:48 AM UTC
**Owner:** Neelakanta Reddy


At the time of loading when attribute has SA_IMM_ATTR_DEFAULT_REMOVED, then the 
syslog will be flodded with the message 

LOG_NO("Attribute %s has a removed default, the value will be empty"

This has to be coverted to trace




---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets