[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Lalatendu Mohanty (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Lalatendu Mohanty commented on JBIDE-23016:
-------------------------------------------
I think the last resort would be to ask user to do "vagrant up" manually for first time in a terminal.
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.1.Final
>
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Lalatendu Mohanty (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Lalatendu Mohanty commented on JBIDE-23016:
-------------------------------------------
We can also try to do the steps which Landrush does as part of Vagrant up as part of DevStudio. So when "vagrant up" is done we will not ask for sudoers username/password.
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.1.Final
>
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ]
Jeff Cantrill edited comment on JBIDE-23015 at 8/31/16 8:28 AM:
----------------------------------------------------------------
Routes will by default use the port(s) specified by the service. You can explicitly define one https://github.com/openshift/origin/blob/master/pkg/route/api/types.go#L38 which can be an integer or named port on the services. If a port is not specified, I believe it will round robin them. I believe there is still a limitation for services which ties into this where you can specify a single port for a service to target or all of them; you can not specify a subset. I mentioned that in another issue dealing with the deploy image workflow.
Editing...the hitch to explicitly defining a port in the route is that it removes the flexibility for someone to update the service port it exposes without changes to the route. I'm not saying we shouldn't do it but its one drawback
was (Author: jcantrill):
Routes will by default use the port(s) specified by the service. You can explicitly define one https://github.com/openshift/origin/blob/master/pkg/route/api/types.go#L38 which can be an integer or named port on the services. If a port is not specified, I believe it will round robin them. I believe there is still a limitation for services which ties into this where you can specify a single port for a service to target or all of them; you can not specify a subset. I mentioned that in another issue dealing with the deploy image workflow.
> Creating a route should have a default port
> -------------------------------------------
>
> Key: JBIDE-23015
> URL: https://issues.jboss.org/browse/JBIDE-23015
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Fix For: 4.4.1.Final
>
>
> When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail.
> There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others.
> The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation)
> To reproduce:
> - git clone https://github.com/redhat-helloworld-msa/aloha
> - mvn package
> - build docker image from Dockerfile, to CDK docker connection
> - deploy docker image to openshift
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-23015:
---------------------------------------
Routes will by default use the port(s) specified by the service. You can explicitly define one https://github.com/openshift/origin/blob/master/pkg/route/api/types.go#L38 which can be an integer or named port on the services. If a port is not specified, I believe it will round robin them. I believe there is still a limitation for services which ties into this where you can specify a single port for a service to target or all of them; you can not specify a subset. I mentioned that in another issue dealing with the deploy image workflow.
> Creating a route should have a default port
> -------------------------------------------
>
> Key: JBIDE-23015
> URL: https://issues.jboss.org/browse/JBIDE-23015
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Fix For: 4.4.1.Final
>
>
> When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail.
> There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others.
> The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation)
> To reproduce:
> - git clone https://github.com/redhat-helloworld-msa/aloha
> - mvn package
> - build docker image from Dockerfile, to CDK docker connection
> - deploy docker image to openshift
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Praveen Kumar (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Praveen Kumar commented on JBIDE-23016:
---------------------------------------
I am not sure if that helps but I just used a python script which run vagrant[0] as spawn process and using it pexpect module we can pass whatever required. I am hoping java might have some module around expect.
[0] https://gist.github.com/praveenkumar/75279d589581c7327a866add68947f2c
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.1.Final
>
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements
by Praveen Kumar (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ]
Praveen Kumar commented on JBIDE-23039:
---------------------------------------
I am not sure if that helps but I just used a python script which run vagrant[0] as spawn process and using it pexpect module we can pass whatever required. I am hoping java might have some module around expect.
[0] https://gist.github.com/praveenkumar/75279d589581c7327a866add68947f2c
> Need an interactive terminal that fits specific requirements
> ------------------------------------------------------------
>
> Key: JBIDE-23039
> URL: https://issues.jboss.org/browse/JBIDE-23039
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.4.1.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Attachments: vagranttty.png
>
>
> CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for.
> 1) I must be able to get a Process or IProcess object when a command is run
> 2) I must be able to get an event or know when the process terminates
> 3) The terminal or console must be interactive and allow user input when prompted.
> 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins.
> These three requirements thus far seem impossible to solve. Solutions that have been attempted are:
> 1) Creating a java Process by myself via Runtime.exec. The interactive prompts never arrive and there is no API for Process to know when it is waiting for input.
> 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed:
> a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input
> b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen
> 3) Launching / Opening a tm.terminal view. This solution fails requirements 1 and 2. We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed.
> Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant.
> Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream?
> No other obvious solutions have presented themselves in the past year.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Lalatendu Mohanty (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Lalatendu Mohanty commented on JBIDE-23016:
-------------------------------------------
Landrush needs to do several things which needs Administrator/root/sudoers access. So from Landrush point of view it is not doing anything wrong. However from a devstudio user experience point of view this is an issue in Linux and OS X. For Windows it should not be an issue as we expect the Windows user to be Administrator otherwise he can not run Devsuite installer.
So we are looking at work arounds for GNU/Linux and OS X.
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.1.Final
>
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23043) Not working connection to CDK Docker deamon
by Lalatendu Mohanty (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Lalatendu Mohanty commented on JBIDE-23043:
-------------------------------------------
This is fixed as part of CDK2.2 RC2 builds. Kindly verify.
> Not working connection to CDK Docker deamon
> -------------------------------------------
>
> Key: JBIDE-23043
> URL: https://issues.jboss.org/browse/JBIDE-23043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker, target-platform
> Affects Versions: 4.4.1.Final
> Environment: F24,
> Devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160825-0621-B5857
> Build date: 20160825-0621
> Docker Tooling:
> 2.1.0.20160825102
> Reporter: Josef Kopriva
> Assignee: Jeff Johnston
> Priority: Blocker
> Fix For: 4.4.1.Final
>
> Attachments: RC1vs0825N.txt, RC1vs0825N_sorted.txt
>
>
> After upgrading Docker Tooling to latest nightly, I cannot create connection to the Docker CDK deamon through TCP connection with certificates.
> Stacktrace:
> {code:java}
> An internal error occurred during: "Opening connection...".
> java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMParser
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:80)
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:64)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:83)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23042) CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
by Lalatendu Mohanty (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Lalatendu Mohanty commented on JBIDE-23042:
-------------------------------------------
The upstream issue has been closed as it was a configuration issue. I believe Rob also able to move ahead with his setup and not seeing this issue anymore. So this should be closed now.
> CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
> -------------------------------------------------------------
>
> Key: JBIDE-23042
> URL: https://issues.jboss.org/browse/JBIDE-23042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: cdk
> Fix For: 4.4.1.Final
>
> Attachments: vagrant-output.txt
>
>
> When launching the latest CDK 2.2 candidate the following error occurrs:
> {code}
> [landrush] Using eth1 (172.28.128.3)
> [landrush] adding Landrush'es DNS server to network 'VirtualBox Host-Only Network #3' using DNS IP '172.28.128.3'' and search domain 'cdk'
> ==> default: The folowing SH comand responded with a non-zero exit status.
> ==> default: Vagrant asumes that this means the comand failed!
> ==> default: sudo rm /etc/docker/ca.pem & sudo systemctl restart docker
> ==> default: Stdout from the comand:
> ==> default: Stder from the comand:
> ==> default: rm: canot remove '/etc/docker/ca.pem': No such file or directory
> ==> default: Forcing shutdown of VM...
> ==> default: Destroying VM and associated drives...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/services/docker.rb:20:in `execute': undefined method `zero?' for #<Thread:0x24a7250 dead> (NoMethodError)
> from C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/service.rb:20:in `each'
> {code}
> The complete vagrant output is here: [^vagrant-output.txt]
> See the following mail that Rob sent to the mailing list: http://post-office.corp.redhat.com/archives/devtools-program/2016-August/...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months