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

OpenShift: delayed application creation

    XMLWordPrintable

Details

    • Hide
      Previously a user ran into an error dialog when the application wizard had timed out. For the application to appear in the workspace, a user had to cancel the creation wizard and use the import wizard. To correct this issue a new dialog box has been added that allows a user to wait for the remote application to become reachable or to close the wizard. This ensures that the user has a way of closing the OpenShift application creation wizard without requiring the import wizard after.
      Show
      Previously a user ran into an error dialog when the application wizard had timed out. For the application to appear in the workspace, a user had to cancel the creation wizard and use the import wizard. To correct this issue a new dialog box has been added that allows a user to wait for the remote application to become reachable or to close the wizard. This ensures that the user has a way of closing the OpenShift application creation wizard without requiring the import wizard after.
    • Documented as Feature Request

    Description

      We should discuss how should the wizard behave when the application is not created in time-out, but e.g. few seconds later, this exception is thrown:

      com.openshift.express.client.OpenShiftApplicationNotAvailableException: We werent able to lookup your hostname (https://as11-adomain.rhcloud.com/) in a reasonable amount of time. This can happen periodically and will just take an extra minute or two to propagate depending on where you are in the world.
      Once you are able to access your application in a browser, you can then clone your git repository.
      If you cant get your application running in the browser, you can also try destroying and recreating the application as well using this Wizard.

      If this doesnt work for you, let us know in the forums or in IRC and well make sure to get you up and running.

      Forums: https://www.redhat.com/openshift/forums/express

      IRC: #openshift (on Freenode)
      at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.waitForAccessible(OpenShiftExpressApplicationWizardModel.java:341)
      at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.createApplication(OpenShiftExpressApplicationWizardModel.java:353)
      at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.createApplication(OpenShiftExpressApplicationWizardModel.java:359)
      at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizard$3.run(OpenShiftExpressApplicationWizard.java:195)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

      So the user needs to close the wizard and import the application via console or import wizard. Otherwise, when he tries to click Finish button again he gets another exception that the application already exists on OpenShift.

      Should the wizard rely on the fix time-out?

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-11848 Frequent read timeouts when embedding cartridges / creating applications

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-10607 Cannot import application if I previously killed and recreated it

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-11237 Error message changes for the case when newly created application does not respond

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              adietish@redhat.com André Dietisheim
              sbunciak-rh Stefan Bunciak
              Isaac Rooskov Isaac Rooskov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: