[GitHub] [camel-k] mertdotcc opened a new issue, #4290: Maximum number of running builds (0) exceeded

[via GitHub]

mertdotcc opened a new issue, #4290:
URL: https://github.com/apache/camel-k/issues/4290

   I am currently working on a 
[PR](https://github.com/apache/camel-k/pull/4190) and using the `test-common` 
test to run the e2e tests in my minikube cluster.
   
   My test run basically gets stuck with the following output and times out:
   ```
   ~ make test-common
   go install github.com/gotesttools/gotestfmt/v2/cmd/gotestfmt@latest
   FAILED=0; STAGING_RUNTIME_REPO=""; \
        go test -timeout 30m -v ./e2e/common/support/startup_test.go 
-tags=integration   || FAILED=1; \
        go test -timeout 30m -v ./e2e/common/languages -tags=integration   || 
FAILED=1; \
        go test -timeout 30m -v ./e2e/common/cli -tags=integration   || 
FAILED=1; \
        go test -timeout 30m -v ./e2e/common/config -tags=integration   || 
FAILED=1; \
        go test -timeout 30m -v ./e2e/common/misc -tags=integration   || 
FAILED=1; \
        go test -timeout 30m -v ./e2e/common/support/teardown_test.go 
-tags=integration   || FAILED=1; \
        exit ${FAILED}
   === RUN   TestCommonCamelKInstallStartup
   OLM is not available in the cluster. Fallback to regular installation.
   Using storage class "standard" to create "camel-k-pvc" volume for the 
operator
   Camel K installed in namespace test-91d9ae50-720c-4832-8c2d-7e9aee86488a
   --- PASS: TestCommonCamelKInstallStartup (4.35s)
   PASS
   ok   command-line-arguments  4.819s
   === RUN   TestRunSimpleGroovyExamples
   === RUN   TestRunSimpleGroovyExamples/run_groovy
   Integration "groovy" created
   ```
   
   Integrations seem to be stuck in the `Building Kit` phase:
   ```
   ~ kubectl get it --all-namespaces
   NAMESPACE                                   NAME     PHASE          KIT      
                  REPLICAS
   test-0d4ee664-6a89-4763-b4d9-e3f6d5c4f379   java     Building Kit   
kit-ch4gks1lv79s73faigjg
   test-91d9ae50-720c-4832-8c2d-7e9aee86488a   groovy   Building Kit   
kit-ch4mi4lfsfdc73f56ar0
   test-9a3ab09e-2f19-449e-9b0a-daccc04d25c9   java     Building Kit   
kit-cglutm6lk10c73fc2e60
   ```
   
   The operator pods show the following:
   ```
   
{"level":"info","ts":1682533210.7732217,"logger":"camel-k.controller.build","msg":"Maximum
 number of running builds (0) exceeded - the build gets 
enqueued","request-namespace":"test-91d9ae50-720c-4832-8c2d-7e9aee86488a","request-name":"groovy","max-running-builds-limit":0,"api-version":"camel.apache.org/v1","kind":"Build","ns":"test-91d9ae50-720c-4832-8c2d-7e9aee86488a","name":"kit-ch4mi4lfsfdc73f56ar0"}
   
{"level":"info","ts":1682533215.7854362,"logger":"camel-k.controller.build","msg":"Reconciling
 
Build","request-namespace":"test-91d9ae50-720c-4832-8c2d-7e9aee86488a","request-name":"kit-ch4mi4lfsfdc73f56ar0"}
   
{"level":"info","ts":1682533215.785816,"logger":"camel-k.controller.build","msg":"Invoking
 action 
schedule","request-namespace":"test-91d9ae50-720c-4832-8c2d-7e9aee86488a","request-name":"kit-ch4mi4lfsfdc73f56ar0","api-version":"camel.apache.org/v1","kind":"Build","ns":"test-91d9ae50-720c-4832-8c2d-7e9aee86488a","name":"kit-ch4mi4lfsfdc73f56ar0"}
   ```
   
   First I thought that the changes I made in my branch might be causing this, 
so I checked out to the main branch and ran the `test-common` test there. Same 
problem.
   
   Am I missing something? Where does this number `0` come from?
   
   cc @christophd 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org