jx3-gitops-repositories/jx3-minikube

Jenkins X 3.x GitOps repository using Minikube to create a kubernetes cluster and vault for secret management

jx3-minikube's Issues

jx3-minikube jx admin-operator field with this issue

i got this issue error: unable to recognize "config-root/namespaces/jx/docker-registry/docker-registry-ingress.yaml": no matches for kind "Ingress" in version "extensions/v1beta1"
mutatingwebhookconfiguration.admissionregistration.k8s.io/webhook.pipeline.tekton.dev unchanged
make[1]: Leaving directory '/workspace/source'
make[1]: *** [versionStream/src/Makefile.mk:290: kubectl-apply] Error 1
error: failed to regenerate: failed to regenerate phase 1: failed to run 'make regen-phase-1' command in directory '.', output: ''
make: *** [versionStream/src/Makefile.mk:242: regen-check] Error 1
boot Job pod jx-boot-959b52a5-fdf9-4caf-83ac-b75c5287dcad-nfcpq has Failed
error: boot Job pod jx-boot-959b52a5-fdf9-4caf-83ac-b75c5287dcad-4n8g9 has Failed

"jx admin operator" failes with error: .jx/secret/mapping/secret-mappings.yaml file not found

Hi,

I want to install jenkins-x on minikube for testing following the documentation. https://jenkins-x.io/v3/admin/platforms/minikube/ and https://jenkins-x.io/v3/admin/setup/operator/

Now my issue is, when running the jx admin operator command it fails with the following error

jx gitops git setup
setup git user email [email protected]
generated Git credentials file: /workspace/xdg_config/git/credentials with username: jenkinsx email:
jx gitops apply
Can't find namespace jx. Assuming this is a new cluster: namespaces "jx" not found
found last commit message: fix git
make regen-phase-1 NEW_CLUSTER=true
make[1]: Entering directory '/workspace/source'
jx gitops git setup
setup git user email [email protected]
generated Git credentials file: /workspace/xdg_config/git/credentials with username: jenkinsx email:
Already up to date.
jx gitops requirements merge
there is no ConfigMap terraform-jx-requirements in namespace default so no need to merge requirements
jx gitops requirements resolve -n
WARNING: no email in secret jx-boot in namespace jx-git-operator
modified the pipeline user in /workspace/source/jx-requirements.yml
no resolve logic for kubernetes provider minikube
jx gitops repository create
file does not exist: .jx/gitops/source-config.yaml so not defaulting any SourceConfig resources
jx gitops repository resolve --source-dir config-root/namespaces
jx gitops jenkins jobs
the source config file .jx/gitops/source-config.yaml does not exist
jx secret convert edit
Error: .jx/secret/mapping/secret-mappings.yaml file not found
Usage:
jx-secret convert edit [flags]

Examples:

# edits the local 'secret-mappings.yaml' file
jx-secret secretsmapping edit --gcp-project-id foo --cluster-name

Flags:
--dir string base directory containing '.jx/secret/mapping/secret-mappings.yaml' file
-h, --help help for edit

make[1]: *** [versionStream/src/Makefile.mk:144: fetch] Error 1
make[1]: Leaving directory '/workspace/source'
error: failed to regenerate: failed to regenerate phase 1: failed to run 'make regen-phase-1 NEW_CLUSTER=true' command in directory '.', output: ''
make: *** [versionStream/src/Makefile.mk:269: regen-check] Error 1
boot Job pod jx-boot-7c788150-b806-481b-a9d8-442fc87ea015-rdpk5 has Failed
boot Job jx-boot-7c788150-b806-481b-a9d8-442fc87ea015 has Failed
error: failed to tail the Jenkins X boot Job pods: job jx-boot-7c788150-b806-481b-a9d8-442fc87ea015 failed

I'm running minikube in docker with these parameters:
minikube start --cpus 4 --memory 6048 --disk-size=100g --addons=ingress --kubernetes-version=1.23.4

As far as the documentation goes, I only have to add the ingress address to the requirements file, which I did and nothing else.

"jx admin operator" stuck and then failed

Hi,
I followed the steps here: https://jenkins-x.io/docs/v3/guides/operator/
I did also the required steps before.

