#1991 AMF: Existing PG tracking should not be stopped for CURRENT flag

[Srikanth R]

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().

[Minh Hon Chau]

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]