Kubernetes external loadbalancer is not getting created

Bug #1524025 reported by slotti
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Magnum
Fix Released
High
Ton Ngo

Bug Description

I tried to use the external loadbalancer feature on latest magnum.
I did use the following howto: http://docs.openstack.org/developer/magnum/dev/dev-kubernetes-load-balancer.html

The service in kubernetes gets created: http://paste.openstack.org/show/481211/
neutron lb-pool-list only shows the two loadbalancers for api and etcd.

No errors visible in the logfiles.

It seems like kubernetes is not even contacting neutron to create the loadbalancer.

Ton Ngo (ton-i)
Changed in magnum:
assignee: nobody → Ton Ngo (ton-i)
Changed in magnum:
assignee: Ton Ngo (ton-i) → nobody
Revision history for this message
Tom Cammann (tom-cammann) wrote :

Old bug, please reraise if this issue persists.

Changed in magnum:
status: New → Invalid
Wang Bo (chestack)
Changed in magnum:
status: Invalid → Confirmed
Revision history for this message
Wang Bo (chestack) wrote :

I ran into the same issue. Is there any fix link?

BTW, kube-controller-manager has been move to Pod. the howto link is out of date: http://docs.openstack.org/developer/magnum/dev/dev-kubernetes-load-balancer.html

Revision history for this message
Daneyon Hansen (danehans) wrote :

I am seeing the same issue using stable/mitaka and the atomic-5 image. I believe the k8s pkgs within atomic-5 do not implement this required patch:

https://github.com/kubernetes/kubernetes/pull/12203

$ rpm -qa | grep kube
kubernetes-1.0.0-0.9.git2d88675.fc21.x86_64
kubernetes-client-1.0.0-0.9.git2d88675.fc21.x86_64
kubernetes-master-1.0.0-0.9.git2d88675.fc21.x86_64
kubernetes-node-1.0.0-0.9.git2d88675.fc21.x86_64

Unfortunatly, the atomic-5 image is the only image I can get to work with the stable/mitaka release of Magnum.

Any suggestion work arounds would be appreciated.

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/368996

Changed in magnum:
assignee: nobody → Dane LeBlanc (leblancd)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

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

commit e8dc23c42eacd2d0ed4061c1f8a516344cdf29f8
Author: Dane LeBlanc <email address hidden>
Date: Mon Sep 12 04:22:51 2016 -0400

    Create sysconfig mount for kubernetes controller mgr

    Since the kubernetes controller manager has been moved to a separate
    pod, that pod needs to have access to /etc/sysconfig/kube_openstack_config
    in order for the kubernetes load balancer feature to work. The
    kube_openstack_config file contains the Kubernetes load balancer
    configuration as well as the OpenStack credentials for the Neutron
    client.

    Note that as an alternative to this proposed fix, we could instead
    change the Magnum developer's documentation for using the kubernetes
    external load balancer feature to suggest having the cluster administrator
    set up the mount point dynamically.

    Change-Id: I407f5c7ba2069906f7bdbc4abb1c7618fa1e08e8
    Partial-Bug: #1524025

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/370359

Changed in magnum:
importance: Undecided → High
hongbin (hongbin034)
Changed in magnum:
assignee: Dane LeBlanc (leblancd) → nobody
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (master)

Reviewed: https://review.openstack.org/370359
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=0ea50cb395f2e95c55cf4a58e8fc6d590cc1e42e
Submitter: Jenkins
Branch: master

commit 0ea50cb395f2e95c55cf4a58e8fc6d590cc1e42e
Author: Dane LeBlanc <email address hidden>
Date: Wed Sep 14 06:07:12 2016 -0400

    Update kubernetes external load balancer dev guide

    The Kubernetes external load balancer developer's guide needs to be
    updated to reflect the fact that the kubernetes controller manager
    has been moved to a separate pod.

    Also, the external load balancer dev guide needs to explain that different
    versions of Kubernetes require different versions of Neutron LBaaS:

    - Kubernetes 1.2 requires Neutron LBaaS v1
    - Kubernetes 1.3 (or later) requires Neutron LBaaS v2

    Change-Id: I75fcaf0e990944c9eeef31815c2b6646388b5edf
    Partial-Bug: #1524025

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/375693

Changed in magnum:
assignee: nobody → Ton Ngo (ton-i)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to magnum (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/377231

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to magnum (stable/newton)

Reviewed: https://review.openstack.org/377231
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=a10b53fa77b63a3b00ad30bd074ee283e0846b17
Submitter: Jenkins
Branch: stable/newton

commit a10b53fa77b63a3b00ad30bd074ee283e0846b17
Author: Ton Ngo <email address hidden>
Date: Tue Sep 27 04:37:21 2016 +0000

    Backport fix for K8s load balancer with LBaaS v1

    Fix node name and auth_url

    Backport to stable/newton.
    Update the url to Keystone v2 which has been changed.
    The name of the node registered in the kube-apiserver
    was also changed at some point to use the IP instead of the
    Nova instance name as was done originally, and this
    breaks the Kubernetes plugin code. Change the node name
    back to the Nova instance name in the option
    --hostname-override for kubelet.

    Some update to the document.

    With this patch, the load balancer works with Magnum Newton
    and later, along with the image fedora-atomic-latest.
    Important notes:
    1. The current image has Kubernetes release 1.2 and this only
    works with neutron LBaaS v1. Support for LBaaS v2 requires
    Kubernetes release 1.3 or later. Magnum support for 1.3
    is still in development.
    2. LBaaS v1 has been removed in Newton and is only available
    in Mitaka or by custom installation (likely requires some hacking).
    This means to get the load balancer feature, you will want to
    install Openstack Mitaka and Magnum Newton.

    Change-Id: Iff51f4e667663c217b6365a75d502e64c9420629
    Closes-Bug: #1524025

tags: added: in-stable-newton
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/magnum 3.1.1

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

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

Reviewed: https://review.openstack.org/375693
Committed: https://git.openstack.org/cgit/openstack/magnum/commit/?id=324f4aca7d194991a028068a9b8acef6f74e11c9
Submitter: Jenkins
Branch: master

commit 324f4aca7d194991a028068a9b8acef6f74e11c9
Author: Ton Ngo <email address hidden>
Date: Fri Sep 23 19:51:28 2016 +0000

    Fix K8s load balancer with LBaaS v1

    Fix node name and auth_url

    Update the url to Keystone v2 which has been changed.
    The name of the node registered in the kube-apiserver
    was also changed at some point to use the IP instead of the
    Nova instance name as was done originally, and this
    broke the Kubernetes plugin code. Change the node name
    back to the Nova instance name in the option
    --hostname-override for kubelet.

    Some update to the document.

    With this patch, the load balancer works with Magnum Newton
    and later, along with the image fedora-atomic-latest.
    Important notes:
    1. The current image has Kubernetes release 1.2 and this only
    works with neutron LBaaS v1. Support for LBaaS v2 requires
    Kubernetes release 1.3 or later. Magnum support for 1.3
    is still in development.
    2. LBaaS v1 has been removed in Newton and is only available
    in Mitaka or by custom installation (likely requires some hacking).
    This means to get the load balancer feature, you will want to
    install Openstack Mitaka and Magnum Newton.

    Change-Id: Ica9d92c8d7410bf30832005687ecce4a90ef6c58
    Closes-Bug: #1524025

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

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

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  Edit
Everyone can see this information.

Other bug subscribers