Possible VRID collision? about baremetal-runtimecfg HOT 4 CLOSED

This is definitely a possibility, and it's even worse than just collisions between our three VIPs. It's possible a deployer could have keepalived running on their network already for other services and we might accidentally pick one of their existing VRIDs. Ideally we would check for ids already in use on the network when we select ours and have a consistent fallback mechanism to deal with collisions.

The check in the code should be pretty easy to write, but I'm not sure how looking for existing ids on the network would work. So far it hasn't been a big problem so we haven't prioritized solving it.

from baremetal-runtimecfg.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from baremetal-runtimecfg.

This has been fixed with #23
/close

from baremetal-runtimecfg.

@mandre: Closing this issue.

from baremetal-runtimecfg.