Skip to content
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 2015154: Support for ports and primarySubnet fields in machine #583

Merged
merged 5 commits into from Oct 25, 2021
Merged

Conversation

ghost
Copy link

@ghost ghost commented Oct 25, 2021

No description provided.

gryf and others added 5 commits October 7, 2021 11:55
For now, by default, pod network was taken from OpenShift Machine spec,
by looking for "networks" field and get the first item out of it to
figure out right subnet. Currently there is another field, where
networks can be defined - under "ports" field, where subnet for fixed
IPs can be found. Additionally, to avoid confusion, there is another
field, which defines primary subnet for the pods - "primarySubnet".

Implementation has been adapted to reflect that change:

1. primarySubnet will be examined, to get the subnet id
2. if primarySubnet does not exists, networks field will be examined
3. if there is no networks field (or it doesn't contain subnets), ports
   field will be examined for subnet id

Change-Id: I35b6f2e6288cbe3fd80b74a5da03639d7bd0a765
We're moving this because we discovered that Octavia will not always
raise Conflict if you create an LB with the same IP.

If no VIP port got created for an LB, then Octavia will not have any
issue with creating another LB with the same IP.

Closes-Bug: 1947809

Change-Id: I26b911b30403c7ea5a35706b2fc80af499e91330
@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Oct 25, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 25, 2021

Hi @kuryr-bot. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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 openshift-ci bot requested review from gryf and luis5tb October 25, 2021 07:02
@MaysaMacedo
Copy link
Contributor

/label ok-to-test

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 25, 2021

@MaysaMacedo: The label(s) /label ok-to-test cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, backport-risk-assessed, cherry-pick-approved

In response to this:

/label ok-to-test

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.

@MaysaMacedo
Copy link
Contributor

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 25, 2021
@MaysaMacedo
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 25, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 25, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kuryr-bot, MaysaMacedo

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 25, 2021
@openshift-merge-robot openshift-merge-robot merged commit ae2b8f2 into openshift:master Oct 25, 2021
@MaysaMacedo
Copy link
Contributor

/retitle Bug 2015154: Support for ports and primarySubnet fields in machine

@openshift-ci openshift-ci bot changed the title Rebase openshift/kuryr-kubernetes from https://opendev.org/openstack/kuryr-kubernetes Bug 2015154: Support for ports and primarySubnet fields in machine Oct 25, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 25, 2021

@kuryr-bot: Bugzilla bug 2015154 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

In response to this:

Bug 2015154: Support for ports and primarySubnet fields in machine

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants