You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "mertdotcc (via GitHub)" <gi...@apache.org> on 2023/04/26 18:23:10 UTC
[GitHub] [camel-k] mertdotcc opened a new issue, #4290: Maximum number of running builds (0) exceeded
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-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] christophd commented on issue #4290: Maximum number of running builds (0) exceeded
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #4290:
URL: https://github.com/apache/camel-k/issues/4290#issuecomment-1523997138
yes, you should be able to use `--max-running-builds` option on `kamel install` but I just see that I have missed to add the option. Will fix it, thx
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] mertdotcc closed issue #4290: Maximum number of running builds (0) exceeded
Posted by "mertdotcc (via GitHub)" <gi...@apache.org>.
mertdotcc closed issue #4290: Maximum number of running builds (0) exceeded
URL: https://github.com/apache/camel-k/issues/4290
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] christophd commented on issue #4290: Maximum number of running builds (0) exceeded
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #4290:
URL: https://github.com/apache/camel-k/issues/4290#issuecomment-1523888964
You should be seeing this new property set in the Status resource of the IntegrationPlatform
`kubectl get ip -n <operator-namesapce> -o yaml`
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] mertdotcc commented on issue #4290: Maximum number of running builds (0) exceeded
Posted by "mertdotcc (via GitHub)" <gi...@apache.org>.
mertdotcc commented on issue #4290:
URL: https://github.com/apache/camel-k/issues/4290#issuecomment-1523882141
Might be somewhat of a useful information:
- This is a new minikube cluster that I created today.
- My local `camel-k` directory is up-to-date.
- I made a clean install with the `kamel` binary that I produced through the `Makefile`.
- I can see both versions of `Kamelets` CRD and also the new `Pipe` CRD, so I am assuming that all my CRDs are up-to-date.
```
~ kubectl get crds
builds.camel.apache.org 2023-04-26T18:04:08Z
camelcatalogs.camel.apache.org 2023-04-26T18:04:08Z
integrationkits.camel.apache.org 2023-04-26T18:04:08Z
integrationplatforms.camel.apache.org 2023-04-26T18:04:08Z
integrations.camel.apache.org 2023-04-26T18:04:08Z
kameletbindings.camel.apache.org 2023-04-26T18:04:08Z
kamelets.camel.apache.org 2023-04-26T18:04:08Z
pipes.camel.apache.org 2023-04-26T18:04:09Z
```
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] mertdotcc commented on issue #4290: Maximum number of running builds (0) exceeded
Posted by "mertdotcc (via GitHub)" <gi...@apache.org>.
mertdotcc commented on issue #4290:
URL: https://github.com/apache/camel-k/issues/4290#issuecomment-1523892200
You were right. My feature branch was not rebased to the main branch. I can see the new `maxRunningBuilds` property now. Many thanks for the help! 🙏🏻
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] christophd commented on issue #4290: Maximum number of running builds (0) exceeded
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #4290:
URL: https://github.com/apache/camel-k/issues/4290#issuecomment-1523884380
The new property on the IntegrationPlatform is called `maxRunningBuilds` see https://github.com/apache/camel-k/blob/main/config/crd/bases/camel.apache.org_integrationplatforms.yaml#L245
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] mertdotcc commented on issue #4290: Maximum number of running builds (0) exceeded
Posted by "mertdotcc (via GitHub)" <gi...@apache.org>.
mertdotcc commented on issue #4290:
URL: https://github.com/apache/camel-k/issues/4290#issuecomment-1523968556
Another question: I see that the default value for `maxRunningBuilds` is set to 10. Is this something we will give the option to specify during the `kamel install` command with a flag maybe? Or is this something the users basically will go to and edit directly in the IntegrationPlatform resource?
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] christophd commented on issue #4290: Maximum number of running builds (0) exceeded
Posted by "christophd (via GitHub)" <gi...@apache.org>.
christophd commented on issue #4290:
URL: https://github.com/apache/camel-k/issues/4290#issuecomment-1523876699
This is a new enhancement to limit the maximum number of builds running on the operator in parallel. The enhancement has been merged today. The value `0` definitely does not make sense here.
The setting comes with the IntegrationPlatform custom resource. Can you please check that the IntegrationPlatform CRD has been updated on your local cluster?
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org