new-app can't find imagestream for Jenkins

[SoukainaKhalkhouliIBM]

we are using this template to create a jenkins pod but while creating new app jenkins pods is not creating:

Template code:

apiVersion: template.openshift.io/v1
kind: Template
parameters:

• description: The name of the OpenShift Service exposed for the Jenkins container.
  displayName: Jenkins Service Name
  name: JENKINS_SERVICE_NAME
  value: jenkins
• description: The name of the service used for master/slave communication.
  displayName: Jenkins JNLP Service Name
  name: JNLP_SERVICE_NAME
  value: jenkins-jnlp
• description: Whether to enable OAuth OpenShift integration. If false, the static account 'admin' will be initialized with the password 'password'.
  displayName: Enable OAuth in Jenkins
  name: ENABLE_OAUTH
  value: 'true'
• description: Volume space available for data, e.g. 512Mi, 2Gi.
  displayName: Volume Capacity
  name: VOLUME_CAPACITY
  required: true
  value: 2Gi
• description: The OpenShift Namespace where the Jenkins ImageStream resides.
  displayName: Jenkins ImageStream Namespace
  name: NAMESPACE
  value: openshift
• description: Whether to perform memory intensive, possibly slow, synchronization with the Jenkins Update Center on start. If true, the Jenkins core update monitor and site warnings monitor are disabled.
  displayName: Disable memory intensive administrative monitors
  name: DISABLE_ADMINISTRATIVE_MONITORS
  value: 'false'
• description: Name of the ImageStreamTag to be used for the Jenkins image.
  displayName: Jenkins ImageStreamTag
  name: JENKINS_IMAGE_STREAM_TAG
  value: jenkins:2
• description: When a fatal error occurs, an error log is created with information and the state obtained at the time of the fatal error.
  displayName: Fatal Error Log File
  name: ENABLE_FATAL_ERROR_LOG_FILE
  value: 'false'
• description: The amount of CPU to request.
  displayName: CPU request
  name: CPU_REQUEST
  required: true
  value: '0.7'
• description: The amount of memory required for the container to run.
  displayName: Memory request
  name: MEMORY_REQUEST
  required: true
  value: 512Mi
• description: The amount of CPU the container is limited to use.
  displayName: CPU limit
  name: CPU_LIMIT
  required: true
  value: '1'
• description: Maximum amount of memory the container can use.
  displayName: Memory Limit
  name: MEMORY_LIMIT
  value: 512Mi
• description: The Time Zone of Country
  dispalyName: Time Zone
  name: TZ
  required: true
  value: 'America/Sao_Paulo'
  labels:
  app: jenkins-persistent
  template: jenkins-persistent-template
  message: A Jenkins service has been created in your project. Log into Jenkins with
  your OpenShift account. The tutorial at https://github.com/openshift/origin/blob/master/examples/jenkins/README.md
  contains more information about using this template.
  metadata:
  annotations:
  description: |-
  Jenkins service, with persistent storage.
  NOTE: You must have persistent volumes available in your cluster to use this template.
  iconClass: icon-jenkins
  openshift.io/display-name: Jenkins
  openshift.io/documentation-url: https://docs.okd.io/latest/using_images/other_images/jenkins.html
  openshift.io/long-description: This template deploys a Jenkins server capable
  of managing OpenShift Pipeline builds and supporting OpenShift-based oauth login.
  openshift.io/provider-display-name: Red Hat, Inc.
  openshift.io/support-url: https://access.redhat.com
  tags: instant-app,jenkins
  name: jenkins-persistent
  objects:
• apiVersion: v1
  kind: Route
  metadata:
  annotations:
  haproxy.router.openshift.io/timeout: 4m
  template.openshift.io/expose-uri: http://{.spec.host}{.spec.path}
  name: "${JENKINS_SERVICE_NAME}"
  spec:
  tls:
  insecureEdgeTerminationPolicy: Redirect
  termination: edge
  to:
  kind: Service
  name: "${JENKINS_SERVICE_NAME}"
• apiVersion: v1
  kind: PersistentVolumeClaim
  metadata:
  name: "${JENKINS_SERVICE_NAME}"
  spec:
  accessModes:
  • ReadWriteOnce
    resources:
    requests:
    storage: "${VOLUME_CAPACITY}"
• apiVersion: v1
  kind: DeploymentConfig
  metadata:
  annotations:
  template.alpha.openshift.io/wait-for-ready: 'true'
  name: "${JENKINS_SERVICE_NAME}"
  spec:
  replicas: 1
  selector:
  name: "${JENKINS_SERVICE_NAME}"
  strategy:
  type: Recreate
  template:
  metadata:
  labels:
  name: "${JENKINS_SERVICE_NAME}"
  spec:
  containers:
  - capabilities: {}
  env:
  - name: OPENSHIFT_ENABLE_OAUTH
  value: "${ENABLE_OAUTH}"
  - name: OPENSHIFT_ENABLE_REDIRECT_PROMPT
  value: 'true'
  - name: DISABLE_ADMINISTRATIVE_MONITORS
  value: "${DISABLE_ADMINISTRATIVE_MONITORS}"
  - name: KUBERNETES_MASTER
  value: https://kubernetes.default:443
  - name: KUBERNETES_TRUST_CERTIFICATES
  value: 'true'
  - name: JENKINS_SERVICE_NAME
  value: "${JENKINS_SERVICE_NAME}"
  - name: JNLP_SERVICE_NAME
  value: "${JNLP_SERVICE_NAME}"
  - name: ENABLE_FATAL_ERROR_LOG_FILE
  value: "${ENABLE_FATAL_ERROR_LOG_FILE}"
  - name: TZ
  value: "${TIME_ZONE}"
  image: " "
  imagePullPolicy: IfNotPresent
  livenessProbe:
  failureThreshold: 2
  httpGet:
  path: "/login"
  port: 8080
  initialDelaySeconds: 420
  periodSeconds: 360
  timeoutSeconds: 240
  name: jenkins
  readinessProbe:
  httpGet:
  path: "/login"
  port: 8080
  initialDelaySeconds: 3
  timeoutSeconds: 240
  resources:
  limits:
  cpu: '${CPU_LIMIT}'
  memory: '${MEMORY_LIMIT}'
  requests:
  cpu: '${CPU_REQUEST}'
  memory: '${MEMORY_REQUEST}'
  securityContext:
  capabilities: {}
  privileged: false
  terminationMessagePath: "/dev/termination-log"
  volumeMounts:
  - mountPath: "/var/lib/jenkins"
  name: "${JENKINS_SERVICE_NAME}-data"
  dnsPolicy: ClusterFirst
  restartPolicy: Always
  serviceAccountName: "${JENKINS_SERVICE_NAME}"
  volumes:
  - name: "${JENKINS_SERVICE_NAME}-data"
  persistentVolumeClaim:
  claimName: "${JENKINS_SERVICE_NAME}"
  triggers:
  • imageChangeParams:
    automatic: true
    containerNames:
    • jenkins
      from:
      kind: ImageStreamTag
      name: "${JENKINS_IMAGE_STREAM_TAG}"
      namespace: "non-root-image-builds"
      lastTriggeredImage: " "
      type: ImageChange
  • type: ConfigChange
• apiVersion: v1
  kind: ServiceAccount
  metadata:
  annotations:
  serviceaccounts.openshift.io/oauth-redirectreference.jenkins: '{"kind":"OAuthRedirectReference","apiVersion":"v1","reference":{"kind":"Route","name":"${JENKINS_SERVICE_NAME}"}}'
  name: "${JENKINS_SERVICE_NAME}"
• apiVersion: v1
  groupNames:
  kind: RoleBinding
  metadata:
  name: "${JENKINS_SERVICE_NAME}_edit"
  roleRef:
  name: edit
  subjects:
  • kind: ServiceAccount
    name: "${JENKINS_SERVICE_NAME}"
• apiVersion: v1
  kind: Service
  metadata:
  name: "${JNLP_SERVICE_NAME}"
  spec:
  ports:
  • name: agent
    nodePort: 0
    port: 50000
    protocol: TCP
    targetPort: 50000
    selector:
    name: "${JENKINS_SERVICE_NAME}"
    sessionAffinity: None
    type: ClusterIP
• apiVersion: v1
  kind: Service
  metadata:
  annotations:
  service.alpha.openshift.io/dependencies: '[{"name": "${JNLP_SERVICE_NAME}",
  "namespace": "", "kind": "Service"}]'
  service.openshift.io/infrastructure: 'true'
  name: "${JENKINS_SERVICE_NAME}"
  spec:
  ports:
  • name: web
    nodePort: 0
    port: 80
    protocol: TCP
    targetPort: 8080
    selector:
    name: "${JENKINS_SERVICE_NAME}"
    sessionAffinity: None
    type: ClusterIP

$oc status:

% oc status
In project non-root-image-builds on server https://c114-e.us-south.containers.cloud.ibm.com:32006

svc/jenkins-jnlp - 172.21.102.186:50000
https://jenkins-non-root-image-builds.macys-nonprod-cluster-9f573d67fe84a8f4a076f7f5505127b4-0000.us-south.containers.appdomain.cloud (redirects) (svc/jenkins)
dc/jenkins deploys istag/jenkins:2
deployment #1 waiting on image or update

bc/non-root-jenkins-agent-base docker builds uploaded code
-> istag/non-root-jenkins-agent-base:latest
build #1 succeeded 3 hours ago

bc/non-root-jenkins-agent-python docker builds uploaded code
-> istag/non-root-jenkins-agent-python:latest
build #1 succeeded 3 hours ago

Errors:

• The image trigger for dc/jenkins will have no effect because is/jenkins does not exist.

View details with 'oc describe /' or list resources with 'oc get all'.
soukainakhalkhouli@Soukainas-MacBook-Pro-2 jenkins % oc get service registry
Error from server (NotFound): services "registry" not found
soukainakhalkhouli@Soukainas-MacBook-Pro-2 jenkins % oc status
In project non-root-image-builds on server https://c114-e.us-south.containers.cloud.ibm.com:32006

svc/jenkins-jnlp - 172.21.102.186:50000
https://jenkins-non-root-image-builds.macys-nonprod-cluster-9f573d67fe84a8f4a076f7f5505127b4-0000.us-south.containers.appdomain.cloud (redirects) (svc/jenkins)
dc/jenkins deploys istag/jenkins:2
deployment #1 waiting on image or update

bc/non-root-jenkins-agent-base docker builds uploaded code
-> istag/non-root-jenkins-agent-base:latest
build #1 succeeded 3 hours ago

bc/non-root-jenkins-agent-python docker builds uploaded code
-> istag/non-root-jenkins-agent-python:latest
build #1 succeeded 3 hours ago

Errors:

• The image trigger for dc/jenkins will have no effect because is/jenkins does not exist.

View details with 'oc describe /' or list resources with 'oc get all'.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.