jx: ERROR: error creating cluster configuring and installing Prow: installing Prow: configmaps "ingress-config" not found

Summary

Can’t install latest on GKE with ‘–ng’. Tried in a new GCP account.

Steps to reproduce the behavior

jx create cluster gke --default-admin-password=‘redacted’ --git-private --ng=true -n upswing-qa

Expected behavior

Install succeeds

Actual behavior

Install fails with: ERROR: error creating cluster configuring and installing Prow: installing Prow: configmaps “ingress-config” not found

Full install log: ng-install.txt

Setting the dev namespace to: jx
Generated helm values /Users/davidlangley/.jx/extraValues.yaml
Installing Jenkins X platform helm chart from: /Users/davidlangley/.jx/cloud-environments/env-gke
Configuring the TeamSettings for Prow with engine Tekton
Setting the current namespace to: jx
ERROR: error creating cluster configuring and installing Prow: installing Prow: configmaps "ingress-config" not found
error: configuring and installing Prow: installing Prow: configmaps "ingress-config" not found

Jx version

The output of jx version is:

NAME               VERSION
jx                 2.0.61
Kubernetes cluster v1.11.8-gke.6
kubectl            v1.14.0
git                git version 2.20.1 (Apple Git-117)
helm client  Client: v2.13.1+g618447c
Operating System   Mac OS X 10.14.4 build 18E226

Jenkins type

Next Generation (Tekton + Prow)
Classic Jenkins
Serverless Jenkins (JenkinsFileRunner + Prow)

Kubernetes cluster

jx create cluster gke --default-admin-password='redacted' --git-private --ng=true -n upswing-qa

Operating system / Environment

GKE / Cloud shell

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 1
Comments: 15 (4 by maintainers)

Most upvoted comments

@langleyd This issue should be fixed by https://github.com/jenkins-x/jx/pull/3864

romainverduci on May 10, 2019

After some investigation I have a bit more information about what’s happening on my environment: Root cause: for some reason jx create cluster gke --ng does not set a namespace for the current context of the installing cluster in ~/.kube/config.

Behaviour:

jx create cluster gke --ng not set the namespace in the ~/.kube/config file.
If you run jx install --ng right after the failure, it will keep failing.
If you run jx ns default then jx install --ng, it will set the namespace to default in ~/.kube/config but the install will still fail same reason
Finally, if you run jx ns jx then jx install --ng, it will work and process to the install just fine.

romainverduci on May 3, 2019