[jbosstools-issues] [JBoss JIRA] (JBIDE-11314) OpenShift: delayed application creation
[
https://issues.jboss.org/browse/JBIDE-11314?page=com.atlassian.jira.plugi...
]
Isaac Rooskov updated JBIDE-11314:
----------------------------------
Release Notes Text: 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. (was: Previously a
user ran into an error dialog when the application wizard had timed out. He then could
only cancel the creation wizard and use the import wizard to add the application to his
workspace. A new dialog box has since been added that asks a user if he'd wish to
continue waiting for the remote application to become reachable or to close the wizard.
This ensures that the user doesn't get stuck while creating and importing his
OpenShift application.)
OpenShift: delayed application creation
---------------------------------------
Key: JBIDE-11314
URL: https://issues.jboss.org/browse/JBIDE-11314
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Stefan Bunciak
Assignee: Andre Dietisheim
Priority: Blocker
Labels: new_and_noteworthy
Fix For: 3.3.0.CR1
Attachments: keep-creating.png, keep-waiting.png
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:
{quote}
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)
{quote}
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?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira