Uploaded image for project: 'JBoss Web Server'
  1. JBoss Web Server
  2. JWS-2536

Missing status information in Operator 2.0.0

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • Operator.2.0.0.GA
    • None
    • cloud
    • None
    • False
    • None
    • False
    • Hide

      kubectl get webserver -o yaml

      This is what is missing from perator 2.0.0:

       
      hosts:

      • jws-app-ktsagara-operator-test.apps.jws-qe-gymi.dynamic.xpaas
        pods:
      • name: jws-app-5b96986c7d-45zj9
        podIP: 10.129.2.131
        state: ACTIVE
      • name: jws-app-5b96986c7d-ktz2l
        podIP: 10.131.0.137
        state: ACTIVE
        replicas: 2
        scalingdownPods: 0
         
         
        These are the web servers yaml files:
        webserver-pod-test-2.0.0.yaml
        webserver-pod-test-1.2.4.yaml
      •  
      Show
      kubectl get webserver -o yaml This is what is missing from perator 2.0.0:   hosts: jws-app-ktsagara-operator-test.apps.jws-qe-gymi.dynamic.xpaas pods: name: jws-app-5b96986c7d-45zj9 podIP: 10.129.2.131 state: ACTIVE name: jws-app-5b96986c7d-ktz2l podIP: 10.131.0.137 state: ACTIVE replicas: 2 scalingdownPods: 0     These are the web servers yaml files: webserver-pod-test-2.0.0.yaml webserver-pod-test-1.2.4.yaml  

      Status information in the yaml file of the operator's webserver is missing. I can't see the pod's status with cli as well. 
       

              rhn-engineering-jclere Jean-Frederic Clere
              ktsagara@redhat.com Katerina Tsagaraki (Inactive)
              Katerina Tsagaraki Katerina Tsagaraki (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: