imm: timeout in imma_sync_with_immnd is wrong

Brought to you by: anders-w, gary_lee, hansnordeback, jonasarndt, and 3 others

#2701 imm: timeout in imma_sync_with_immnd is wrong

Milestone: never

Status: invalid

Owner: nobody

Labels: None

Type: defect

Component: imm

Part: -

Version:

Priority: major

Blocker: False

Updated: 2018-03-01

Created: 2017-11-22

Creator: Zoran Milinkovic

Private: No

In the change in the ticket #452, the timeout was increased from 3 seconds to 30 seconds by mistake.
The timeout needs to be reverted to 3 seconds.

Discussion

Anders Widell - 2018-02-02

Milestone: 5.18.01 --> 5.18.04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Vu Minh Nguyen - 2018-03-01

status: assigned --> invalid

assigned_to: Vu Minh Nguyen --> nobody

Milestone: 5.18.04 --> never
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Vu Minh Nguyen - 2018-03-01

30-second wait is there to avoid potential endless loop of TRY_AGAIN when IMMND not yet come up. Once IMMND is up, that waiting will be unlocked right away. 30-second wait is also common pattern for most of OpenSAF agents.

So, I will change the ticket to invalid.

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

Log in to post a comment.