You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "lburgazzoli (via GitHub)" <gi...@apache.org> on 2023/12/07 09:12:19 UTC
[I] Ready condition does not report errors if a deployment fails [camel-k]
lburgazzoli opened a new issue, #4974:
URL: https://github.com/apache/camel-k/issues/4974
### What happened?
I've installed camel-k upstream in an OpenShift instance on IBM Cloud and when deploying an integration to a brand new namespace, the integration fails, hence the Ready condition is set to False, however no reason or message is given.
### Steps to reproduce
1. install camel-k upstream (2.x) in an OpenShift instance on IBM Cloud
2. create a brand new namespace
3. deploy a simple integration to the newly created namespace
### Relevant log output
```shell
Integration conditions:
conditions:
- firstTruthyTime: '2023-12-07T08:59:20Z'
lastTransitionTime: '2023-12-07T08:59:20Z'
lastUpdateTime: '2023-12-07T08:59:20Z'
message: openshift-operators/camel-k
reason: IntegrationPlatformAvailable
status: 'True'
type: IntegrationPlatformAvailable
- firstTruthyTime: '2023-12-07T08:59:20Z'
lastTransitionTime: '2023-12-07T08:59:20Z'
lastUpdateTime: '2023-12-07T08:59:20Z'
message: kit-clo6phlsqkl925kh59bg
reason: IntegrationKitAvailable
status: 'True'
type: IntegrationKitAvailable
- lastTransitionTime: '2023-12-07T08:59:20Z'
lastUpdateTime: '2023-12-07T08:59:20Z'
message: different controller strategy used (deployment)
reason: CronJobNotAvailableReason
status: 'False'
type: CronJobAvailable
- firstTruthyTime: '2023-12-07T08:59:20Z'
lastTransitionTime: '2023-12-07T08:59:20Z'
lastUpdateTime: '2023-12-07T08:59:20Z'
message: deployment name is example
reason: DeploymentAvailable
status: 'True'
type: DeploymentAvailable
- lastTransitionTime: '2023-12-07T08:59:20Z'
lastUpdateTime: '2023-12-07T08:59:20Z'
message: no http service required
reason: ServiceNotAvailable
status: 'False'
type: ServiceAvailable
- firstTruthyTime: '2023-12-07T08:59:20Z'
lastTransitionTime: '2023-12-07T08:59:20Z'
lastUpdateTime: '2023-12-07T08:59:20Z'
message: integration(jolokia/8778)
reason: JolokiaAvailable
status: 'True'
type: JolokiaAvailable
- lastTransitionTime: '2023-12-07T08:59:20Z'
lastUpdateTime: '2023-12-07T08:59:20Z'
message: no target service found
reason: RouteNotAvailable
status: 'False'
type: ExposureAvailable
- lastTransitionTime: '2023-12-07T08:59:20Z'
lastUpdateTime: '2023-12-07T08:59:20Z'
status: 'False'
type: Ready
```
Related deployment conditions
```
conditions:
- type: Available
status: 'False'
lastUpdateTime: '2023-12-07T08:59:20Z'
lastTransitionTime: '2023-12-07T08:59:20Z'
reason: MinimumReplicasUnavailable
message: Deployment does not have minimum availability.
- type: ReplicaFailure
status: 'True'
lastUpdateTime: '2023-12-07T08:59:20Z'
lastTransitionTime: '2023-12-07T08:59:20Z'
reason: FailedCreate
message: >-
pods "example-785f95d488-" is forbidden: unable to validate against any
security context constraint:
[pod.metadata.annotations[container.seccomp.security.alpha.kubernetes.io/integration]:
Forbidden: seccomp may not be set, provider restricted-v2:
.containers[0].runAsUser: Invalid value: 1000420000: must be in the
ranges: [1000650000, 1000659999], provider "restricted": Forbidden: not
usable by user or serviceaccount, provider "ibm-restricted-scc":
Forbidden: not usable by user or serviceaccount, provider "nonroot-v2":
Forbidden: not usable by user or serviceaccount, provider "nonroot":
Forbidden: not usable by user or serviceaccount, provider
"ibm-anyuid-scc": Forbidden: not usable by user or serviceaccount,
provider "hostmount-anyuid": Forbidden: not usable by user or
serviceaccount, provider "ibm-anyuid-hostpath-scc": Forbidden: not
usable by user or serviceaccount, provider "hostnetwork-v2": Forbidden:
not usable by user or serviceaccount, provider "hostnetwork": Forbidden:
not usable by user or serviceaccount, provider "hostaccess": Forbidden:
not usable by user or serviceaccount, provider
"ibm-anyuid-hostaccess-scc": Forbidden: not usable by user or
serviceaccount, provider "node-exporter": Forbidden: not usable by user
or serviceaccount, provider "ibm-privileged-scc": Forbidden: not usable
by user or serviceaccount, provider "privileged": Forbidden: not usable
by user or serviceaccount]
```
```
### Camel K version
2.x
--
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
Re: [I] Ready condition does not report errors if a deployment fails [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #4974: Ready condition does not report errors if a deployment fails
URL: https://github.com/apache/camel-k/issues/4974
--
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