[tickets] [opensaf:tickets] #2919 plm: "plmtest 3 13" causing plmd to crash
- **status**: accepted --> review --- ** [tickets:#2919] plm: "plmtest 3 13" causing plmd to crash** **Status:** review **Milestone:** 5.18.08 **Created:** Mon Aug 27, 2018 08:06 PM UTC by Alex Jones **Last Updated:** Mon Aug 27, 2018 08:07 PM UTC **Owner:** Alex Jones "plmtest 3 13" causes plmd to crash. This test passes an entities pointer in saPlmReadinessTrack, but with numberOfEntities smaller than plmd would return. So, it returns ERR_NO_SPACE. But, the plm code is setting number of entities in the response with no actual entities, which is causing the EDU code to crash. --- 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] #2919 plm: "plmtest 3 13" causing plmd to crash
--- ** [tickets:#2919] plm: "plmtest 3 13" causing plmd to crash** **Status:** accepted **Milestone:** 5.18.08 **Created:** Mon Aug 27, 2018 08:06 PM UTC by Alex Jones **Last Updated:** Mon Aug 27, 2018 08:06 PM UTC **Owner:** Alex Jones "plmtest 3 13" causes plmd to crash. This test passes an entities pointer in saPlmReadinessTrack, but with numberOfEntities smaller than plmd would return. So, it returns ERR_NO_SPACE. But, the plm code is setting number of entities in the response with no actual entities, which is causing the EDU code to crash. --- 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] #592 LOG: saLogStreamPathName is not writable in stream config class
Note that security must be handled if this attribute is made writable. If the path can be changed it must be ensured it cannot be given a value outside of the allowed directory structure etc. (other security issues?) This is a relative path and the root path is given in the log configuration object (that has checks) so there should be no problem. But check to be sure. --- ** [tickets:#592] LOG: saLogStreamPathName is not writable in stream config class** **Status:** accepted **Milestone:** 5.18.08 **Created:** Thu Oct 10, 2013 01:40 PM UTC by elunlen **Last Updated:** Thu Aug 23, 2018 10:12 AM UTC **Owner:** Ratnamala In IMM model attribute saLogStreamPathName in class SaLogStreamConfig is SA_CONFIG but not SA_WRITABLE. This means that this attribute cannot be modified or error handled in the log service OI. --- 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] #2879 amf: amfnd crashes with amf-adm restart NPI comp
- **status**: review --> fixed - **Comment**: commit 1030360034e765f5f4134d58f0fef8f5c69e8739 Author: thang.nguyen Date: Tue Aug 14 17:53:06 2018 +0700 amf: remove assignment for NPI component with enable DisableRestart [#2879] --- ** [tickets:#2879] amf: amfnd crashes with amf-adm restart NPI comp** **Status:** fixed **Milestone:** 5.18.08 **Created:** Mon Jun 18, 2018 04:21 AM UTC by Thang Duc Nguyen **Last Updated:** Fri Jun 29, 2018 03:29 PM UTC **Owner:** Thang Duc Nguyen Reproduce steps 1. Deploy 2N model, NPI SU/Comp to PL-3,PL-4 with saAmfCtDefRecoveryOnError=3, saAmfCtDefDisableRestart=0. 2. Config saAmfCtDefDisableRestart=1. 3. Amf-adm restart on NPI compoent with ACTIVE assignment. 4. Core dump happen. --- 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] #2916 amfd: SU remains OUT_OF_SERVICE when unlock SU during cluster start up
[develop] commit fb4890756ebd14fbe40906d37962b9261ed9a282 Author: Minh Chau Date: Fri Aug 24 08:11:29 2018 +1000 amfd: Set SA_AMF_READINESS_IN_SERVICE for qualified SU after cluster startup timeout [#2916] [release] commit 219efe2012231fbc491b7d7c3a50221e648c771f Author: Minh Chau Date: Fri Aug 24 08:11:29 2018 +1000 amfd: Set SA_AMF_READINESS_IN_SERVICE for qualified SU after cluster startup timeout [#2916] --- ** [tickets:#2916] amfd: SU remains OUT_OF_SERVICE when unlock SU during cluster start up** **Status:** fixed **Milestone:** 5.18.08 **Created:** Tue Aug 21, 2018 11:09 PM UTC by Minh Hon Chau **Last Updated:** Mon Aug 27, 2018 06:31 AM UTC **Owner:** Minh Hon Chau The problem happens in NWay Active SUs, all SUs have the assignment, except SU in the SC-1. Scenario: It is single step upgrade, after cluter reboot, SMF will issue unlock command during cluster startup. During cluster starting up, SC-2 has already joined cluster and before the SC-1 (standby) joins the cluster, issue unlock the SUs in SC-1 and SC-2. Only SU in SC-2 becomes IN_SERVICE. 3001 2018-08-16T02:52:00.986+0200 SC-2 safApp=safAmfService NO: "Admin op "UNLOCK" initiated for 'safSu=SC-1,safSg=NWA,safApp=QWE-ABC-Amfproxy', invocation: 425201762315" 3002 2018-08-16T02:52:00.987+0200 SC-2 safApp=safAmfService NO: "safSu=SC-1,safSg=NWA,safApp=QWE-ABC-Amfproxy AdmState LOCKED => UNLOCKED" 3003 2018-08-16T02:52:00.988+0200 SC-2 safApp=safAmfService NO: "Admin op done for invocation: 425201762315, result 1" 3004 2018-08-16T02:52:00.990+0200 SC-2 safApp=safAmfService NO: "Admin op "UNLOCK" initiated for 'safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy', invocation: 429496729612" 3005 2018-08-16T02:52:00.990+0200 SC-2 safApp=safAmfService NO: "safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy AdmState LOCKED => UNLOCKED" 3006 2018-08-16T02:52:00.991+0200 SC-2 safApp=safAmfService NO: "safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy ReadinessState OUT_OF_SERVICE => IN_SERVICE" When "cluster init timeout" amfd will start assignment of all SUs 3069 2018-08-16T02:52:10.058+0200 SC-2 safApp=safAmfService NO: "Cluster startup timeout, assigning SIs to SUs" so we can see the other SUs were being assigned 3080 2018-08-16T02:52:10.129+0200 SC-2 safApp=safAmfService NO: "safSi=ABC.main-NWA-1,safApp=QWE-ABC-Amfproxy assigned to safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy HA State 'ACTIVE'" 3311 2018-08-16T02:53:55.745+0200 SC-2 safApp=safAmfService NO: "safSu=PL-4,safSg=NWA,safApp=QWE-ABC-Amfproxy PresenceState INSTANTIATING => INSTANTIATED" 3312 2018-08-16T02:53:55.745+0200 SC-2 safApp=safAmfService NO: "safSu=PL-4,safSg=NWA,safApp=QWE-ABC-Amfproxy ReadinessState OUT_OF_SERVICE => IN_SERVICE" 3313 2018-08-16T02:53:55.750+0200 SC-2 safApp=safAmfService NO: "safSi=ABC.main-NWA-1,safApp=QWE-ABC-Amfproxy assigned to safSu=PL-4,safSg=NWA,safApp=QWE-ABC-Amfproxy HA State 'ACTIVE'" 3360 2018-08-16T02:54:06.555+0200 SC-2 safApp=safAmfService NO: "safSu=PL-3,safSg=NWA,safApp=QWE-ABC-Amfproxy PresenceState INSTANTIATING => INSTANTIATED" 3361 2018-08-16T02:54:06.555+0200 SC-2 safApp=safAmfService NO: "safSu=PL-3,safSg=NWA,safApp=QWE-ABC-Amfproxy ReadinessState OUT_OF_SERVICE => IN_SERVICE" 3362 2018-08-16T02:54:06.560+0200 SC-2 safApp=safAmfService NO: "safSi=ABC.main-NWA-1,safApp=QWE-ABC-Amfproxy assigned to safSu=PL-3,safSg=NWA,safApp=QWE-ABC-Amfproxy HA State 'ACTIVE'" The only SU in SC-1 is not assigned, because it is still OUT_OF_SERVICE The unlock command does not get the SU IN_SERVICE, because node SC-1 is still DISABLED. --- 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] #2916 amfd: SU remains OUT_OF_SERVICE when unlock SU during cluster start up
Can you please update the ticket with the change sets? --- ** [tickets:#2916] amfd: SU remains OUT_OF_SERVICE when unlock SU during cluster start up** **Status:** fixed **Milestone:** 5.18.08 **Created:** Tue Aug 21, 2018 11:09 PM UTC by Minh Hon Chau **Last Updated:** Thu Aug 23, 2018 10:16 PM UTC **Owner:** Minh Hon Chau The problem happens in NWay Active SUs, all SUs have the assignment, except SU in the SC-1. Scenario: It is single step upgrade, after cluter reboot, SMF will issue unlock command during cluster startup. During cluster starting up, SC-2 has already joined cluster and before the SC-1 (standby) joins the cluster, issue unlock the SUs in SC-1 and SC-2. Only SU in SC-2 becomes IN_SERVICE. 3001 2018-08-16T02:52:00.986+0200 SC-2 safApp=safAmfService NO: "Admin op "UNLOCK" initiated for 'safSu=SC-1,safSg=NWA,safApp=QWE-ABC-Amfproxy', invocation: 425201762315" 3002 2018-08-16T02:52:00.987+0200 SC-2 safApp=safAmfService NO: "safSu=SC-1,safSg=NWA,safApp=QWE-ABC-Amfproxy AdmState LOCKED => UNLOCKED" 3003 2018-08-16T02:52:00.988+0200 SC-2 safApp=safAmfService NO: "Admin op done for invocation: 425201762315, result 1" 3004 2018-08-16T02:52:00.990+0200 SC-2 safApp=safAmfService NO: "Admin op "UNLOCK" initiated for 'safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy', invocation: 429496729612" 3005 2018-08-16T02:52:00.990+0200 SC-2 safApp=safAmfService NO: "safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy AdmState LOCKED => UNLOCKED" 3006 2018-08-16T02:52:00.991+0200 SC-2 safApp=safAmfService NO: "safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy ReadinessState OUT_OF_SERVICE => IN_SERVICE" When "cluster init timeout" amfd will start assignment of all SUs 3069 2018-08-16T02:52:10.058+0200 SC-2 safApp=safAmfService NO: "Cluster startup timeout, assigning SIs to SUs" so we can see the other SUs were being assigned 3080 2018-08-16T02:52:10.129+0200 SC-2 safApp=safAmfService NO: "safSi=ABC.main-NWA-1,safApp=QWE-ABC-Amfproxy assigned to safSu=SC-2,safSg=NWA,safApp=QWE-ABC-Amfproxy HA State 'ACTIVE'" 3311 2018-08-16T02:53:55.745+0200 SC-2 safApp=safAmfService NO: "safSu=PL-4,safSg=NWA,safApp=QWE-ABC-Amfproxy PresenceState INSTANTIATING => INSTANTIATED" 3312 2018-08-16T02:53:55.745+0200 SC-2 safApp=safAmfService NO: "safSu=PL-4,safSg=NWA,safApp=QWE-ABC-Amfproxy ReadinessState OUT_OF_SERVICE => IN_SERVICE" 3313 2018-08-16T02:53:55.750+0200 SC-2 safApp=safAmfService NO: "safSi=ABC.main-NWA-1,safApp=QWE-ABC-Amfproxy assigned to safSu=PL-4,safSg=NWA,safApp=QWE-ABC-Amfproxy HA State 'ACTIVE'" 3360 2018-08-16T02:54:06.555+0200 SC-2 safApp=safAmfService NO: "safSu=PL-3,safSg=NWA,safApp=QWE-ABC-Amfproxy PresenceState INSTANTIATING => INSTANTIATED" 3361 2018-08-16T02:54:06.555+0200 SC-2 safApp=safAmfService NO: "safSu=PL-3,safSg=NWA,safApp=QWE-ABC-Amfproxy ReadinessState OUT_OF_SERVICE => IN_SERVICE" 3362 2018-08-16T02:54:06.560+0200 SC-2 safApp=safAmfService NO: "safSi=ABC.main-NWA-1,safApp=QWE-ABC-Amfproxy assigned to safSu=PL-3,safSg=NWA,safApp=QWE-ABC-Amfproxy HA State 'ACTIVE'" The only SU in SC-1 is not assigned, because it is still OUT_OF_SERVICE The unlock command does not get the SU IN_SERVICE, because node SC-1 is still DISABLED. --- 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
