Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-23358

OpenShift Explorer: Pod status is not reflecting reality

XMLWordPrintable

    • devex #122 October 2016
    • 8
    • Hide

      ASSERT: Have an OpenShift connection with a project and a docker connection with a local image.
      EXEC: in Docker Explorer: Select the docker image and select its context menu item Deploy to OpenShift.
      EXEC: Proceed through Deploy Image to OpenShift wizard but do not push image to OpenShift registry.

      RESULT: Deployment fails and status of pods is Crash loop back off, but status of pod in OpenShift Explorer is still Running.
      EXPECTED RESULT: Status of failed pod in OpenShift explorer reflects reality.

      Show
      ASSERT: Have an OpenShift connection with a project and a docker connection with a local image. EXEC: in Docker Explorer: Select the docker image and select its context menu item Deploy to OpenShift. EXEC: Proceed through Deploy Image to OpenShift wizard but do not push image to OpenShift registry. RESULT: Deployment fails and status of pods is Crash loop back off, but status of pod in OpenShift Explorer is still Running. EXPECTED RESULT: Status of failed pod in OpenShift explorer reflects reality.

      When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods". Refresh of a project or service does not help.

            dbocharo@redhat.com Dmitrii Bocharov (Inactive)
            mlabuda_jira Marián Labuda (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: