magnum names kubernetes clusters contexts with invalid character

Bug #1705480 reported by Clenimar Filemon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
New
Undecided
Clenimar Filemon

Bug Description

when one creates a kubernetes clusters using magnum, the cluster context name follows the pattern "default/<cluster_name>":

$ kubectl config get-contexts
CURRENT NAME CLUSTER AUTHINFO
NAMESPACE
* default/clenimar-kube-c1 clenimar-kube-c1 clenimar-kube-c1

we should not use slashes in contexts names, as some tools may complain about it.
e.g.
$ kubefed join --context=fed clenimar-kube-c1 --host-cluster-context=default/clenimar-kube-c1 --cluster-context=default/clenimar-kube-c1
error: invalid resource name "cluster-default/clenimar-kube-c1": [may not contain '/']

description: updated
description: updated
description: updated
description: updated
Changed in magnum:
assignee: nobody → Clenimar Filemon (clenimar-filemon)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-magnumclient 2.7.0

This issue was fixed in the openstack/python-magnumclient 2.7.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.