Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-37091

There should be an error when osus instance not in same namespace with osus operator

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When installing osus instance in a different namespace from osus operator, there are no error to indicate the pod could not be created.
          

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

      
          

      How reproducible:

      always
          

      Steps to Reproduce:

          1. install osus operator in namespace `install-osus-here`
          2. install osus instance in another namespace, like `openshift-update-service`
          3.
          

      Actual results:

      updateservices was created without any pod :
      
      [jianl@jianl-thinkpadt14gen4 416]$ oc get updateservices/service -n openshift-update-service -o yaml
      apiVersion: updateservice.operator.openshift.io/v1
      kind: UpdateService
      metadata:
        creationTimestamp: "2024-07-16T08:57:16Z"
        generation: 1
        name: service
        namespace: openshift-update-service
        resourceVersion: "54411"
        uid: 0f18f3b5-5ca6-46cc-b02e-222c60e68ca8
      spec:
        graphDataImage: quay.io/openshifttest/graph-data:latest
        releases: quay.io/openshift-release-dev/ocp-release
        replicas: 1
      [jianl@jianl-thinkpadt14gen4 416]$ 
          

      Expected results:

      Should be an error in status section in service
          

      Additional info:

      
          

              hongkliu Hongkai Liu
              rhn-support-jianl Jian Li
              Jian Li Jian Li
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: