I would like to install DOOM at my Openshift Cluster

[preogon]

Hello Nick,

i am running an Openshift Cluster on VMware. I would like to install DOOM for a presentation -> To show my boss how cool Openshift is :-)

I was doing all the steps from your manual and got an error with this command:

oc new-app https://github.com/OpenShiftDemos/ocpdoom.git --name=ocpdoom -n oc

` oc new-app https://github.com/OpenShiftDemos/ocpdoom.git --name=ocpdoom -n ocpdoom warning: Cannot check if git requires authentication. error: unable to load template file "https://github.com/OpenShiftDemos/ocpdoom.git": error parsing https://github.com/OpenShiftDemos/ocpdoom.git: error converting YAML to JSON: yaml: line 30: mapping values are not allowed in this context error: local file access failed with: stat https://github.com/OpenShiftDemos/ocpdoom.git: no such file or directory error: unable to locate any images in image streams, templates loaded in accessible projects, template files, local docker images with name "https://github.com/OpenShiftDemos/ocpdoom.git"

Argument 'https://github.com/OpenShiftDemos/ocpdoom.git' was classified as an image, image~source, or loaded template reference.

The 'oc new-app' command will match arguments to the following types:

1. Images tagged into image streams in the current project or the 'openshift' project
   • if you don't specify a tag, we'll add ':latest'
2. Images in the container storage, on remote registries, or on the local container engine
3. Templates in the current project or the 'openshift' project
4. Git repository URLs or local paths that point to Git repositories

--allow-missing-images can be used to point to an image that does not exist yet.

`

FYI: Company Proxy Settings are set

[nickschuetz]

I suspect it's a network issue. Your firewall/proxy might be blocking access to https://github.com/OpenShiftDemos/ocpdoom.git. You could try doing the following to test from the same network you're running OpenShift on:

git clone https://github.com/OpenShiftDemos/ocpdoom.git

[preogon]

Thank you for answering :-)

I tried like you suggested : git clone was successfully.

 oc new-app ocpdoom --name=ocpdoom -n ocpdoom
warning: Cannot check if git requires authentication.
--> Found image b50c923 (20 hours old) in image stream "ocpdoom/fedora" under tag "37" for "fedora:37"

    * A Docker build using source code from https://github.com/OpenShiftDemos/ocpdoom.git#main will be created
      * The resulting image will be pushed to image stream tag "ocpdoom:latest"
      * Use 'oc start-build' to trigger a new build
      * WARNING: this source repository may require credentials.
                 Create a secret with your git credentials and use 'oc set build-secret' to assign it to the build config.

--> Creating resources ...
    imagestreamtag.image.openshift.io "ocpdoom:latest" created 
    buildconfig.build.openshift.io "ocpdoom" created 
    deployment.apps "ocpdoom" created 
--> Success 

This sentence makes me a little bit suspicious : " Create a secret with your git credentials and use 'oc set build-secret' to assign it to the build config."

Do I need a build-secret for the creation? Because your repo is public.

[nickschuetz]

No you should not need to create a build secret. It looks to me like your oc new-app command succeeded. Did the source code not get pulled? Did the build not succeed? Check the following:

oc logs bc/ocpdoom -f -n ocpdoom

If all is well move on to the next steps.

[preogon]

i tried this command ;

oc get pods -n ocpdoom
NAME                     READY   STATUS      RESTARTS   AGE
novnc-1-build            0/1     Completed   0          13h
novnc-569698c498-bz44b   1/1     Running     0          13h
ocpdoom-1-build          0/1     Error       0          13h
ocpdoom-2-build          1/1     Running     0          25m

The Pod from deployment ocpdoom wont deploy:

oc get deployments -n ocpdoom
NAME      READY   UP-TO-DATE   AVAILABLE   AGE
novnc     1/1     1            1           14h
ocpdoom   0/1     0            0           8m15s

There is also no image at the doom deployment:

-> Output from oc edit deployment/ocpdoom -o yaml -n ocpdoom

apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
    image.openshift.io/triggers: '[{"from":{"kind":"ImageStreamTag","name":"ocpdoom:latest"},"fieldPath":"spec.template.spec.containers[?(@.name==\"ocpdoom\")].image"}]'
    openshift.io/generated-by: OpenShiftNewApp
  creationTimestamp: "2023-07-07T06:15:04Z"
  generation: 1
  labels:
    app: ocpdoom
    app.kubernetes.io/component: ocpdoom
    app.kubernetes.io/instance: ocpdoom
  name: ocpdoom
  namespace: ocpdoom
  resourceVersion: "4653991"
  uid: ea752efd-39b1-41c6-be69-3c0bd36ebaa3
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      deployment: ocpdoom
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      annotations:
        openshift.io/generated-by: OpenShiftNewApp
      creationTimestamp: null
      labels:
        deployment: ocpdoom
    spec:
      containers:
      - image: ' '
        imagePullPolicy: IfNotPresent
        name: ocpdoom
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30
status:
  conditions:
  - lastTransitionTime: "2023-07-07T06:15:04Z"
    lastUpdateTime: "2023-07-07T06:15:04Z"
    message: Deployment does not have minimum availability.
    reason: MinimumReplicasUnavailable
    status: "False"
    type: Available
  - lastTransitionTime: "2023-07-07T06:15:04Z"
    lastUpdateTime: "2023-07-07T06:15:04Z"
    message: 'Pod "ocpdoom-7f9df4677-mdzwp" is invalid: spec.containers[0].image:
      Invalid value: " ": must not have leading or trailing whitespace'
    reason: FailedCreate
    status: "True"

My firewall colleague checked the logs at the firewall: Yes there were some blockings, but he set a temporary exception. No positive results -> I deleted ocpdoom deployment, buildconfig, imagestream at -n ocpdoom and entered the new-app command again....