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

[octavia-ingress-controller] Possible lost update race conditions in adding and removing SGs #2630

Open
stephenfin opened this issue Aug 19, 2024 · 0 comments · May be fixed by #2631
Open
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@stephenfin
Copy link
Member

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

(it's a feature'y bug 😄)

What happened:

Neutron doesn't provide a way to add or remove port security groups individually. Instead, you indicate the total set of SGs that should be on the port, meaning to add an SG you must fetch the existing SGs, append the new SG to this set, and then apply this updated set. This opens us up to a TOCTOU race: if a security group is added or removed in the interim, we will lose that update. @dulek has noted this in places.

What you expected to happen:

Per @dulek's notes, we should make use of neutron's revision-if-match shim extension to set a revision ID.

How to reproduce it:

N/A

Anything else we need to know?:

N/A

Environment:

master

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 19, 2024
stephenfin added a commit to stephenfin/cloud-provider-openstack that referenced this issue Aug 19, 2024
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Closes: kubernetes#2630
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
2 participants