Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-3157

Showcase `latest` container image tag on quay.io/janus-idp is outdated

Prepare for Y ReleasePrepare for Z ReleaseRemove QuarterXMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • 1.3
    • None
    • Core platform, Upstream
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • Release Note Not Required
    • RHDH Core Team 3259

      Description of problem:

      How/when is the latest tag for quay.io/janus-idp/backstage-showcase updated?
      I noticed that this latest tag is 4 months old (and seems to match the 1.1 tag). It is supposed to be the latest stable version (1.2), no?

      Detected this because the operator nightly tests are failing due to a recent change in the default app-config Configuration to remove a deprecation warning in the logs, but this change will only work with 1.2+ (expected - see RHIDP-2716).

      The operator tests try to run against the latest stable Showcase image.

      Prerequisites (if any, like setup, operators/versions):

      • Operator on the main branch

      Steps to Reproduce

      git clone --depth 1 https://github.com/janus-idp/operator.git
      cd operator
      make deploy
      
      cat <<EOF | kubectl apply -f -               
      apiVersion: rhdh.redhat.com/v1alpha1
      kind: Backstage
      metadata:  
        name: my-backstage     
      EOF
      
      kubectl get pod -w
      

      Actual results:

      The application pod will end up crashing:

      $ kubectl get pod -w  
      NAME                                      READY   STATUS              RESTARTS   AGE
      backstage-my-backstage-86cd447485-ck62b   0/1     Init:0/1            0          17s
      backstage-psql-my-backstage-0             0/1     ContainerCreating   0          16s
      backstage-psql-my-backstage-0             0/1     Running             0          106s
      backstage-my-backstage-86cd447485-ck62b   0/1     Init:0/1            0          107s
      backstage-psql-my-backstage-0             1/1     Running             0          113s
      backstage-my-backstage-86cd447485-ck62b   0/1     PodInitializing     0          2m49s
      backstage-my-backstage-86cd447485-ck62b   0/1     Running             0          2m50s
      backstage-my-backstage-86cd447485-ck62b   0/1     Error               0          2m59s
      backstage-my-backstage-86cd447485-ck62b   0/1     Running             1 (2s ago)   3m
      backstage-my-backstage-86cd447485-ck62b   0/1     Error               1 (11s ago)   3m9s
      backstage-my-backstage-86cd447485-ck62b   0/1     CrashLoopBackOff    1 (6s ago)    3m14s
      

      Excerpt from the pod logs:

      /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1481
                throw new Error(
                      ^
      
      Error: Failed to instantiate service 'core.tokenManager' for 'search' because the factory function threw an error, Error: Failed to instantiate service 'core.tokenManager' because createRootContext threw an error, Error: You must configure at least one key in backend.auth.keys for production.
          at /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1481:17
          at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
          at async BackendInitializer.getInitDeps_fn (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1644:20)
          at async /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1779:32
          at async processNode (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1302:22)
          at async Promise.all (index 0)
          at async processMoreNodes (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1297:7)
          at async _DependencyGraph.parallelTopologicalTraversal (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1308:5)
          at async /opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1777:9
          at async Promise.all (index 4)
          at async BackendInitializer.doStart_fn (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1757:3)
          at async BackendInitializer.start (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1611:5)
          at async BackstageBackend.start (/opt/app-root/src/node_modules/@backstage/backend-app-api/dist/index.cjs.js:1881:5)
      
      Node.js v18.18.2
      

      Expected results:

      RHIDP-2716 changed the default configuration of the Operator to remove a deprecated configuration, but this change will only work with RHDH 1.2+, not 1.1

      The application pods will be created by default with the `quay.io/janus-idp/backstage-showcase:latest` image, and I noticed that this image was still matching the 1.1 tag.

      "latest" is supposed to be the latest stable version (so 1.2), no? In that case, it needs to be updated.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

              nickboldt Nick Boldt
              rh-ee-asoro Armel Soro
              RHIDP - Core Platform
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: