[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23039:
---------------------------------------
Roland is correct.
I just tried this on Windows and the output of vagrant up is now printed in the Terminal view. But I have one question: Why is the terminal instance called Test? That's a bit confusing. Another slightly confusing thing: vagrant up output is in Terminal view, but when you stop your cdk, the output from "vagrant halt" is shown in the Console view.
But then I tried unchecking "pass credentials to environment" to see if it actually works. And *it does not really work*. When I reach the point in vagrant up when it asks whether I want to registrer, there is a cursor blinking. But when I press "y", nothing is shown. If I press Enter, in a few seconds it proceeds and asks for my username, but again, nothing is printed and I was not able to properly enter my credentials at all.
> 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
> Priority: Blocker
> Fix For: 4.4.1.Final
>
> 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-23035) Support WildFly 10.1 - change server adapter name
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23035?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-23035.
---------------------------------
Resolution: Done
this was pushed
> Support WildFly 10.1 - change server adapter name
> -------------------------------------------------
>
> Key: JBIDE-23035
> URL: https://issues.jboss.org/browse/JBIDE-23035
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.1.Final
>
>
> WildFly 10.1 has been released.
> We need to make sure it works properly.
> My initial test doesn't show any problems. The server can be added both manually and using runtime detection which properly recognizes the version as 10.1.
> AFAICS, the only cosmetic change we'll need is to change the adapter name from 10.0 to 10.x. But please take a look and maybe you'll see there's more.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22686) Can't push image to docker registry
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22686?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-22686:
------------------------------------------
[~hardy.ferentschik] can you help me again, please?
I can do `vagrant ssh` without any problems
I can login:
{code:bash}
[dbocharo@dbocharo rhel-ose]$ oc login 10.1.2.2:8443 -u openshift-dev -p devel
Login successful.
Using project "sample-project".
[dbocharo@dbocharo rhel-ose]$ docker login -u openshift-dev -p `oc whoami -t` -e foo(a)bar.com hub.openshift.rhel-cdk.10.1.2.2.xip.io
Flag --email has been deprecated, will be removed in 1.13.
Error response from daemon: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/users/: x509: certificate signed by unknown authority
{code}
successfully.
{code:bash}
[dbocharo@dbocharo rhel-ose]$ ping 10.1.2.2
PING 10.1.2.2 (10.1.2.2) 56(84) bytes of data.
64 bytes from 10.1.2.2: icmp_seq=1 ttl=64 time=0.427 ms
64 bytes from 10.1.2.2: icmp_seq=2 ttl=64 time=0.612 ms
64 bytes from 10.1.2.2: icmp_seq=3 ttl=64 time=0.381 ms
{code}
> Can't push image to docker registry
> -----------------------------------
>
> Key: JBIDE-22686
> URL: https://issues.jboss.org/browse/JBIDE-22686
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Affects Versions: 4.4.0.Final
> Environment: Fedora 23
> Reporter: Dmitrii Bocharov
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.1.AM2
>
> Attachments: DeployDockerImageToOS.webm, DeployedSuccessfully.webm
>
>
> The screencast of the last steps is attached.
> Properties and settings of the cdk haven't been changed. Everything is dowloaded and installed in a usual way.
> Possibly something is with the dns - maybe it wasn't configured correctly while cdk installation. Because we to push to the valid url, while OS connection only an IP in its settings.
> _exception:_
> org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1047)
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:67)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:42)
> at com.spotify.docker.client.ProgressStream.tail(ProgressStream.java:74)
> at com.spotify.docker.client.DefaultDockerClient.push(DefaultDockerClient.java:821)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1043)
> ... 3 more
> Caused by: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
> v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> at org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler.processMessage(ImagePushProgressHandler.java:49)
> at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40)
> ... 6 more
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23097) jbosstools-cleanup not working on www.qa
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-23097:
----------------------------------
Summary: jbosstools-cleanup not working on www.qa
Key: JBIDE-23097
URL: https://issues.jboss.org/browse/JBIDE-23097
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.4.1.Final
Reporter: Nick Boldt
Priority: Minor
{code}
Check for 10.0/snapshots/builds builds more than 2 days old; keep minimum 2 builds per branch (linked in composite: 2)
Check /qa/services/http/binaries/RHDS/10.0/snapshots/builds/ for dirs matching /devstudio.product_10.0.neon/ ...
> Check /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_10.0.neon...
date: 2016-09-02_13-58-37-B41: No such file or directory
+ /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_10.0.neon/2016-09-02_13-58-37-B41 (17046d)
date: 2016-06-15_14-51-47-B33: No such file or directory
+ /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_10.0.neon/2016-06-15_14-51-47-B33 (17046d){code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23097) jbosstools-cleanup not working on www.qa
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23097?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23097:
-------------------------------
Fix Version/s: 4.4.2.AM1
> jbosstools-cleanup not working on www.qa
> ----------------------------------------
>
> Key: JBIDE-23097
> URL: https://issues.jboss.org/browse/JBIDE-23097
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.4.2.AM1
>
>
> {code}
> Check for 10.0/snapshots/builds builds more than 2 days old; keep minimum 2 builds per branch (linked in composite: 2)
> Check /qa/services/http/binaries/RHDS/10.0/snapshots/builds/ for dirs matching /devstudio.product_10.0.neon/ ...
> > Check /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_10.0.neon...
> date: 2016-09-02_13-58-37-B41: No such file or directory
> + /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_10.0.neon/2016-09-02_13-58-37-B41 (17046d)
> date: 2016-06-15_14-51-47-B33: No such file or directory
> + /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_10.0.neon/2016-06-15_14-51-47-B33 (17046d){code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23097) jbosstools-cleanup not working on www.qa
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23097?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23097:
----------------------------------
Assignee: Nick Boldt
> jbosstools-cleanup not working on www.qa
> ----------------------------------------
>
> Key: JBIDE-23097
> URL: https://issues.jboss.org/browse/JBIDE-23097
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.4.2.AM1
>
>
> {code}
> Check for 10.0/snapshots/builds builds more than 2 days old; keep minimum 2 builds per branch (linked in composite: 2)
> Check /qa/services/http/binaries/RHDS/10.0/snapshots/builds/ for dirs matching /devstudio.product_10.0.neon/ ...
> > Check /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_10.0.neon...
> date: 2016-09-02_13-58-37-B41: No such file or directory
> + /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_10.0.neon/2016-09-02_13-58-37-B41 (17046d)
> date: 2016-06-15_14-51-47-B33: No such file or directory
> + /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_10.0.neon/2016-06-15_14-51-47-B33 (17046d){code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs...
--
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 MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23015:
------------------------------------
We could use the port name instead of numeric value to provide the flexibily
> 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.2.AM1
>
>
> 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-23042) CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Martin Malina resolved JBIDE-23042.
-----------------------------------
Resolution: Done
I am able to start cdk 2.2 rc3 on Windows 10 using vagrant up just fine. Please let us know if you're still seeing issues with this latest cdk build.
> 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