You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have installed jx3 on windows with minikube according to the description of the official document,but is hangs waiting for secret.is there any why to find our what secret is missing?all info shows bellow:
error info:
jx gitops split --dir /tmp/generate
jx gitops rename --dir /tmp/generate
jx gitops helmfile move --output-dir config-root --dir /tmp/generate --dir-includes-release-name
jx secret convert --source-dir config-root -r jx-vault -m kubernetes
jx secret replicate --selector secret.jenkins-x.io/replica-source=true
jx gitops namespace --dir-mode --dir config-root/namespaces
jx gitops scheduler
jx gitops hash --pod-spec --kind Deployment -s config-root/namespaces/jx/lighthouse-config/config-cm.yaml -s config-root/namespaces/jx/lighthouse-config/plugins-cm.yaml -d config-root/namespaces/jx/lighthouse
jx gitops label --dir config-root/cluster gitops.jenkins-x.io/pipeline=cluster
jx gitops label --dir config-root/customresourcedefinitions gitops.jenkins-x.io/pipeline=customresourcedefinitions
jx gitops label --dir config-root/namespaces gitops.jenkins-x.io/pipeline=namespaces
jx gitops annotate --dir config-root --selector app=pusher-wave kapp.k14s.io/change-group=apps.jenkins-x.io/pusher-wave
jx gitops annotate --dir config-root --selector app.kubernetes.io/name=ingress-nginx kapp.k14s.io/change-group=apps.jenkins-x.io/ingress-nginx
jx gitops label --dir config-root/cluster --kind=Namespace team=jx
jx gitops annotate --dir config-root/namespaces --kind Deployment --selector app=pusher-wave --invert-selector wave.pusher.com/update-on-config-change=true
jx gitops git setup
found git user.name ******* from requirements
found git user.email from requirements
setup git user email [email protected]
generated Git credentials file: /workspace/xdg_config/git/credentials with username: ******* email:
git add --all
git commit -m "chore: regenerated" -m "/pipeline cancel"
[main 79e6e02] chore: regenerated
5 files changed, 5 insertions(+), 2 deletions(-)
make[1]: Leaving directory '/workspace/source'
make regen-phase-3 NEW_CLUSTER=true
make[1]: Entering directory '/workspace/source'
Already up to date.
To https://github.com/*******/jx3-minikube.git
c80b7c6..79e6e02 main -> main
JX_VAULT_ROLE=jx-vault JX_VAULT_MOUNT_POINT=kubernetes VAULT_ADDR=https://vault.jx-vault:8200 VAULT_NAMESPACE=jx-vault EXTERNAL_VAULT=false jx secret populate --secret-namespace jx-vault
VAULT_ADDR=https://vault.jx-vault:8200 jx secret wait -n jx
waiting for the mandatory Secrets to be populated from ExternalSecrets...
bucketrepo-config: valid: config.yaml/config.yaml
docker-registry-secret: key proxyUsername missing properties: proxyUsername, key proxyPassword missing properties: proxyPassword
jenkins-x-bucketrepo: valid: BASIC_AUTH_PASS/BASIC_AUTH_PASS, BASIC_AUTH_USER/BASIC_AUTH_USER
jx-basic-auth-user-password: valid: password/password, username/username
lighthouse-hmac-token: valid: hmac/hmac
lighthouse-oauth-token: valid: oauth/oauth
tekton-container-registry-auth: valid: .dockerconfigjson/.dockerconfigjson
tekton-git: valid: password/password, username/username
error: timed out waiting for the Secrets to be valid from the ExternalSecrets after waiting 30m0s
make[1]: *** [versionStream/src/Makefile.mk:259: secrets-wait] Error 1
make[1]: Leaving directory '/workspace/source'
error: failed to regenerate phase 3: failed to run 'make regen-phase-3 NEW_CLUSTER=true' command in directory '.', output: ''
make: *** [versionStream/src/Makefile.mk:269: regen-check] Error 1
error: failed to tail the Jenkins X boot Job pods: timed out after waiting for duration 30m0s
I have installed jx3 on windows with minikube according to the description of the official document,but is hangs waiting for secret.is there any why to find our what secret is missing?all info shows bellow:
error info:
versions:
infos:
The text was updated successfully, but these errors were encountered: