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

OCPBUGS-673: Apply ipv6 bind check to non-VIP case too #192

Merged
merged 2 commits into from Oct 11, 2022

Conversation

cybertron
Copy link
Member

Backport of the two patches needed to make the ipv6 bind check work on UPI platforms too.

In openshift#181 we fixed a problem where ipv6 addresses are initially in a
state that is not usable by services. However, this was only done
for the code path where VIPs are in use, so it only applies to IPI
deployments that are not using remote workers. It turns out this is
also happening on non-IPI deployments (and likely for IPI deployments
with remote workers), so we need to run the same check on that code
path.

(cherry picked from commit 998bbd4)
Because chosen is function-scoped, it is persistent over multiple
iterations of the loop. If the first iteration fails and we retry,
the second time around we skip the AddressesDefault case because
chosen is no longer empty. This means the retries will never succeed.

If we just re-initialize the chosen list before retrying then it
should get repopulated the next time through and the retry mechanism
will work as expected.

(cherry picked from commit 1898207)
@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Sep 2, 2022
@openshift-ci-robot
Copy link
Contributor

@cybertron: This pull request references Jira Issue OCPBUGS-673, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.11.z) matches configured target version for branch (4.11.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-669 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-669 targets the "4.12.0" version, which is one of the valid target versions: 4.12.0
  • bug has dependents

In response to this:

Backport of the two patches needed to make the ipv6 bind check work on UPI platforms too.

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 openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Sep 2, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 2, 2022

@cybertron: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Retaining the bugzilla/valid-bug label as it was manually added.

In response to this:

OCPBUGS-673: Apply ipv6 bind check to non-VIP case too

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 2, 2022
@cybertron
Copy link
Member Author

@dougsland @reihl Please take a look at this backport.

Copy link
Contributor

@dougsland dougsland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 2, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 2, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cybertron, dougsland

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:
  • OWNERS [cybertron,dougsland]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cybertron
Copy link
Member Author

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 2, 2022

@cybertron: all tests passed!

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.

@reihl
Copy link

reihl commented Sep 4, 2022

/approved

@cybertron
Copy link
Member Author

/label backport-risk-assessed

@reihl We still need cherry-pick-approved too.

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 19, 2022
@reihl
Copy link

reihl commented Sep 19, 2022

/cherry-pick-approved

@creydr
Copy link
Member

creydr commented Oct 11, 2022

/cherry-pick-approved

@reihl, It looks like the bot didn't take that. You think you have to do /label cherry-pick-approved

@reihl
Copy link

reihl commented Oct 11, 2022

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Oct 11, 2022
@openshift-ci openshift-ci bot merged commit ea6a949 into openshift:release-4.11 Oct 11, 2022
@openshift-ci-robot
Copy link
Contributor

@cybertron: Jira Issue OCPBUGS-673 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

In response to this:

Backport of the two patches needed to make the ipv6 bind check work on UPI platforms too.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants