8:14 a.m.
[
https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-21823 at 3/15/16 9:13 AM:
-------------------------------------------------------------------
I just experienced this whith [~tmader] when editing a DeploymentConfig (to enable
Debugging):
# EXEC: create a new application via template (eap-basic-s2i)
# EXEC: once the resources are created confirm the import (and let the cloning etc.
happen)
# ASSERT: have Properties view opened
# EXEC: in Explorer: select the new service
# EXEC: in Properties view: select "Deployment" tab, select your deployment
config and hit "Edit" in the context menu.
# ASSERT: Editor for the deployment config pops up
# EXEC: do some changes and save the editor
Result:
Error pops up telling you that the resources is outdated.
Refreshing didnt help, we finally restarted Eclipse and once up again the timestamp (and
version) of the resource were updated and editing worked.
This might make it to its own jira but it looks like it's caused by the same issues in
the watch/refresh
was (Author: adietish):
I just experienced this whith [~tmader] when editing a DeploymentConfig (to enable
Debugging):
# EXEC: create a new application via template (eap-basic-s2i)
# EXEC: once the resources are created confirm the import (and let the cloning etc.
happen)
# ASSERT: have Properties view opened
# EXEC: in Explorer: select the new service
# EXEC: in Properties view: select "Deployment" tab, select your deployment
config and hit "Edit" in the context menu.
# ASSERT: Editor for the deployment config pops up
# EXEC: do some changes and save the editor
Result:
Error pops up telling you that the resources is outdated.
Refreshing didnt help, we finally restarted Eclipse and once up again the timestamp (and
version) of the resource were updated and editing worked.
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)
3679
days inactive
3679
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Andre Dietisheim (JIRA)