[tickets] [opensaf:tickets] #1991 AMF: Existing PG tracking should not be stopped for CURRENT flag
- **status**: review --> fixed - **assigned_to**: Long HB Nguyen --> nobody - **Comment**: changeset: 8097:b6faa36cf2ce tag: tip parent: 8095:06794cdbd3ee user:Long Nguyen date:Tue Sep 20 11:54:58 2016 +1000 summary: amfa: fix saAmfProtectionGroupTrackStop [#1991] changeset: 8096:f6760a2e9c76 branch: opensaf-5.1.x parent: 8094:6e6980f88b50 user:Long Nguyen date:Tue Sep 20 11:53:55 2016 +1000 summary: amfa: fix saAmfProtectionGroupTrackStop [#1991] --- ** [tickets:#1991] AMF: Existing PG tracking should not be stopped for CURRENT flag** **Status:** fixed **Milestone:** 5.1.RC2 **Created:** Wed Aug 31, 2016 09:44 AM UTC by Srikanth R **Last Updated:** Fri Sep 16, 2016 02:14 AM UTC **Owner:** nobody 5.1.FC : changeset - 6997 Issue : Existing PG tracking should not be stopped for CURRENT call Steps performed : -> Call saAmfInitialize_4() -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag. -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CHANGES flag. -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag. -> Call saAmfProtectionGroupTrackStop() Observed output : TrackStop returns ERR_NOT_EXIST, indicating that tracking is not started earlier. Expected output: TrackStop() api should return SA_AIS_OK and in the earlier release, api is returning SA_AIS_OK. According to the B04.01 spec 7.11.1 page 318 , Tracking should not be stopped untill TrackStop() is called explicitly. Once saAmfProtectionGroupTrack_4() has been called with trackFlags containing either SA_TRACK_CHANGES or SA_TRACK_CHANGES_ONLY, notification callbacks can only be stopped by an invocation of saAmfProtectionGroupTrackStop(). --- 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] #1991 AMF: Existing PG tracking should not be stopped for CURRENT flag
- **status**: accepted --> review --- ** [tickets:#1991] AMF: Existing PG tracking should not be stopped for CURRENT flag** **Status:** review **Milestone:** 5.1.RC2 **Created:** Wed Aug 31, 2016 09:44 AM UTC by Srikanth R **Last Updated:** Wed Sep 14, 2016 04:32 AM UTC **Owner:** Long HB Nguyen 5.1.FC : changeset - 6997 Issue : Existing PG tracking should not be stopped for CURRENT call Steps performed : -> Call saAmfInitialize_4() -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag. -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CHANGES flag. -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag. -> Call saAmfProtectionGroupTrackStop() Observed output : TrackStop returns ERR_NOT_EXIST, indicating that tracking is not started earlier. Expected output: TrackStop() api should return SA_AIS_OK and in the earlier release, api is returning SA_AIS_OK. According to the B04.01 spec 7.11.1 page 318 , Tracking should not be stopped untill TrackStop() is called explicitly. Once saAmfProtectionGroupTrack_4() has been called with trackFlags containing either SA_TRACK_CHANGES or SA_TRACK_CHANGES_ONLY, notification callbacks can only be stopped by an invocation of saAmfProtectionGroupTrackStop(). --- 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] #1991 AMF: Existing PG tracking should not be stopped for CURRENT flag
- **status**: unassigned --> accepted - **assigned_to**: Long HB Nguyen --- ** [tickets:#1991] AMF: Existing PG tracking should not be stopped for CURRENT flag** **Status:** accepted **Milestone:** 5.1.RC2 **Created:** Wed Aug 31, 2016 09:44 AM UTC by Srikanth R **Last Updated:** Tue Sep 13, 2016 10:09 AM UTC **Owner:** Long HB Nguyen 5.1.FC : changeset - 6997 Issue : Existing PG tracking should not be stopped for CURRENT call Steps performed : -> Call saAmfInitialize_4() -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag. -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CHANGES flag. -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag. -> Call saAmfProtectionGroupTrackStop() Observed output : TrackStop returns ERR_NOT_EXIST, indicating that tracking is not started earlier. Expected output: TrackStop() api should return SA_AIS_OK and in the earlier release, api is returning SA_AIS_OK. According to the B04.01 spec 7.11.1 page 318 , Tracking should not be stopped untill TrackStop() is called explicitly. Once saAmfProtectionGroupTrack_4() has been called with trackFlags containing either SA_TRACK_CHANGES or SA_TRACK_CHANGES_ONLY, notification callbacks can only be stopped by an invocation of saAmfProtectionGroupTrackStop(). --- 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] #1991 AMF: Existing PG tracking should not be stopped for CURRENT flag
- **Milestone**: 5.1.RC1 --> 5.1.RC2 --- ** [tickets:#1991] AMF: Existing PG tracking should not be stopped for CURRENT flag** **Status:** unassigned **Milestone:** 5.1.RC2 **Created:** Wed Aug 31, 2016 09:44 AM UTC by Srikanth R **Last Updated:** Wed Aug 31, 2016 09:44 AM UTC **Owner:** nobody 5.1.FC : changeset - 6997 Issue : Existing PG tracking should not be stopped for CURRENT call Steps performed : -> Call saAmfInitialize_4() -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag. -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CHANGES flag. -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag. -> Call saAmfProtectionGroupTrackStop() Observed output : TrackStop returns ERR_NOT_EXIST, indicating that tracking is not started earlier. Expected output: TrackStop() api should return SA_AIS_OK and in the earlier release, api is returning SA_AIS_OK. According to the B04.01 spec 7.11.1 page 318 , Tracking should not be stopped untill TrackStop() is called explicitly. Once saAmfProtectionGroupTrack_4() has been called with trackFlags containing either SA_TRACK_CHANGES or SA_TRACK_CHANGES_ONLY, notification callbacks can only be stopped by an invocation of saAmfProtectionGroupTrackStop(). --- 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] #1991 AMF: Existing PG tracking should not be stopped for CURRENT flag
--- ** [tickets:#1991] AMF: Existing PG tracking should not be stopped for CURRENT flag** **Status:** unassigned **Milestone:** 5.1.RC1 **Created:** Wed Aug 31, 2016 09:44 AM UTC by Srikanth R **Last Updated:** Wed Aug 31, 2016 09:44 AM UTC **Owner:** nobody 5.1.FC : changeset - 6997 Issue : Existing PG tracking should not be stopped for CURRENT call Steps performed : -> Call saAmfInitialize_4() -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag. -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CHANGES flag. -> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag. -> Call saAmfProtectionGroupTrackStop() Observed output : TrackStop returns ERR_NOT_EXIST, indicating that tracking is not started earlier. Expected output: TrackStop() api should return SA_AIS_OK and in the earlier release, api is returning SA_AIS_OK. According to the B04.01 spec 7.11.1 page 318 , Tracking should not be stopped untill TrackStop() is called explicitly. Once saAmfProtectionGroupTrack_4() has been called with trackFlags containing either SA_TRACK_CHANGES or SA_TRACK_CHANGES_ONLY, notification callbacks can only be stopped by an invocation of saAmfProtectionGroupTrackStop(). --- 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
