Uploaded image for project: 'Knative Serving'
  1. Knative Serving
  2. SRVKS-674

Revision gets stuck in ResolvingDigests step

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 1.12.0
    • None
    • None
    • False
    • False
    • Undefined
    • Serverless Sprint 193

      Steps to reproduce:
      a) Install OCP 4.6.6 (cluster bot)
      b) Install Serving, Kourier following upstream instructions here as usual.
      Launch a service in any ns:

      apiVersion: serving.knative.dev/v1
      kind: Service
      metadata:
      name: event-display
      spec:
      template:
      spec:
      containers:

      • image: quay.io/openshift-knative/knative-eventing-sources-event-display

      Revision gets stuck and no service pod comes up:

      Name: event-display-00001
      Namespace: default
      Labels: serving.knative.dev/configuration=event-display
      serving.knative.dev/configurationGeneration=1
      serving.knative.dev/routingState=active
      serving.knative.dev/service=event-display
      Annotations: serving.knative.dev/creator: system:admin
      serving.knative.dev/routes: event-display
      serving.knative.dev/routingStateModified: 2020-12-02T16:01:15Z
      API Version: serving.knative.dev/v1
      Kind: Revision
      Metadata:
      Creation Timestamp: 2020-12-02T16:01:15Z
      Generation: 1
      Managed Fields:
      API Version: serving.knative.dev/v1
      Fields Type: FieldsV1
      fieldsV1:
      f:metadata:
      f:annotations:
      .:
      f:serving.knative.dev/creator:
      f:serving.knative.dev/routes:
      f:serving.knative.dev/routingStateModified:
      f:labels:
      .:
      f:serving.knative.dev/configuration:
      f:serving.knative.dev/configurationGeneration:
      f:serving.knative.dev/routingState:
      f:serving.knative.dev/service:
      f:ownerReferences:
      .:
      k:
      Unknown macro: {"uid"}
      :
      .:
      f:apiVersion:
      f:blockOwnerDeletion:
      f:controller:
      f:kind:
      f:name:
      f:uid:
      f:spec:
      .:
      f:containerConcurrency:
      f:containers:
      f:enableServiceLinks:
      f:timeoutSeconds:
      f:status:
      .:
      f:conditions:
      f:observedGeneration:
      Manager: controller
      Operation: Update
      Time: 2020-12-02T16:01:15Z
      Owner References:
      API Version: serving.knative.dev/v1
      Block Owner Deletion: true
      Controller: truehttps://knative.dev/docs/install/any-kubernetes-cluster​_
      Kind: Configuration
      Name: event-display
      UID: 80261e6a-b302-41db-98a9-b0cef3f5b187
      Resource Version: 46845
      Self Link: /apis/serving.knative.dev/v1/namespaces/default/revisions/event-display-00001
      UID: b7ae07f2-7f50-47ec-bd5b-0c2757cab632
      Spec:
      Container Concurrency: 0
      Containers:
      Image: quay.io/openshift-knative/knative-eventing-sources-event-display
      Name: user-container
      Readiness Probe:
      Success Threshold: 1
      Tcp Socket:
      Port: 0
      Resources:
      Enable Service Links: false
      Timeout Seconds: 300
      Status:
      Conditions:
      Last Transition Time: 2020-12-02T16:01:15Z
      Status: Unknown
      Type: ContainerHealthy
      Last Transition Time: 2020-12-02T16:01:15Z
      Reason: ResolvingDigests
      Status: Unknown
      Type: Ready
      Last Transition Time: 2020-12-02T16:01:15Z
      Reason: ResolvingDigests
      Status: Unknown
      Type: ResourcesAvailable
      Observed Generation: 1
      Events: <none>

              skontopo@redhat.com Stavros Kontopoulos
              skontopo@redhat.com Stavros Kontopoulos
              Chris Suszynski Chris Suszynski
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: