Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ready condition does not report errors if a deployment fails #4974

Closed
lburgazzoli opened this issue Dec 7, 2023 · 0 comments · Fixed by #5010
Closed

Ready condition does not report errors if a deployment fails #4974

lburgazzoli opened this issue Dec 7, 2023 · 0 comments · Fixed by #5010
Assignees
Labels
kind/bug Something isn't working

Comments

@lburgazzoli
Copy link
Contributor

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

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants