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

Openshift explorer: pods are shown twice, if you have only a rc, no dc for your app

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 4.6.0.AM3
    • None
    • openshift
    • Hide

      The same as for https://issues.jboss.org/browse/JBIDE-24979:

      1. ASSERT: make sure that you have an app that has NO deployment config, just a replication controller
        (EXEC: if you dont, create it via the attached custom template eap-without-service-nor-deploymentconfig.json)
      2. EXEC: in OpenShift explorer: select the pod for your rc, pick "Scale > Up" or "Scale > Down" or "Scale > To"
      Show
      The same as for https://issues.jboss.org/browse/JBIDE-24979: ASSERT: make sure that you have an app that has NO deployment config, just a replication controller (EXEC: if you dont, create it via the attached custom template eap-without-service-nor-deploymentconfig.json ) EXEC: in OpenShift explorer: select the pod for your rc, pick "Scale > Up" or "Scale > Down" or "Scale > To"

    Description

      Also see discussion for the corresponding PR: https://github.com/jbosstools/jbosstools-openshift/pull/1748

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-26084 Explorer: pods are show twice if they're controlled by an rc (no dc, no service)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-24979 Scale up/down/to: NPE if you have only a rc, no dc for your app

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              adietish@redhat.com André Dietisheim
              dbocharo@redhat.com Dmitrii Bocharov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: