ConfigMap skupper-network-status shows incorrect linkCost after quickly deleting/recreating link with new cost

[Karen-Schoener]

Describe the bug ConfigMap skupper-network-status shows incorrect linkCost after quickly deleting/recreating link with new cost.

Test steps are basically:

• create link with default cost of 1.
• observe that linkCost in configmap skupper-network-status shows as 1 (as expected)
• delete link
• do not wait ~60 seconds for link record to age out of the skupper-network-status.
• create link with cost of 10
• observe that linkCost in configmap skupper-network-status shows as 1

How To Reproduce

Create sites: east, west

    skupper -n west init
    skupper -n east init

Link sites (with default cost):

    skupper -n west token create skupper_token_west.out
    skupper -n east link create skupper_token_west.out

In east, view configmap skupper-network-status. Observe that link cost shows as: 1

Delete link.

    skupper -n east link delete link1

Create link (with cost=10). Do not wait for link to age out of the skupper-network-status before creating link (with cost=10).

    skupper -n west token create skupper_token_west.out
    skupper -n east link create skupper_token_west.out --cost=10

In east, view configmap skupper-network-status. Observe that link cost shows as: 1

Expected behavior Expected behavior: linkCost in configmap skupper-network-status matches the configured link cost.

Environment details

• Skupper CLI: 1.8.0
• Skupper Operator (if applicable): NA
• Platform: minikube