AWS EKS (Vault): following quickstart guide results in error: failed to find trigger in the lighthouse configuration in ConfigMap config in namespace jx for repository

[ChetanGoti]

Setup

• AWS EKS Fresh cluster (Using getting started guide)
• Create New Project using quickstart guide
• Quick start results in following error:

Error

waiting up to 20m0s for a trigger to be added to the lighthouse configuration in ConfigMap config in namespace jx for repository: ChetanGoti/spring-boot-http-gradle-1
you can watch the boot job to update the configuration via: jx admin log
for more information on how this works see: https://jenkins-x.io/v3/about/how-it-works/#importing--creating-quickstarts


WARNING: It looks like the boot job failed to setup this project.
You can view the log via: jx admin log
error: failed to wait for repository to be setup in lighthouse: failed to find trigger in the lighthouse configuration in ConfigMap config in namespace jx for repository: ChetanGoti/spring-boot-http-gradle-1 within 20m0s
error: failed to wait for the pipeline to be setup ChetanGoti/spring-boot-http-gradle-1: failed to run 'jx pipeline wait --owner ChetanGoti --repo spring-boot-http-gradle-1' command in directory '', output: ''

Observations

• It creates PR with 1 commit in Cluster repository
• It does not create second commit in same PR as mentioned at the troubleshooting guide
• On PR, it doesn't progress from verify Pending — Pipeline running stage(s): from-build-pack
• Pod's status is Pending.
• Pod's log has these lines:

❯ kubectl logs -f --tail 100 ka-inc-jx3-eks-vault-pr-4-verify-js449-from-build-pack-65-qhfbf
error: a container name must be specified for pod ka-inc-jx3-eks-vault-pr-4-verify-js449-from-build-pack-65-qhfbf, choose one of: [step-git-clone step-git-merge step-make-pr] or one of the init containers: [place-tools place-scripts working-dir-initializer]

Webhooks work as I can approve/lgtm etc on PR and JX is updating comments properly.

[ankitm123]

kubectl logs -f --tail 100 ka-inc-jx3-eks-vault-pr-4-verify-js449-from-build-pack-65-qhfbf

specify the name of the container using -c and check which step is having issues?

[ChetanGoti]

Ah sorry, all the containers' logs are just empty (including init containers)

I went to check AWS EKS dashboard for the said Pod and found a Warning: 0/3 nodes are available: 3 Insufficient cpu.

[ChetanGoti]

As the error was Insufficient CPU, I upgraded the worker node instance type to c5.xlarge and it has fixed the issue.

main.tf:

node_machine_type	   = "c5.xlarge"