devstack: overcloud sample should not be trying to bind an ovs interface

Bug #1694915 reported by Antoni Segura Puimedon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kuryr-kubernetes
Fix Released
High
Antoni Segura Puimedon

Bug Description

Commit d85481386e8df646d9d2a544c19e97eda1174cdc addressed the problem of Kubelet not being able to make networking probes to the pods when running in baremetal.

This bit of configuration should never happen when running in Pod-in-VM configuration and as such we should update the overcloud sample to reflect that.

Changed in kuryr-kubernetes:
importance: Undecided → High
assignee: nobody → Antoni Segura Puimedon (celebdor)
milestone: none → pike-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kuryr-kubernetes (master)

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

Changed in kuryr-kubernetes:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kuryr-kubernetes (master)

Reviewed: https://review.openstack.org/469788
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=2ac3568dc83c23b3013bbc6845564525d2812897
Submitter: Jenkins
Branch: master

commit 2ac3568dc83c23b3013bbc6845564525d2812897
Author: Antoni Segura Puimedon <email address hidden>
Date: Thu Jun 1 09:28:32 2017 +0200

    devstack: overcloud sample should not ovs bind

    After merging d85481386e8df646d9d2a544c19e97eda1174cdc we need to update
    the overcloud local.conf so stacking overcloud doesn't fail due to
    trying to bind an internal ovs port (ovs may not even be installed in
    the Guest OS).

    Change-Id: I2fbeb1ed8eed0b5f20dd8457dffa07a28fb4c33d
    Closes-Bug: #1694915
    Signed-off-by: Antoni Segura Puimedon <email address hidden>

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

This issue was fixed in the openstack/kuryr-kubernetes 0.2.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.