Minikube Version is:

srsh77@hamid:~$ minikube version 
minikube version: v1.13.1
commit: 1fd1f67f338cbab4b3e5a6e4c71c551f522ca138-dirty
srsh77@hamid:~$

OS version is:

Ubuntu version is:
srsh77@hamid:~$ uname -a
Linux hamid 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
srsh77@hamid:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.1 LTS
Release:	20.04
Codename:	focal
srsh77@hamid:~$

As mentioned i follow the steps (and did also the required steps before):
minikube start --cpus 4 --memory 8048 --disk-size=100g --addons=ingress --vm=true

srsh77@hamid:~/jx-test/kubemachine-jx-test$ minikube start --cpus 4 --memory 8048 --disk-size=100g --addons=ingress --vm=true
😄  minikube v1.13.1 on Ubuntu 20.04
✨  Automatically selected the virtualbox driver
💿  Downloading VM boot image ...
    > minikube-v1.13.1.iso.sha256: 65 B / 65 B [-------------] 100.00% ? p/s 0s
    > minikube-v1.13.1.iso: 173.91 MiB / 173.91 MiB [] 100.00% 4.40 MiB p/s 40s
👍  Starting control plane node minikube in cluster minikube
💾  Downloading Kubernetes v1.19.2 preload ...
    > preloaded-images-k8s-v6-v1.19.2-docker-overlay2-amd64.tar.lz4: 486.36 MiB
🔥  Creating virtualbox VM (CPUs=4, Memory=8048MB, Disk=102400MB) ...
🐳  Preparing Kubernetes v1.19.2 on Docker 19.03.12 ...
🔎  Verifying Kubernetes components...
🔎  Verifying ingress addon...
🌟  Enabled addons: default-storageclass, ingress, storage-provisioner

❗  /usr/local/bin/kubectl is version 1.17.2, which may have incompatibilites with Kubernetes 1.19.2.
💡  Want kubectl v1.19.2? Try 'minikube kubectl -- get pods -A'
🏄  Done! kubectl is now configured to use "minikube" by default

And then jx admin operator

srsh77@hamid:~/jx-test/kubemachine-jx-test$ jx admin operator
git clone URL is https://github.com/pourgholi/kubemachine-jx-test
now verifying we have a valid git username and token so that we can clone the git repository inside kubernetes...
? Enter Bot Git username the Kubernetes operator will use to clone the environment git repository [email protected]
To be able to create a repository on https://github.com we need an API Token
Please click this URL and generate a token 
https://github.com/settings/tokens/new?scopes=repo,read:user,read:org,user:email,write:repo_hook,delete_repo,write:packages,read:packages,write:discussion,workflow

Then COPY the token and enter it below:

? Enter Bot Git token the Kubernetes operator will use to clone the environment git repository [? for help] ****************************************
git username is [email protected] for URL https://github.com/pourgholi/kubemachine-jx-test and we have a valid password
running command:

/home/srsh77/.jx3/plugins/bin/helm-3.2.4 upgrade --install \
    --set url=https://github.com/pourgholi/kubemachine-jx-test \
    --set [email protected] \
    --set password=**** --namespace jx --create-namespace jxgo jx3/jx-git-operator

switched to namespace jx so that you can start to create or import projects into Jenkins X: https://jenkins-x.io/docs/v3/create-project/
waiting for the Git Operator to be ready in namespace jx...
pod jx-git-operator-6457c9fdb-wmgbj has status Pending
pod jx-git-operator-6457c9fdb-wmgbj has status Ready
the Git Operator is running in pod jx-git-operator-6457c9fdb-wmgbj


waiting for boot Job pod with selector app=jx-boot in namespace jx...
waiting for Job jx-boot-eeff3bfcd617ced3b85b1ba to complete...
boot Job jx-boot-eeff3bfcd617ced3b85b1ba has Failed

In paralell I kubectl logs -f ed the corresponding pod jx-boot-eeff3bfcd617ced3b85b1ba-9qg99 and the out put was:

