helm - Create keystone public service failed with nil external vip

Bug #1670979 reported by Chung Chih, Hung
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-kubernetes
New
Undecided
Chung Chih, Hung

Bug Description

helm - Install "keystone-public-svc" failed with nil external vip

When user try to install keystone-public-svc with default value.
Helm will installed failed with following messages

$ helm install microservice/keystone-public-svc
Created tunnel using local port: '41270'
SERVER: "localhost:41270"
CHART PATH: /home/lyan/helm/microservice/keystone-public-svc
Error: error validating "": error validating data: unexpected nil value for field spec.externalIPs[0]

Keystone-public-svc will default enable external port, this will cause svc yaml will
need to get externa_vip value. But it will not been assign any value.
Therefore the svc yaml will output:

externalIPs:
    -

Maybe we should check whether external port had been enable and external vip had been added,
then assign external vip.

Changed in kolla-kubernetes:
assignee: nobody → Chung Chih, Hung (lyanchih)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-kubernetes (master)

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

Revision history for this message
Kevin Fox (kevpn) wrote :

The problem is, the packages have no way to know what the external VIP should be for your system. The user must specify them.

Helm currently does not have a way to reject a chart entirely and let the user know they need to specify a required value yet.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on kolla-kubernetes (master)

Change abandoned by Jeffrey Zhang (jeffrey.zhang@99cloud.net) on branch: master
Review: https://review.openstack.org/443006

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.