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

Scaling: is not working with OpenShift 3.4 (CDK 2.4)

XMLWordPrintable

    • devex #127 February 2017
    • 4
    • Hide

      ASSERT: Have CDK 2.4 running
      ASSERT: Have OS3 connection, project and application created (I used nodejs-example)
      ASSERT: When this application is created it is configured to have one pod.
      EXEC: Select Scale -> Up or Scale -> Scale to... (it doesn't matter if you do this on the pod or the service or in properties view)
      ASSERT: Desired number of pods should spin up and after a while they should be running.
      FAIL: Desired number of pods are spun up, but they are immediately terminated. Only the original one is kept.

      Show
      ASSERT: Have CDK 2.4 running ASSERT: Have OS3 connection, project and application created (I used nodejs-example) ASSERT: When this application is created it is configured to have one pod. EXEC: Select Scale -> Up or Scale -> Scale to... (it doesn't matter if you do this on the pod or the service or in properties view) ASSERT: Desired number of pods should spin up and after a while they should be running. FAIL: Desired number of pods are spun up, but they are immediately terminated. Only the original one is kept.

      Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now).
      When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again.

      This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4).

            adietish@redhat.com André Dietisheim
            rhopp@redhat.com Radim Hopp
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: