[JBoss JIRA] (JBIDE-21755) "Eager-er" loading of the project properties
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21755:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> "Eager-er" loading of the project properties
> --------------------------------------------
>
> Key: JBIDE-21755
> URL: https://issues.jboss.org/browse/JBIDE-21755
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21755) "Eager-er" loading of the project properties
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21755:
--------------------------------
Priority: Minor (was: Major)
> "Eager-er" loading of the project properties
> --------------------------------------------
>
> Key: JBIDE-21755
> URL: https://issues.jboss.org/browse/JBIDE-21755
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21425) Server adapter wizard: Finish button should be disabled in page which contains connection selection
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21425?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21425:
-----------------------------------------------
[~mlabuda], can it be successfully finished? It seems it remembers the last selection and so is initialized. If finish does work, it is kind of a feature, though maybe unexpected. If it does not work, then wizard is not properly cleaned at closing, and remains in a wrong state, which is a bug.
> Server adapter wizard: Finish button should be disabled in page which contains connection selection
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21425
> URL: https://issues.jboss.org/browse/JBIDE-21425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2, 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> In server adapter wizard on wizard page where selection of a connection is performed, the Finish button is enabled. This should not be possible, because although connection is selected but service, eclipse project and paths are not filled in. Hitting finish button in this stage leads to a new server adapter, which does not do anything and its linked to nothing, because details are empty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21831) Change host to localhost when cdk is selected in new server dialog
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21831?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21831:
--------------------------------
Fix Version/s: 4.3.1.CR1
> Change host to localhost when cdk is selected in new server dialog
> ------------------------------------------------------------------
>
> Key: JBIDE-21831
> URL: https://issues.jboss.org/browse/JBIDE-21831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.CR1
>
>
> When you open the new server dialog, select OpenShift 2, it will set host to openshift.redhat.com. When you then select cdk, it will complain that it only works on localhost. So the suggestion is to make it work the same way OpenShift adapters work and ensure that host is always changed to localhost when you select the cdk adapter.
> This was spotted and brought up by [~mlabuda].
> For reference, this is the JIRA where similar thing was discussed for OpenShift: JBIDE-20114
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21849?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21849:
---------------------------------------
What is AP? Atomic platform?
> [AP] Not able to list services under a project after login to AP
> ----------------------------------------------------------------
>
> Key: JBIDE-21849
> URL: https://issues.jboss.org/browse/JBIDE-21849
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: -JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191
> -AP puddle: 2016-03-09.2
> -oc version:
> oc v3.2.0.1
> kubernetes v1.2.0-alpha.7-703-gbc4550d
> Reporter: Xia Zhao
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3
>
> -Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}"
> -Issue did not repro if switch to OSE
> -Repro on Linux/Windows/Mac OS
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21831) Change host to localhost when cdk is selected in new server dialog
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21831?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21831:
--------------------------------
Issue Type: Bug (was: Feature Request)
> Change host to localhost when cdk is selected in new server dialog
> ------------------------------------------------------------------
>
> Key: JBIDE-21831
> URL: https://issues.jboss.org/browse/JBIDE-21831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> When you open the new server dialog, select OpenShift 2, it will set host to openshift.redhat.com. When you then select cdk, it will complain that it only works on localhost. So the suggestion is to make it work the same way OpenShift adapters work and ensure that host is always changed to localhost when you select the cdk adapter.
> This was spotted and brought up by [~mlabuda].
> For reference, this is the JIRA where similar thing was discussed for OpenShift: JBIDE-20114
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21831) Change host to localhost when cdk is selected in new server dialog
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21831?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21831:
--------------------------------
Priority: Minor (was: Major)
> Change host to localhost when cdk is selected in new server dialog
> ------------------------------------------------------------------
>
> Key: JBIDE-21831
> URL: https://issues.jboss.org/browse/JBIDE-21831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
>
> When you open the new server dialog, select OpenShift 2, it will set host to openshift.redhat.com. When you then select cdk, it will complain that it only works on localhost. So the suggestion is to make it work the same way OpenShift adapters work and ensure that host is always changed to localhost when you select the cdk adapter.
> This was spotted and brought up by [~mlabuda].
> For reference, this is the JIRA where similar thing was discussed for OpenShift: JBIDE-20114
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21823:
-------------------------------------
[~xcoulon] do you still experience the problem?
> Unable to re-edit Service config
> --------------------------------
>
> Key: JBIDE-21823
> URL: https://issues.jboss.org/browse/JBIDE-21823
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes.
> Steps to reproduce:
> - select a service in the OpenShift Explorer
> - click on the {{Edit...}} command.
> - in the JSON editor for the service config, note the resource version. Eg:
> {code}
> {
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38301",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> },
> ...
> {code}
> - make some changes and save
> - the service config version should have incremented:
> {code}
> {
> "kind" : "Service",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38390",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> }
> ....
> {code}
> - close the config editor
> - re-open the config editor
> *ASSERT: the editor displays the latest config*
> *FAIL the editor displays the initial config*
> *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version*
> {code}
> Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again
> Could not update resource jee-sample: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again",
> "reason": "Conflict",
> "details": {
> "name": "jee-sample",
> "kind": "services"
> },
> "code": 409
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-21823:
----------------------------------------
Priority: Major (was: Critical)
> Unable to re-edit Service config
> --------------------------------
>
> Key: JBIDE-21823
> URL: https://issues.jboss.org/browse/JBIDE-21823
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes.
> Steps to reproduce:
> - select a service in the OpenShift Explorer
> - click on the {{Edit...}} command.
> - in the JSON editor for the service config, note the resource version. Eg:
> {code}
> {
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38301",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> },
> ...
> {code}
> - make some changes and save
> - the service config version should have incremented:
> {code}
> {
> "kind" : "Service",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38390",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> }
> ....
> {code}
> - close the config editor
> - re-open the config editor
> *ASSERT: the editor displays the latest config*
> *FAIL the editor displays the initial config*
> *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version*
> {code}
> Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again
> Could not update resource jee-sample: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again",
> "reason": "Conflict",
> "details": {
> "name": "jee-sample",
> "kind": "services"
> },
> "code": 409
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21823:
---------------------------------------------
It seems to work just for me.
Also you should be able to click refresh and open editor again (so there is a workaround)
> Unable to re-edit Service config
> --------------------------------
>
> Key: JBIDE-21823
> URL: https://issues.jboss.org/browse/JBIDE-21823
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes.
> Steps to reproduce:
> - select a service in the OpenShift Explorer
> - click on the {{Edit...}} command.
> - in the JSON editor for the service config, note the resource version. Eg:
> {code}
> {
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38301",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> },
> ...
> {code}
> - make some changes and save
> - the service config version should have incremented:
> {code}
> {
> "kind" : "Service",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "jee-sample",
> "namespace" : "sample",
> "selfLink" : "/api/v1/namespaces/sample/services/jee-sample",
> "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e",
> "resourceVersion" : "38390",
> "creationTimestamp" : "2016-02-23T16:06:03Z",
> "labels" : {"app" : "jee-sample"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"}
> }
> ....
> {code}
> - close the config editor
> - re-open the config editor
> *ASSERT: the editor displays the latest config*
> *FAIL the editor displays the initial config*
> *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version*
> {code}
> Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again
> Could not update resource jee-sample: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again",
> "reason": "Conflict",
> "details": {
> "name": "jee-sample",
> "kind": "services"
> },
> "code": 409
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years