[jbosstools-issues] [JBoss JIRA] (JBIDE-24241) Server adapter not working when created from replication controller fallback

[Andre Dietisheim (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-24241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-24241:
-------------------------------------
    Steps to Reproduce: 
ASSERT: Have an OpenShift 3 connection and a project
EXEC: Create a new application (I used nodejs:latest image)
EXEC: Wait for a pod to start
EXEC: Remove the created service and deployment config
EXEC: Create a new server adapter -> Openshift 3 server adapter
EXEC: Choose the deployment of the newly created application
ASSERT: In Resource Details, the Kind property says 'ReplicationController'
EXEC: Finish the wizard
RESULT: The server adapter is created
RESULT: An error occurs when starting the server adapter
!replication-controller-not-found.png!

  was:
ASSERT: Have an OpenShift 3 connection and a project
EXEC: Create a new application (I used nodejs:latest image)
EXEC: Wait for a pod to start
EXEC: Remove the created service and deployment config
EXEC: Create a new server adapter -> Openshift 3 server adapter
EXEC: Choose the deployment of the newly created application
ASSERT: In Resource Details, the Kind property says 'ReplicationController'
EXEC: Finish the wizard
RESULT: The server adapter is created
RESULT: An error occurs when starting the server adapter



> Server adapter not working when created from replication controller fallback
> ----------------------------------------------------------------------------
>
>                 Key: JBIDE-24241
>                 URL: https://issues.jboss.org/browse/JBIDE-24241
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.4.AM3
>            Reporter: Jan Richter
>            Assignee: Jeff MAURY
>              Labels: openshift_v3, server_adapter
>             Fix For: 4.4.4.Final, 4.5.0.AM1
>
>         Attachments: replication-controller-not-found.png
>
>
> When no service nor deployment config is available, it is possible to create a server adapter using replication controllers. A server adapter created this way errors on start with the following message:
> {noformat}
> An internal error occurred during: "Starting nodejs-1 (ReplicationController) at OpenShift 3 (192.168.42.24)".
> deploymentconfigs "nodejs" not found deploymentconfigs "nodejs" not found
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)