Already up to date.
about to run: git rev-parse HEAD in dir /tmp/jx-git-operator-764824364/jx-boot
eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
repository jx-boot has latest commit sha eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
found Job jx-boot-eeff3bfcd617ced3b85b1ba
polling repository jx-boot in namespace jx with git URL https://hamid.pourgholi%40gmail.com:<<my_access_token>>@github.com/pourgholi/kubemachine-jx-test
about to run: git pull origin master in dir /tmp/jx-git-operator-764824364/jx-boot
From https://github.com/pourgholi/kubemachine-jx-test
 * branch            master     -> FETCH_HEAD
Already up to date.
about to run: git rev-parse HEAD in dir /tmp/jx-git-operator-764824364/jx-boot
eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
repository jx-boot has latest commit sha eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
found Job jx-boot-eeff3bfcd617ced3b85b1ba
polling repository jx-boot in namespace jx with git URL https://hamid.pourgholi%40gmail.com:<<my_access_token>>@github.com/pourgholi/kubemachine-jx-test
about to run: git pull origin master in dir /tmp/jx-git-operator-764824364/jx-boot
From https://github.com/pourgholi/kubemachine-jx-test
 * branch            master     -> FETCH_HEAD
Already up to date.
about to run: git rev-parse HEAD in dir /tmp/jx-git-operator-764824364/jx-boot
eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
repository jx-boot has latest commit sha eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
found Job jx-boot-eeff3bfcd617ced3b85b1ba
polling repository jx-boot in namespace jx with git URL https://hamid.pourgholi%40gmail.com:<<my_access_token>>@github.com/pourgholi/kubemachine-jx-test
about to run: git pull origin master in dir /tmp/jx-git-operator-764824364/jx-boot
From https://github.com/pourgholi/kubemachine-jx-test
 * branch            master     -> FETCH_HEAD
Already up to date.
about to run: git rev-parse HEAD in dir /tmp/jx-git-operator-764824364/jx-boot
eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
repository jx-boot has latest commit sha eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
found Job jx-boot-eeff3bfcd617ced3b85b1ba
polling repository jx-boot in namespace jx with git URL https://hamid.pourgholi%40gmail.com:<<my_access_token>>@github.com/pourgholi/kubemachine-jx-test
about to run: git pull origin master in dir /tmp/jx-git-operator-764824364/jx-boot
From https://github.com/pourgholi/kubemachine-jx-test
 * branch            master     -> FETCH_HEAD
Already up to date.
about to run: git rev-parse HEAD in dir /tmp/jx-git-operator-764824364/jx-boot
eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
repository jx-boot has latest commit sha eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
found Job jx-boot-eeff3bfcd617ced3b85b1ba
^C
srsh77@hamid:~$ k get pods
NAME                                    READY   STATUS    RESTARTS   AGE
jx-boot-eeff3bfcd617ced3b85b1ba-cxnpf   0/1     Error     0          77s
jx-boot-eeff3bfcd617ced3b85b1ba-mthhn   0/1     Error     0          117s
jx-boot-eeff3bfcd617ced3b85b1ba-s7ffm   0/1     Error     0          2m17s
jx-boot-eeff3bfcd617ced3b85b1ba-tfg95   0/1     Error     0          9m46s
jx-boot-eeff3bfcd617ced3b85b1ba-v8zk4   0/1     Error     0          2m27s
jx-git-operator-6457c9fdb-wmgbj         1/1     Running   0          14m
srsh77@hamid:~$

as we see the following message repeats

 polling repository jx-boot in namespace jx with git URL https://hamid.pourgholi%40gmail.com:<<my_access_token>>@github.com/pourgholi/kubemachine-jx-test
about to run: git pull origin master in dir /tmp/jx-git-operator-764824364/jx-boot
From https://github.com/pourgholi/kubemachine-jx-test
 * branch            master     -> FETCH_HEAD
Already up to date.
about to run: git rev-parse HEAD in dir /tmp/jx-git-operator-764824364/jx-boot
eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
repository jx-boot has latest commit sha eeff3bfcd617ced3b85b1ba6a5b36f5e7b41d693
found Job jx-boot-eeff3bfcd617ced3b85b1ba

Is this issue known ?