[JBoss JIRA] (JBIDE-23010) landrush plugin prevents CDK server adapter from starting
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23010?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23010:
---------------------------------------
Note: The workaround from the previous JIRA still works - if I start cdk from CLI and then start in devstudio, it will then work correctly.
Note2: CDK 2.1 still works fine. So this should really block AM3 release. The issue is only reproducible with CDK 2.2 rc1 atm.
> landrush plugin prevents CDK server adapter from starting
> ---------------------------------------------------------
>
> Key: JBIDE-23010
> URL: https://issues.jboss.org/browse/JBIDE-23010
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
>
> Today I downloaded cdk 2.2.rc1 [1], installed all the vagrant plugins from scratch. And then I first started this from CLI - it wanted password for sudo to set up landrush. (That's another concern I have: How will this work in devstudio? Probably it won't.)
> Then I stopped it, set up in devstudio and start there. Everything looks fine, but the server adapter is stuck at "Starting...".
> This is the console output:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Clearing any previously set forwarded ports...
> ==> default: Clearing any previously set network interfaces...
> ==> default: [landrush] virtualbox requires an additional private network; adding it
> ==> default: [landrush] starting dns server
> ==> default: Preparing network interfaces based on configuration...
> default: Adapter 1: nat
> default: Adapter 2: hostonly
> ==> default: Forwarding ports...
> default: 22 (guest) => 2222 (host) (adapter 1)
> ==> default: Running 'pre-boot' VM customizations...
> ==> default: Booting VM...
> ==> default: Waiting for machine to boot. This may take a few minutes...
> default: SSH address: 127.0.0.1:2222
> default: SSH username: vagrant
> default: SSH auth method: private key
> default: Warning: Remote connection disconnect. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> default: Warning: Remote connection disconnect. Retrying...
> ==> default: Machine booted and ready!
> ==> default: Registering box with vagrant-registration...
> ==> default: Checking for guest additions in VM...
> default: No guest additions were detected on the base box for this VM! Guest
> default: additions are required for forwarded ports, shared folders, host only
> default: networking, and more. If SSH fails on this machine, please install
> default: the guest additions and repackage the box to continue.
> default:
> default: This is not an error message; everything may continue to work properly,
> default: in which case you may ignore this message.
> ==> default: Setting hostname...
> ==> default: Configuring and enabling network interfaces...
> [landrush] Using eth1 (172.28.128.3)
> ==> default: [landrush] adding machine entry: cdk.vm => 172.28.128.3
> ==> default: [landrush] adding static DNS entry: cdk => cdk.vm
> [landrush] Using eth1 (172.28.128.3)
> [landrush] Host DNS resolver config looks good.
> ==> default: Copying TLS certificates to /Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Mounting SSHFS shared folder...
> ==> default: Mounting folder via SSHFS: /Users/rasp => /Users/rasp
> ==> default: Checking Mount..
> ==> default: Checking Mount..
> ==> default: Folder Successfully Mounted!
> ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
> ==> default: flag to force provisioning. Provisioners marked to run always will still run.
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default: Running provisioner: shell...
> default: Running: inline script
> ==> default:
> ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory.
> ==> default: To modify the number of cores and/or available memory set the environment variables
> ==> default: VM_CPU respectively VM_MEMORY.
> ==> default:
> ==> default: You can now access the OpenShift console on: https://openshift.cdk:8443/console
> ==> default:
> ==> default: To use OpenShift CLI, run:
> ==> default: $ vagrant ssh
> ==> default: $ oc login
> ==> default:
> ==> default: Configured users are (<username>/<password>):
> ==> default: openshift-dev/devel
> ==> default: admin/admin
> ==> default:
> ==> default: If you have the oc client library on your host, you can also login from your host.
> {code}
> These are my plugins:
> {code}
> $ vagrant plugin list
> landrush (1.1.1)
> - Version Constraint: 1.1.1
> vagrant-registration (1.2.3)
> - Version Constraint: 1.2.3
> vagrant-service-manager (1.3.0)
> - Version Constraint: 1.3.0
> vagrant-share (1.1.5, system)
> vagrant-sshfs (1.2.0)
> - Version Constraint: 1.2.0
> {code}
> [1] http://cdk-builds.usersys.redhat.com/builds/weekly/12-Aug-2016.rc1/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23012) move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23012?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23012:
-------------------------------
Description:
Since July 2014, the only file that's been changed in the jbosstools-documentation repo is ...
https://github.com/jbosstools/jbosstools-documentation/blob/master/whatsn...
In fact, the last time the repo was tagged was for JBoss Tools 4.1.0.Final -- 3 years ago.
So... since docs are now on access.redhat.com and N&N are on tools.jboss.org (in jbosstools-website), maybe it's time to terminate this project and move the ONE active file into another project?
Could move it to jbosstools-webite, where all the N&N stuff lives, or we could move it to jbosstools-build-ci, where all the other python/jira scripts live.
was:
Since December of 2014, the only file that's been changed in the jbosstools-documentation repo is ...
https://github.com/jbosstools/jbosstools-documentation/blob/master/whatsn...
In fact, the last time the repo was tagged was for JBoss Tools 4.1.0.Final -- 3 years ago.
So... since docs are now on access.redhat.com and N&N are on tools.jboss.org (in jbosstools-website), maybe it's time to terminate this project and move the ONE active file into another project?
Could move it to jbosstools-webite, where all the N&N stuff lives, or we could move it to jbosstools-build-ci, where all the other python/jira scripts live.
> move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23012
> URL: https://issues.jboss.org/browse/JBIDE-23012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
>
> Since July 2014, the only file that's been changed in the jbosstools-documentation repo is ...
> https://github.com/jbosstools/jbosstools-documentation/blob/master/whatsn...
> In fact, the last time the repo was tagged was for JBoss Tools 4.1.0.Final -- 3 years ago.
> So... since docs are now on access.redhat.com and N&N are on tools.jboss.org (in jbosstools-website), maybe it's time to terminate this project and move the ONE active file into another project?
> Could move it to jbosstools-webite, where all the N&N stuff lives, or we could move it to jbosstools-build-ci, where all the other python/jira scripts live.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22425) Unable to run offline script on windows
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22425?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-22425.
---------------------------------
Resolution: Done
Fixed in master. &'s are escaped to \u0026 values
> Unable to run offline script on windows
> ---------------------------------------
>
> Key: JBIDE-22425
> URL: https://issues.jboss.org/browse/JBIDE-22425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.4.0.Alpha2
> Environment: JBDS 10.0.0.Alpha2
> Windows 10
> {noformat}
> C:\>java -version
> openjdk version "1.8.0_91-2-redhat"
> OpenJDK Runtime Environment (build 1.8.0_91-2-redhat-b14)
> OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
> C:\>groovy -version
> Groovy Version: 2.4.6 JVM: 1.8.0_91-2-redhat Vendor: Oracle Corporation OS: Windows 10
> C:\>mvn -version
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: C:\Users\jboss-qa\programs\apache-maven-3.3.9\bin\..
> Java version: 1.8.0_91-2-redhat, vendor: Oracle Corporation
> Java home: C:\java-1.8.0-openjdk-1.8.0.91-2.b14.windows.x86_64\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
> {noformat}
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Fix For: 4.4.1.AM3
>
>
> Output of groovy script:
> {noformat}
> C:\Users\jboss-qa\temp\offline>groovy -Dgrape.config="C:\Users\jboss-qa\workspace\.metadata\.plugins\org.jboss.tools.project.examples\offline\jbossToolsGrapeConfig_3.1.0.Alpha1_v20160510_1913_B866.xml" "C:\Users\jboss-qa\workspace\.metadata\.plugins\org.jboss.tools.project.examples\offline\go_offline_3.1.0.Alpha1_v20160510_1913_B866.groovy" http://download.jboss.org/jbosstools/examples/4/4/project-examples-catego... http://download.jboss.org/jbosstools/examples/4/4/project-examples-devstu... http://download.jboss.org/gatein/quickstarts/jboss-portal-6.2/project-exa... http://download.jboss.org/jbosstools/examples/4/4/project-examples-shared... -u "http://dcp.jboss.org/v1/rest/search^?content_provider=jboss-developer&con..." -q -e
> 'content_provider' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> Invalid parameter(s)
> QUERY { PROCESS | SESSION | TERMSERVER | USER }
> 'size' is not recognized as an internal or external command,
> operable program or batch file.
> ^CTerminate batch job (Y/N)? Y{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22425) Unable to run offline script on windows
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22425?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22425:
-----------------------------------
Fix Version/s: 4.4.1.AM3
Story Points: 4
Sprint: devex #118 July 2016
Assignee: Fred Bricon
> Unable to run offline script on windows
> ---------------------------------------
>
> Key: JBIDE-22425
> URL: https://issues.jboss.org/browse/JBIDE-22425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.4.0.Alpha2
> Environment: JBDS 10.0.0.Alpha2
> Windows 10
> {noformat}
> C:\>java -version
> openjdk version "1.8.0_91-2-redhat"
> OpenJDK Runtime Environment (build 1.8.0_91-2-redhat-b14)
> OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode)
> C:\>groovy -version
> Groovy Version: 2.4.6 JVM: 1.8.0_91-2-redhat Vendor: Oracle Corporation OS: Windows 10
> C:\>mvn -version
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: C:\Users\jboss-qa\programs\apache-maven-3.3.9\bin\..
> Java version: 1.8.0_91-2-redhat, vendor: Oracle Corporation
> Java home: C:\java-1.8.0-openjdk-1.8.0.91-2.b14.windows.x86_64\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "dos"
> {noformat}
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Fix For: 4.4.1.AM3
>
>
> Output of groovy script:
> {noformat}
> C:\Users\jboss-qa\temp\offline>groovy -Dgrape.config="C:\Users\jboss-qa\workspace\.metadata\.plugins\org.jboss.tools.project.examples\offline\jbossToolsGrapeConfig_3.1.0.Alpha1_v20160510_1913_B866.xml" "C:\Users\jboss-qa\workspace\.metadata\.plugins\org.jboss.tools.project.examples\offline\go_offline_3.1.0.Alpha1_v20160510_1913_B866.groovy" http://download.jboss.org/jbosstools/examples/4/4/project-examples-catego... http://download.jboss.org/jbosstools/examples/4/4/project-examples-devstu... http://download.jboss.org/gatein/quickstarts/jboss-portal-6.2/project-exa... http://download.jboss.org/jbosstools/examples/4/4/project-examples-shared... -u "http://dcp.jboss.org/v1/rest/search^?content_provider=jboss-developer&con..." -q -e
> 'content_provider' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> 'field' is not recognized as an internal or external command,
> operable program or batch file.
> Invalid parameter(s)
> QUERY { PROCESS | SESSION | TERMSERVER | USER }
> 'size' is not recognized as an internal or external command,
> operable program or batch file.
> ^CTerminate batch job (Y/N)? Y{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22382:
-------------------------------------
Reassigning to [~james.cobb] so he can provide us with a new icon. Please assign it back to me when you're done.
> Use different icons for EAP server and Red Hat Central
> ------------------------------------------------------
>
> Key: JBIDE-22382
> URL: https://issues.jboss.org/browse/JBIDE-22382
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Priority: Minor
> Labels: respin-a
> Fix For: 4.4.1.Final
>
> Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png
>
>
> If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22382) Use different icons for EAP server and Red Hat Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22382?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22382:
-----------------------------------
Assignee: James Cobb (was: Fred Bricon)
> Use different icons for EAP server and Red Hat Central
> ------------------------------------------------------
>
> Key: JBIDE-22382
> URL: https://issues.jboss.org/browse/JBIDE-22382
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: James Cobb
> Priority: Minor
> Labels: respin-a
> Fix For: 4.4.1.Final
>
> Attachments: central-rhd-icon.png, fullIDE.png, tools_rebrand.png
>
>
> If there is an EAP server present in Servers view, workbench tool bar contains 2 same icons - Select a default server icon is same as Red Hat Central icon. We should make this explicitly different.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22992) OpenShift tools use wrong rest client bits
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22992?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22992:
--------------------------------
Sprint: devex #118 July 2016 (was: devex #119 August 2016)
> OpenShift tools use wrong rest client bits
> ------------------------------------------
>
> Key: JBIDE-22992
> URL: https://issues.jboss.org/browse/JBIDE-22992
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.1.AM3
> Environment: eclipse.buildId=10.1.0.AM3-v20160810-0441-B5735
> java.version=1.8.0_101
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> Reporter: Denis Golovin
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.4.1.Final
>
> Attachments: IU-unchanged-not-published.png, openshift-client-IU-new-timestamp.png, openshift-client-IU.png
>
>
> An internal error occurred during: "Loading service-manager to configure additional frameworks that CDK depends on.".{code}java.lang.NoSuchMethodError: com.openshift.restclient.ClientBuilder.withMaxRequests(I)Lcom/openshift/restclient/ClientBuilder;
> at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:53)
> at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:77)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:55)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureOpenshift(ConfigureDependentFrameworksListener.java:91)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:56)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:44)
> 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