[jbosstools-issues] [JBoss JIRA] (JBIDE-11849) OpenShift: catrtidge not embedded when creating scaled application

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694290#comment-12694290 ] 

Andre Dietisheim commented on JBIDE-11849:
------------------------------------------

The wizard actually does 3 things:

- creates the application
- waits for the DNS to resolve the new app
- waits for the application to become available

So there's nothing valid you could deduce from looking at the web-UI and seeing your app there even though JBDS still says "creating". You can even see the exact same thing when having 2 eclipses or even 2 web-UIs looking at the very same openshift account. 

What's a valid point IMHO is that creating a scalable app takes far more time, so timeouts are by far more likely. This urgens JBIDE-11314 even more.
                
> OpenShift: catrtidge not embedded when creating scaled application
> ------------------------------------------------------------------
>
>                 Key: JBIDE-11849
>                 URL: https://issues.jboss.org/browse/JBIDE-11849
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 3.3.0.Beta3
>         Environment: OpenShift VIP account (10 gears)
>            Reporter: Stefan Bunciak
>            Assignee: Andre Dietisheim
>            Priority: Critical
>             Fix For: 3.3.0.CR1
>
>         Attachments: scale.png, scale2.png, scale3.png
>
>
> h4. Tried to create medium gear application, scaled, with MySQL:
> h5. Application configuration page
> * !scale.png|thumbnail!
> h5. Application is created on OpenShift, but JBDS still says 'creating'
> * !scale2.png|thumbnail!
> h5. NO MySQL cartridge embedded:
> * !scale3.png|thumbnail!
> h5. Further more I got 3/3 times a Read timeout error described in JBIDE-11314 and JBIDE-11314

--
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