[jbosstools-issues] [JBoss JIRA] (JBIDE-13729) Error trying to embed HAProxy into scaled application: HAProxy not listed in embedded cartridges (OpenShift Explorer, Add/Remove embedded cartridges)

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on JBIDE-13729:
-------------------------------------------------

Andre Dietisheim <adietish at redhat.com> made a comment on [bug 918501|https://bugzilla.redhat.com/show_bug.cgi?id=918501]

What matters to JBDS is not the ability to get removed or not, it's the type: embedded/standalone. What breaks JBDS is when standalone cartridges get reported. If HAProxy (which is afaik an embedded cartridge) cannot be removed, then this doesn't hurt JBDS as long as the REST service errors on removal. What breaks JBDS is if standalone cartridges get reported where it only expects embeddded cartridges.
                
> Error trying to embed HAProxy into scaled application: HAProxy not listed in embedded cartridges (OpenShift Explorer, Add/Remove embedded cartridges)
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13729
>                 URL: https://issues.jboss.org/browse/JBIDE-13729
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Stefan Bunciak
>            Assignee: Andre Dietisheim
>            Priority: Minor
>             Fix For: 4.1.x
>
>         Attachments: scaledeap.png
>
>
> This is a watcher issue that keeps track of the progress in the OpenShift bugzilla:
> HAProxy cartridge not displayed in OpenShift Explorer even it is already embedded during the process of creating scaled application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira