Bug 1908583: Set same additional networks on Bootstrap as Control Plane #4528
Conversation
|
/retest |
1 similar comment
|
/retest |
iamemilio
changed the title
openshift-ci-robot
added
the
bugzilla/severity-medium
|
@iamemilio: This pull request references Bugzilla bug 1908583, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 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. |
openshift-ci-robot
added
the
bugzilla/valid-bug
The bootstrap node was only being attached to the private network created by the installer, causing deployments with more advanced networking topologies that made use of the additional networking feature to fail. The bootstrap needs to be attached to the same networks as the control plane nodes in order to guarantee the install will succeed. Fixes Bug 1908583
iamemilio
force-pushed
the
bootstrap-networks-match-masters
branch
from
f5d374f
to
57d4e4d
Compare
openshift-ci-robot
added
the
do-not-merge/hold
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Fedosin 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 |
openshift-ci-robot
added
lgtm
|
/hold cancel |
openshift-ci-robot
removed
the
do-not-merge/hold
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@iamemilio: All pull requests linked via external trackers have merged: Bugzilla bug 1908583 has 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. |
|
/cherry-pick release-4.6 |
|
@iamemilio: new pull request created: #4535 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. |
|
I would have loved to see this change reflected in the user documentation. And at this point, we should also probably have the boostrap node follow the |
The bootstrap node was only being attached to the private network created by the installer,
causing deployments with more advanced networking topologies that made use of the additional
networking feature to fail. The bootstrap needs to be attached to the same networks as the
control plane nodes in order to guarantee the install will succeed.
Fixes Bug 1908583
/label platform/openstack