[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config
by Andre Dietisheim (JIRA)
[ 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)
10 years
[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21823:
------------------------------------------
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)
10 years
[JBoss JIRA] (JBDS-3671) sshd needs to be installed and started
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBDS-3671?page=com.atlassian.jira.plugin.... ]
Hardy Ferentschik commented on JBDS-3671:
-----------------------------------------
Ok, here is an update. I started over and removed traces of the PowerShell and MSYS2 sshd installs. Instead I went for the Cygwin sshd approach as described here - http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_cyg....
Using this approach, I was able to configure a sshd Windows service and then use version 1.0.0 of vagrant-sshfs to mount the users home directory into the VM. I am not sure whether the PowerShell and MSYS2 really don't work or whether they did not work, due some conflicts. This would need more investigation in case we wanted to give it another try. Bottom line cygwin sshd works.
So far, I only tried the password mode. For a non-interactive approach one would need to setup key based configuration.
[~dgolovin], what's the state of the Cygwin usage in our installer? Is it currently used? If not, would it be hard to bring back? Also, what do you think about the steps described in the document above? The key is {{ssh-host-config}} which is per default interactive, but looking at the help output it seems to be able to run in an non interactive mode as well. WDYT?
> sshd needs to be installed and started
> --------------------------------------
>
> Key: JBDS-3671
> URL: https://issues.jboss.org/browse/JBDS-3671
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Hardy Ferentschik
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> As parts of the Docker story we need to be able to mount the users home directory into the VM (as docker-machine does as well). Only this way the user can then use Docker mounts to mount for example project directories into a Docker container.
> docker-machine uses the vbguest additions for that, but we still need to determine whether this is possible for us due to potential licensing issues.
> An alternative approach is to use [sshfs|https://github.com/dustymabe/vagrant-sshfs/] and use ssh to mount the user's home directory into the VM. sshfs, however, requires a running sshd on the host. On Windows I am aware of two ways of doing that
> * Cygwin - http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_cyg...
> * Win32-OpenSSH - https://github.com/PowerShell/Win32-OpenSSH
> I think the Windows ssh port would be the preferred solution, however, when testing it, the connection failed when using sshfs. I was able to simple ssh from the guest (CDK) to the host (Windows), but when using sshfs the connection would just abort. More investigation is required for using vagrant-sshfs with Win32-OpenSSH. It might just be that the Windows port is not fully functional which would leave use with the cygwin approach.
> Bottom line, if we want to use the sshfs approach as an alternative for vbguest additions, we need to get sshd installed one way or the other.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3617) Cannot run vagrant after running installer
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3617?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3617.
-----------------------------
Verified with installer build from 2016-03-15 source.
> Cannot run vagrant after running installer
> ------------------------------------------
>
> Key: JBDS-3617
> URL: https://issues.jboss.org/browse/JBDS-3617
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Environment: Windows 10
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.CR1
>
> Attachments: Vagrant.png
>
>
> See attached screenshot - the same error is seen when running with the CDK configured as a runtime - or by running vagrant/vagrant.bat form the CLI after running the installer.
> Exception occurred executing command line.
> {{Cannot run program c:\DeveloperPlatform\vagrant\bin\vagrant) (in directory {{C:\DeveloperPlatform\cdk\plugins): CreateProcess error=193, %1 is not a valid Win32 application}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3660) Unable to download ssh-rsync from the provided URL
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3660?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3660.
-----------------------------
Verified with installer build from 2016-03-15 source.
> Unable to download ssh-rsync from the provided URL
> --------------------------------------------------
>
> Key: JBDS-3660
> URL: https://issues.jboss.org/browse/JBDS-3660
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> The URL ssh-rsync should be downloaded from points to google drive, which won't let anyone download it without about two more confirmations. The installer just cant cope with this.
> As a result of the installs now being chained, it now blocks vagrant and cdk installs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-574) Adapt UI tests to 8.0.0
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-574?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík updated JBTIS-574:
-------------------------------
Labels: fus (was: )
> Adapt UI tests to 8.0.0
> -----------------------
>
> Key: JBTIS-574
> URL: https://issues.jboss.org/browse/JBTIS-574
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 4.3.0.Alpha2
> Reporter: Tomáš Sedmík
> Assignee: Tomáš Sedmík
> Priority: Critical
> Fix For: 4.3.0.Final
>
> Original Estimate: 2 weeks
> Remaining Estimate: 2 weeks
>
> There are some changes in Fuse Tooling (new Camel Editor, ...), so our automated tests have to be adapted to reflect these changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3630) Non-consistent labels while downloading files
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3630?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3630.
-----------------------------
Closing as rejected.
> Non-consistent labels while downloading files
> ---------------------------------------------
>
> Key: JBDS-3630
> URL: https://issues.jboss.org/browse/JBDS-3630
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Pavol Pitonak
> Assignee: Joshua Wilson
> Priority: Minor
> Labels: havoc
> Fix For: 9.1.0.CR1
>
> Attachments: installer.png
>
>
> When running the installer, you can see on third screen (Download & Install) 6 progress bars. When the installer is downloading the files, it shows either *Downloading* or *Waiting for all downloads to finish* (see attached screenshot). This should be unified.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years