[JBoss JIRA] (JBIDE-21458) Explorer: New deployments and pods dont refresh properly in explorer tree
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21458?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21458:
---------------------------------------
Merged into feature branch
> Explorer: New deployments and pods dont refresh properly in explorer tree
> -------------------------------------------------------------------------
>
> Key: JBIDE-21458
> URL: https://issues.jboss.org/browse/JBIDE-21458
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: openshift_deployment_view
> Fix For: 4.3.1.Beta2
>
> Attachments: Service_added_but_shows_empty_space.png
>
>
> Expanding the explorer tree of a project to see the deployments and pods and then adding a new deployment from the server causes the display to show the wrong nodes and not receive any updates. See screen shot attached:
> Demonstrated by:
> # From eclipse, add a new project
> # Expand project . note: no deployments
> # From cli, add a service
> # Note screen 'updates' but there is no deployment, just an empty node.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21478) New Server adapter using same build config and server is ignored
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21478?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21478:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.Beta2)
> New Server adapter using same build config and server is ignored
> ----------------------------------------------------------------
>
> Key: JBIDE-21478
> URL: https://issues.jboss.org/browse/JBIDE-21478
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha1
>
>
> When I have a OS3 server adapter in Server view and I open wizard to create a new server adapter from context menu of a servers view, the newly created server adapter is ignored if same build config name and server is used. E.g. I have a server api.engint.openshift.com and eap-app build config (related to the service that server adapter is supposed to be bind to). First time I create a new server adapter for this application, it is shown in servers view, but if I choose to create another server adapter for same build config and server, details filled in this newly opened server adapter wizard are ignored and new adapter is not created.
> I would expect one of following:
> a) An existing server adapter will be updated according to the latest details filled in server adapter wizard
> b) There would be created another server adapter for the same service (and build config) and server but with altered name. This is possible solution because a server adapter name in wizard is already altered but it is never used anywhere.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21478) New Server adapter using same build config and server is ignored
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21478?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-21478.
-----------------------------------
Resolution: Done
> New Server adapter using same build config and server is ignored
> ----------------------------------------------------------------
>
> Key: JBIDE-21478
> URL: https://issues.jboss.org/browse/JBIDE-21478
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha1
>
>
> When I have a OS3 server adapter in Server view and I open wizard to create a new server adapter from context menu of a servers view, the newly created server adapter is ignored if same build config name and server is used. E.g. I have a server api.engint.openshift.com and eap-app build config (related to the service that server adapter is supposed to be bind to). First time I create a new server adapter for this application, it is shown in servers view, but if I choose to create another server adapter for same build config and server, details filled in this newly opened server adapter wizard are ignored and new adapter is not created.
> I would expect one of following:
> a) An existing server adapter will be updated according to the latest details filled in server adapter wizard
> b) There would be created another server adapter for the same service (and build config) and server but with altered name. This is possible solution because a server adapter name in wizard is already altered but it is never used anywhere.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21478) New Server adapter using same build config and server is ignored
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21478:
-------------------------------------
Summary: New Server adapter using same build config and server is ignored
Key: JBIDE-21478
URL: https://issues.jboss.org/browse/JBIDE-21478
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Marián Labuda
Assignee: Viacheslav Kabanovich
Priority: Critical
Fix For: 4.3.1.Beta2
When I have a OS3 server adapter in Server view and I open wizard to create a new server adapter from context menu of a servers view, the newly created server adapter is ignored if same build config name and server is used. E.g. I have a server api.engint.openshift.com and eap-app build config (related to the service that server adapter is supposed to be bind to). First time I create a new server adapter for this application, it is shown in servers view, but if I choose to create another server adapter for same build config and server, details filled in this newly opened server adapter wizard are ignored and new adapter is not created.
I would expect one of following:
a) An existing server adapter will be updated according to the latest details filled in server adapter wizard
b) There would be created another server adapter for the same service (and build config) and server but with altered name. This is possible solution because a server adapter name in wizard is already altered but it is never used anywhere.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21421) New Server adapter using same build config and server is ignored
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21421?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21421.
---------------------------------
Verified in nigthly build of JBDS 9.1.0.Beta2 with OpenShift tools plugin of version 3.1.0.Beta2-v20160119-1135-B153.
> New Server adapter using same build config and server is ignored
> ----------------------------------------------------------------
>
> Key: JBIDE-21421
> URL: https://issues.jboss.org/browse/JBIDE-21421
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> When I have a OS3 server adapter in Server view and I open wizard to create a new server adapter from context menu of a servers view, the newly created server adapter is ignored if same build config name and server is used. E.g. I have a server api.engint.openshift.com and eap-app build config (related to the service that server adapter is supposed to be bind to). First time I create a new server adapter for this application, it is shown in servers view, but if I choose to create another server adapter for same build config and server, details filled in this newly opened server adapter wizard are ignored and new adapter is not created.
> I would expect one of following:
> a) An existing server adapter will be updated according to the latest details filled in server adapter wizard
> b) There would be created another server adapter for the same service (and build config) and server but with altered name. This is possible solution because a server adapter name in wizard is already altered but it is never used anywhere.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21424) Server adapter editor: IP in host name of a server adapter overview has cut off digit
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21424?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21424.
---------------------------------
Currently locally running OpenShift instance and also internal OSE 3 instance display host names as DNS names, but those names are correct, no missing last char, I consider it done. Verified in nigthly build of JBDS 9.1.0.Beta2 with OpenShift tools plugin of version 3.1.0.Beta2-v20160119-1135-B153.
> Server adapter editor: IP in host name of a server adapter overview has cut off digit
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-21424
> URL: https://issues.jboss.org/browse/JBIDE-21424
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.3.1.Beta2
>
>
> In a server adapter overview there is a text widget for a host name, where IP address of a service is filled in. Problem is that the IP address is missing last digit.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months