OpenSAF / Tickets / #2587 amf: Incorrect handling of version when initializing OpenSAF APIs

#2587 amf: Incorrect handling of version when initializing OpenSAF APIs

Milestone: 5.17.11

Status: fixed

Owner: Gary Lee

Labels: None

Type: defect

Component: amf

Part: -

Version:

Priority: major

Blocker: False

Updated: 2017-10-30

Created: 2017-09-21

Creator: Gary Lee

Private: No

AMF sometimes reuses a version variable when initializing OpenSAF APIs. This means that the next time the API is initialized it may be initialized with a higher version. See #2517 for details.

Gary Lee - 2017-09-22

status: accepted --> review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gary Lee - 2017-10-04

develop:

commit c9daf4dae064f10c27fa82d15db7b7cdc3bd90ea
Author: Gary Lee gary.lee@dektech.com.au
Date: Wed Oct 4 11:04:55 2017 +1100

amf: ensure we do not reuse version when calling OpenSAF init functions [#2587]

release:

commit 4957f89607c79c41dc147b5ce3c87343b34ee105
Author: Gary Lee gary.lee@dektech.com.au
Date: Wed Oct 4 11:04:55 2017 +1100

amf: ensure we do not reuse version when calling OpenSAF init functions [#2587]
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gary Lee - 2017-10-04

status: review --> fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

amf: Incorrect handling of version when initializing OpenSAF APIs

Milestone

Searches

Help

#2587 amf: Incorrect handling of version when initializing OpenSAF APIs

Related

Discussion