Bug 1878758: openstack UPI: Allow for no FIP or router#4219
Bug 1878758: openstack UPI: Allow for no FIP or router#4219openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
|
The e2e-openstack-upi job is expected to fail until I adapt the job to create a bootstrap FIP manually. May I get a review ( |
|
Looks good to me, just a couple of questions:
|
It is not. In this patch, IPI and UPI diverge a bit in that respect.
This new PR aims at narrowing the scope of the change as much as possible, and at avoiding any magic. I believe that working towards supporting the absence of an external network is the natural next step. However, I'd treat it as a separate change. WDYT? |
mandre
left a comment
There was a problem hiding this comment.
It's not clear exactly what problem we're trying to solve here.
Letting the user specify the bootstrap FIP makes some sense to me in a UPI scenario, but why forcing an external network? It's a regression from the previous implementation
d78fe40 to
3a85f15
Compare
|
@pierreprinetti: This pull request references Bugzilla bug 1878758, 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
DetailsIn 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. |
|
/label platform/openstack |
|
Made the external network optional again. Required for FIPs. FIPs can be passed on an individual basis. |
3a85f15 to
57a8ef3
Compare
|
/retest |
|
/cc @MaysaMacedo |
MaysaMacedo
left a comment
There was a problem hiding this comment.
Looks good, just a question and suggestion:
57a8ef3 to
45e8ac2
Compare
|
e2e-openstack-upi requires openshift/release#12322 |
|
/retest |
45e8ac2 to
9b9ee29
Compare
99ccd7c to
ee3f486
Compare
|
/test e2e-openstack-upi |
If the external network is not provided, the router will not be created and external connectivity will be a respopnsibility of the operator. Floating IPs will be set if available, on an individual basis. The external network is a requirement for FIPs; if not provided, the playbooks will error. The bootstrap FIP is now required to be created manually like the other FIPs.
ee3f486 to
7df6205
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mandre The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds 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. |
|
@pierreprinetti: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@pierreprinetti: All pull requests linked via external trackers have merged: Bugzilla bug 1878758 has been moved to the MODIFIED state. DetailsIn 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. |
If the external network is not provided, the router will not be created
and external connectivity will be a respopnsibility of the operator.
Floating IPs will be set if available, on an individual basis. The
external network is a requirement for FIPs; if not provided, the
playbooks will error.
The bootstrap FIP is now required to be created manually like the other
FIPs.
This is a follow-up to #3755.
/cc luis5tb adduarte iamemilio mandre