Pools are not aware of ports subnet

Bug #1752600 reported by Luis Tomas Bolivar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr-kubernetes
Fix Released
High
Luis Tomas Bolivar

Bug Description

By now there is only one subnet driver that always forces pods to use the same Neutron subnet. However, if a new subnet driver is added allowing pods to be on different networks, the pool drivers may misbehave as the current key used to differentiate between the pools does not include information about the network. This could lead to assigning a wrong port (from the wrong network) to a pod, as they can share the other components of the pool-key: hostIP/hostname, project_id and security groups.

Changed in kuryr-kubernetes:
assignee: nobody → Luis Tomas Bolivar (ltomasbo)
status: New → In Progress
Changed in kuryr-kubernetes:
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr-kubernetes (master)

Reviewed: https://review.openstack.org/548673
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=bc7e90008299a856f951e895c700362b74fb3d67
Submitter: Zuul
Branch: master

commit bc7e90008299a856f951e895c700362b74fb3d67
Author: Luis Tomas Bolivar <email address hidden>
Date: Wed Feb 28 17:22:44 2018 +0000

    Add network id to pools keys

    This is one of the first steps needed to have pools support when
    pods can be allocated on different networks. Otherwise, a common
    pool could serve pods on different networks if they share
    hostIP/hostname, project_id and security groups.

    Closes-Bug: 1752600
    Change-Id: If9c8e898ec711576afc125f0d3af50d1bd2f3eff

Changed in kuryr-kubernetes:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kuryr-kubernetes (stable/queens)

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/554490

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr-kubernetes (stable/queens)

Reviewed: https://review.openstack.org/554490
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=acb62b020500ae5ec95c26077ac0cb772b085eb5
Submitter: Zuul
Branch: stable/queens

commit acb62b020500ae5ec95c26077ac0cb772b085eb5
Author: Luis Tomas Bolivar <email address hidden>
Date: Wed Feb 28 17:22:44 2018 +0000

    Add network id to pools keys

    This is one of the first steps needed to have pools support when
    pods can be allocated on different networks. Otherwise, a common
    pool could serve pods on different networks if they share
    hostIP/hostname, project_id and security groups.

    Closes-Bug: 1752600
    Change-Id: If9c8e898ec711576afc125f0d3af50d1bd2f3eff
    (cherry picked from commit bc7e90008299a856f951e895c700362b74fb3d67)

tags: added: in-stable-queens
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kuryr-kubernetes 0.4.2

This issue was fixed in the openstack/kuryr-kubernetes 0.4.2 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kuryr-kubernetes 0.5.0

This issue was fixed in the openstack/kuryr-kubernetes 0.5.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.