Bug 2095701 - Sample container images was not available on airgap infra, importing Samples in DevConsole fails
Summary: Sample container images was not available on airgap infra, importing Samples ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Samples
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: David Peraza
QA Contact: Jitendar Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-10 09:29 UTC by Jaivardhan Kumar
Modified: 2022-10-24 14:57 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-19 11:14:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaivardhan Kumar 2022-06-10 09:29:38 UTC
Description of problem: Cannot create deployment using DevConsole workflow under airgap infra

can see more details here https://issues.redhat.com/browse/CRW-3044

Version-Release number of selected component (if applicable):


How reproducible: 


Steps to Reproduce:
1. Login as a regular user in the airgap cluster
2. Under developer perspective click on +Add menu
3. Select the predefined sample: click on the Samples -> Create an Application 
   from a code sample
4. Waiting for loading of the sample list and select Java sample. Click create 
   button
5. Click on the App icon and click on the Start Build button


Actual results: Error "Error resolving ImageStreamTag java:openjdk-17-ubi8 in namespace openshift: unable to find latest tagged image" for field "from"


Expected results: Pod should be created and app. should start building


Additional info:

Comment 1 Christoph Jerolimov 2022-06-21 15:05:40 UTC
Looks like the samples operator could not import all the required resources. The ImageStreams are there, but some (not all!) ImageStreamTags are missed:

➜  ~ oc get imagestreams -n openshift | grep ruby                 
NAME                                                 IMAGE REPOSITORY                                                                                                TAGS                                                  UPDATED
ruby                                                 image-registry.openshift-image-registry.svc:5000/openshift/ruby                                                 2.7-ubi7,2.7-ubi8,3.0-ubi8,latest + 6 more...         3 weeks ago

➜  ~ oc get imagestreamtags -n openshift | grep ruby
NAME                                   IMAGE REFERENCE
ruby:2.7-ubi8                          image-registry.openshift-image-registry.svc:5000/openshift/ruby@sha256:..
ruby:3.0-ubi8                          image-registry.openshift-image-registry.svc:5000/openshift/ruby@sha256:..
ruby:latest                            image-registry.openshift-image-registry.svc:5000/openshift/ruby@sha256:..
ruby:2.7-ubi7                          image-registry.openshift-image-registry.svc:5000/openshift/ruby@sha256:..

You can see an error message also when checking `openshift-samples` `ClusterOperator` resource:

      message: >-
        Samples installed at 4.10.0-0.nightly-2022-05-24-195211, with image
        import failures for these imagestreams:
        jboss-eap74-openjdk11-openshift,fuse7-java11-openshift,jboss-webserver56-openjdk11-tomcat9-openshift-ubi8,sso75-openshift-rhel8,httpd,fuse7-eap-openshift-java11,ubi8-openjdk-8-runtime,ruby,jboss-eap-xp3-openjdk11-openshift,java-runtime,jboss-webserver56-openjdk8-tomcat9-openshift-ubi8,jboss-eap74-openjdk8-openshift,ubi8-openjdk-11-runtime,fuse7-karaf-openshift-jdk11,openshift-service-ca.crt,jboss-eap-xp3-openjdk11-runtime-openshift,jboss-eap74-openjdk8-runtime-openshift,kube-root-ca.crt,jboss-eap74-openjdk11-runtime-openshift;
        last import attempt 2022-05-25 08:02:08 +0000 UTC
      reason: FailedImageImports
      status: 'False'
      type: Progressing

This doesn't look like an UI issue. A good place to get input on this might be #forum-app-services


Note You need to log in before you can comment on or make changes to this bug.