Align the message with master plugin restoration logic

[kichankwon]

thin_entrypoint prints that it allows 45 seconds for its restoration, but it waits until "masterConfigFilePath" exists.
So, adjust the message to align with this logic.

[s1061123]

Thank you for the PR. Good catch that mismatch between comment and actual code. But I would like to know why you fix to 45sec wait, not wait forever. If we cannot find master config, then your change makes the pod quit and launch it again...

How about to change to wait forever until the master config found?

[kichankwon]

Thank you for the PR. Good catch that mismatch between comment and actual code. But I would like to know why you fix to 45sec wait, not wait forever. If we cannot find master config, then your change makes the pod quit and launch it again...

How about to change to wait forever until the master config found?

I fixed to 45 seconds wait because..

• I thought there's a mistake in the message or logic
• And I found that old shell script(images/entrypoint.sh) waits 45 seconds just before it got removed

  • multus-cni/images/entrypoint.sh

    Line 457 in c129e72

    for i in {1..35}

• So, I decided to fix the logic

But, I agree with you. So, I'm going to fix the message not the logic.

[coveralls]

coverage: 63.211% (-0.3%) from 63.468%
when pulling 4f7dce6 on kichankwon:set_timeout
into acfbd42 on k8snetworkplumbingwg:master.

[kichankwon]

@s1061123 Could you check this PR?

[kichankwon]

@s1061123 Can I ping you for a review?

[github-actions]

This pull request is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.