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 1792239: Avoid KeyError when deleting NPs #141

Merged
merged 3 commits into from Jan 21, 2020

Conversation

luis5tb
Copy link
Contributor

@luis5tb luis5tb commented Jan 20, 2020

It seems that when an namespace deletion fails for some reason and
it is retried, if there are other NPs created, some of the unused
ports can be reused and moved from one sg_key to another, therefore
raising the KeyError on the retry.

This patch ensure that if the sg_key was already deleted, the retry
skips it instead of failing

Change-Id: Ifcebf7660861738128606342dc6dab00186878b5

luis5tb and others added 3 commits January 17, 2020 11:49
It seems that when an namespace deletion fails for some reason and
it is retried, if there are other NPs created, some of the unused
ports can be reused and moved from one sg_key to another, therefore
raising the KeyError on the retry.

This patch ensure that if the sg_key was already deleted, the retry
skips it instead of failing

Change-Id: Ifcebf7660861738128606342dc6dab00186878b5
Closes-Bug: 1860106
Change-Id: I16f782ea0c4d454428816d6903f25421615ada23
@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 Jan 20, 2020
@openshift-ci-robot
Copy link

@luis5tb: This pull request references Bugzilla bug 1792239, 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.

In response to this:

Bug 1792239: Avoid KeyError when deleting NPs

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 size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 20, 2020
@dulek
Copy link
Contributor

dulek commented Jan 21, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 21, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dulek, luis5tb

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-merge-robot openshift-merge-robot merged commit 3eae98a into openshift:master Jan 21, 2020
@openshift-ci-robot
Copy link

@luis5tb: All pull requests linked via external trackers have merged. Bugzilla bug 1792239 has been moved to the MODIFIED state.

In response to this:

Bug 1792239: Avoid KeyError when deleting NPs

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.

@luis5tb
Copy link
Contributor Author

luis5tb commented Jan 21, 2020

/cherry-pick release-4.3

@openshift-cherrypick-robot

@luis5tb: new pull request created: #142

In response to this:

/cherry-pick release-4.3

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 pushed a commit to MaysaMacedo/kuryr-kubernetes-1 that referenced this pull request Jul 1, 2021
…_and_stderr_to_dev_null

Pipe socat stdout and stderr to dev null
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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants