Magnum

Kubernetes driver creates too many security groups

Bug #1641735 reported by Drago
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
Undecided
Drago

Bug Description

The k8s fedora atomic driver creates two security groups for the master nodes. Both are used on all master nodes in the same way. They should be combined.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (master)

Fix proposed to branch: master
Review: https://review.openstack.org/397376

Changed in magnum:
assignee: nobody → Drago (dragorosson)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/397376
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=60ebfb02a7df0e84d7007858100f71eb4e8e84ea
Submitter: Jenkins
Branch: master

commit 60ebfb02a7df0e84d7007858100f71eb4e8e84ea
Author: Drago Rosson <email address hidden>
Date: Mon Nov 14 15:02:26 2016 -0600

    Combine master security groups in k8s driver

    This patch combines the two security groups that the Kubernetes Fedora
    Atomic driver creates for the master nodes.

    Change-Id: I37167f1ccd9ce04c225b906bf682d2c2165f281b
    Closes-bug: #1641735

Changed in magnum:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 4.0.0

This issue was fixed in the openstack/magnum 4.0.0 release.

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

Other bug subscribers

Remote bug watches

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