-
Notifications
You must be signed in to change notification settings - Fork 1.3k
CLOUDSTACK-9151 - As a Developer I want the VRID to be set within the limits of KeepaliveD #1231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLOUDSTACK-9151 - As a Developer I want the VRID to be set within the limits of KeepaliveD #1231
Conversation
…ant file - Just like with RVRs, use the VRID 51 instead of making it dependent on the VPCID - Reason: arbitary unique number 0..255 used to differentiate multiple instances of vrrpd running on the same NIC (and hence same socket). virtual_router_id 51
|
Ping @remibergsma @DaanHoogland @borisroman Could you guys test it before the RC? I just fixed, but have to go to a concert now. |
|
Thanks for the quick fix @wilderrodrigues. Bit explanation: redundant routers worked fine in our 4.7 cloud, then all of a sudden were broken. Root cause was due to Thanks @fborn for discovering the issue! |
|
You can read the following from man keepalived.conf: Since we run only one pair of keepalived on each nic, this default is fine. |
|
LGTM, perhaps we can use VPCID % 255 to get a value that is less than 255 but greater than 0? |
|
@bhaisaab nice suggestion! Not sure if it is needed though. The vrrp is done over the first guest network, so it cannot clash with other router pairs. Other tiers are handled by the same keepalived/vrrp instance so that's also fine. I cannot think of a way it'd clash. And even when we make it 0-255, it could still clash (and be harder to spot). First testing it now to see if it resolves the issues we see. Will report back soon. |
|
Jenkins error unrelated to PR change: |
|
First test results: keepalived.conf looks as expected: Service is running: Logs: |
|
As an operator I want this in :p have only read the feature description in jira and the diff but lgtm based on that and @remibergsma his test results. |
|
@DaanHoogland Thanks. Deploying to a real cloud as we speak. Will verify there too. |
|
Update: Verified the same as above in our pre-production environment (aka Employee Cloud). Will now deploy to production as it works as expected. When the integration tests are done and show nothing broke, we will merge. |
|
Update: this resolved our production problem. It now works fine in master+this PR. LGTM 👍 |
|
LGTM 👍 Environment
Integration test suite 1 Result test suite 1 Integration test suite 2 Result test suite 2 |
CLOUDSTACK-9151 - As a Developer I want the VRID to be set within the limits of KeepaliveDThis PR fixes a blocker issue! - Just like with RVRs, use the VRID 51 instead of making it dependent on the VPCID - Reason: arbitary unique number 0..255 used to differentiate multiple instances of vrrpd running on the same NIC (and hence same socket). virtual_router_id 51 * pr/1231: CLOUDSTACK-9151 - Removes the replacement of the VRID in the CsRedundant file Signed-off-by: Remi Bergsma <github@remi.nl>
|
Thanks @DaanHoogland @remibergsma @bhaisaab and @borisroman for reacting very quickly! |

This PR fixes a blocker issue!