March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21824) Content assist for image names in "Deploy Docker Image" wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21824?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21824: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Content assist for image names in "Deploy Docker Image" wizard > --------------------------------------------------------------- > > Key: JBIDE-21824 > URL: https://issues.jboss.org/browse/JBIDE-21824 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection. > If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21824) Content assist for image names in "Deploy Docker Image" wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21824?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21824: ------------------------------------------ cherry-picked into master > Content assist for image names in "Deploy Docker Image" wizard > --------------------------------------------------------------- > > Key: JBIDE-21824 > URL: https://issues.jboss.org/browse/JBIDE-21824 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection. > If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3671) sshd needs to be installed and started

by Hardy Ferentschik (JIRA)

Hardy Ferentschik created JBDS-3671: --------------------------------------- Summary: 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 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21802) Content assist for image names in "Deploy Docker Image" wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21802?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21802: ------------------------------------------ great, thanks! merged into jbosstools-4.3.x > Content assist for image names in "Deploy Docker Image" wizard > --------------------------------------------------------------- > > Key: JBIDE-21802 > URL: https://issues.jboss.org/browse/JBIDE-21802 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection. > If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21824) Content assist for image names in "Deploy Docker Image" wizard

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21824: ---------------------------------------- Summary: Content assist for image names in "Deploy Docker Image" wizard Key: JBIDE-21824 URL: https://issues.jboss.org/browse/JBIDE-21824 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Xavier Coulon Assignee: Andre Dietisheim Fix For: 4.3.1.CR1 The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection. If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[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 commented on JBDS-3660: ----------------------------------- So it only works when logged on a google account, awesome. > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21821) JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21821: ------------------------------------ The 4.0.2 version of jgit is only in the 4.51.x TP, which was used for JBT 4.3.0.Final / JBDS 9.0.0.Final (Mars.1). Can you test if this happens with JBT 4.3.1.CR1 / JBDS 9.1.0.CR1? Install from here: http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/ https://devstudio.jboss.com/9.0/snapshots/updates/core/4.3.mars/ If the problem exists in CR1, we may need to update the CR1 TPs to BOTH include jgit 4.1.1 instead of 4.1.1 in the 4.52.x TP and 4.0.0 in the 4.50.x TP. > JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2 > ---------------------------------------------------------------- > > Key: JBIDE-21821 > URL: https://issues.jboss.org/browse/JBIDE-21821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, marketplace > Reporter: Thomas Mäder > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: FrameworkEvent ERROR.txt > > > Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break. > # Install Eclipse 4.5.2 > # In the Marketplace, search for "jboss developer studio" > # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA > # Install it > # Restart > # Observe: the EGit views and preferences are missing > # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[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: ------------------------------------------ [~jcantrill] do you have the jira ready to link here please? > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20568) Duplicate templates in different OpenShift projects are not distinguishable from each other

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20568?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-20568: ------------------------------------- Assignee: Viacheslav Kabanovich > Duplicate templates in different OpenShift projects are not distinguishable from each other > ------------------------------------------------------------------------------------------- > > Key: JBIDE-20568 > URL: https://issues.jboss.org/browse/JBIDE-20568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: screenshot-1.png, TemplateLableWithNamespace.png > > > New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21823: --------------------------------------- [~adietish] we had a similiar issue with buildconfigs but it was proably editing of any non-service resource. Solution might be that we need to fetch before we edit to ensure we have the latest. We are supposed to be getting updates as changes come in so maybe we are not listening to them properly. > 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, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2016