-
Notifications
You must be signed in to change notification settings - Fork 402
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
Bug 1871769: [baremetal] keep API VIP in the bootstrap node until the bootstrap’s node API goes away #2107
Bug 1871769: [baremetal] keep API VIP in the bootstrap node until the bootstrap’s node API goes away #2107
Conversation
yboaron
commented
Sep 21, 2020
When OPENSHIFT_INSTALL_PRESERVE_BOOTSTRAP deployment configuration parameter is set to true the bootstrap node won't be destroyed and infrastructure components including Keepalived on the bootstrap continue to run. With this PR the Keepalived process is stopped when a stop message is received in Keepalived control socket. This change is important for platforms that run Keepalived in unicast mode (baremetal).
a8e0112
to
590b0a8
Compare
/retitle [baremetal, ovirt, vsphere, openstack] keep API VIP in the bootstrap node until the bootstrap’s node API goes away |
…s away Keeping the API VIP in the bootstrap node until the bootstrap’s node API goes away eliminates the need for master nodes to specify the bootstrap as one of their peers in the unicast Keepalived case, see [1]. Additionally, it makes the deployment flow more deterministic so other components (e.g: remove requirement for provisioning static IP , see [2] ) can benefit from it. [1] https://docs.google.com/document/d/1jPIOYuK1J3PKYS8ff8waHWeHqzgl5OZeOkWngUxHtR8/edit?usp=sharing [2] https://docs.google.com/document/d/18DVr7Ikw_gSJsiQvG8zV2oBEqlG070MzyIElcK94LJI/edit#
590b0a8
to
1537a22
Compare
/retitle bug:1881053 [baremetal] keep API VIP in the bootstrap node until the bootstrap’s node API goes away |
/retitle bug 1881053: [baremetal] keep API VIP in the bootstrap node until the bootstrap’s node API goes away |
@yboaron: This pull request references Bugzilla bug 1881053, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/test e2e-metal-ipi |
/bugzilla refresh Recalculating validity in case the underlying Bugzilla bug has changed. |
@openshift-bot: This pull request references Bugzilla bug 1881053, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retitle Bug 1871769 : [baremetal] keep API VIP in the bootstrap node until the bootstrap’s node API goes away |
@yboaron: No Bugzilla bug is referenced in the title of this pull request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retitle Bug 1871769: [baremetal] keep API VIP in the bootstrap node until the bootstrap’s node API goes away |
@yboaron: An error was encountered adding this pull request to the external tracker bugs for bug 1871769 on the Bugzilla server at https://bugzilla.redhat.com:
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@yboaron: This pull request references Bugzilla bug 1871769, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cc @ericavonb Do you think we can merge this PR ? |
@ericavonb Can we merge this PR ? 10x |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bcrochet, cybertron, yboaron, yuqi-zhang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
@yboaron: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@yboaron: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Bugzilla bug 1871769 has not been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/bugzilla refresh |
@yuqi-zhang: Bugzilla bug 1871769 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |