[
https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi...
]
Dmitrii Bocharov commented on JBIDE-23490:
------------------------------------------
[~jeffmaury] have some problems with your PR [^ScaledUpPodProblems.webm].
1) ASSERT Scale up Pods, say, to 5
2) ASSERT Create Server Adapter for service
3) ASSERT if you try to create Server Adapter for service once again, it will just change
focus to the already created server adapter
4) Try to create server adapter for pod - it will create one more Server Adapter.
For some reason it doesn't happen all the time, just for some pods. If it happens,
you'll have problems with dealing with these server adapters - see the attached
video.
Server adapter: provide ability to link pods/'deployment
config'/'replication controller'(?) when no service is available
-------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-23490
URL:
https://issues.jboss.org/browse/JBIDE-23490
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.4.2.AM3
Reporter: Aurélien Pupier
Assignee: Jeff MAURY
Labels: new_and_noteworthy, openshift_v3, server_adapter,
server_adapter_wizard
Fix For: 4.4.3.Final
Attachments: ScaledUpPodProblems.webm
When some OpenShift applications are not providing any services. the Eclipse OpenShift
Tooling is not able to create an OpenShift server adapters to deploy new version of the
application.
The only that we are sure that will be always available are pods so it would be nice to
provide some fallback logic that asks you to choose a pod or uses the only one it finds​
when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)