April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24373) Can't push an image to the CDK3 Docker registry

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24373?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24373: ------------------------------- Sprint: devex #131 April 2017 > Can't push an image to the CDK3 Docker registry > ----------------------------------------------- > > Key: JBIDE-24373 > URL: https://issues.jboss.org/browse/JBIDE-24373 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.4.Final > > > Pushing an image to the CDK3 Docker registry is not possible. When the image is tagged, the registry port is not used thus Docker will try to contact the CDK Docker registry in port 80 causing a timeout to occur at the UI level. > Steps to reproduce: > # Create a Docker and OpenShift connection to CDK3 (using the server adapter or manually) > # Edit the OpenShift connection and add http://172.30.1.1:5000 as the registry address > # Build your own Docker image on the CDK3 Docker connection > # Deploy that image and select Push to registry: a timeout will occur after 30s -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24084) To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24084?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24084: ----------------------------------------- based on the comment https://github.com/minishift/minishift/issues/356#issuecomment-295129334 the workaround might be to add the user to the Hyper-V admin group during installation with Dev Suite installer. It allows at least something working when using the installer, it is not solving the issue of using JBDS directly and adding a new CDK server. In this case, when starting the CDK server, we might check that the user is admin or in the admin Hyper-V group to guide user on what he needs to achieve. > To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-24084 > URL: https://issues.jboss.org/browse/JBIDE-24084 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM1 > Environment: Windows 10 Pro, x86_64 > HyperV allowed > Reporter: Ondrej Dockal > Priority: Blocker > Fix For: 4.4.4.Final > > > One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE (admin rights are not required). > I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-940) Create a test for checking whether a runtime detection also creates a server

by Dominik Jelinek (JIRA)

[ https://issues.jboss.org/browse/JBTIS-940?page=com.atlassian.jira.plugin.... ] Dominik Jelinek commented on JBTIS-940: --------------------------------------- Use system parameters for jboss.org user/password in tests... > Create a test for checking whether a runtime detection also creates a server > ---------------------------------------------------------------------------- > > Key: JBTIS-940 > URL: https://issues.jboss.org/browse/JBTIS-940 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Final > Reporter: Andrej Podhradsky > Assignee: Dominik Jelinek > > Create a test for checking whether a runtime detections also creates a server. For more info please see FUSETOOLS-2176. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24301) Error While Executing jbosstools-openshift-4.4.3

by jyoti tumsare (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] jyoti tumsare commented on JBIDE-24301: --------------------------------------- Why it is always give me error Missing requirement. I am using EClipse neon 4.6.2 version > Error While Executing jbosstools-openshift-4.4.3 > ------------------------------------------------ > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > Attachments: issues.PNG, issues.txt > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24301) Error While Executing jbosstools-openshift-4.4.3

by jyoti tumsare (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] jyoti tumsare commented on JBIDE-24301: --------------------------------------- Can you please send me the link of jbosstools-openshift-4.4.4 source code link. > Error While Executing jbosstools-openshift-4.4.3 > ------------------------------------------------ > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > Attachments: issues.PNG, issues.txt > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24301) Error While Executing jbosstools-openshift-4.4.3

by jyoti tumsare (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] jyoti tumsare commented on JBIDE-24301: --------------------------------------- I tried a lot to build jbosstools-base source code. I add all possible plugin in eclipse->plugin folder required for the jbosstools-base still it give me error i.e. missing requirement.please help me why it is happened. > Error While Executing jbosstools-openshift-4.4.3 > ------------------------------------------------ > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > Attachments: issues.PNG, issues.txt > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23869: ------------------------------------- upstream origin has responded: https://github.com/openshift/origin/issues/13929#event-1061484579 They rejected it out of hand, and said no way. 2badsosad. ... ... we depend on jolokia client fix now i guess :| > ClassCastException with Jolokia connection > ------------------------------------------ > > Key: JBIDE-23869 > URL: https://issues.jboss.org/browse/JBIDE-23869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: jmx, jolokia, openshift > Fix For: 4.4.4.Final > > Attachments: image-2017-02-06-13-54-27-708.png > > > !image-2017-02-06-13-54-27-708.png|thumbnail! > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24374) Create test of devstudio installation using p2director

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24374?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-24374. -------------------------------- Resolution: Duplicate Dup to JBIDE-24372 > Create test of devstudio installation using p2director > ------------------------------------------------------ > > Key: JBIDE-24374 > URL: https://issues.jboss.org/browse/JBIDE-24374 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.4.4.Final > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.4.4.Final > > > Create test that will install devstudio using p2director to catch problem like JBDS-4377 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24372) Create test of devstudio installation using p2director

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24372?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-24372: --------------------------------- Sprint: devex #131 April 2017 > Create test of devstudio installation using p2director > ------------------------------------------------------ > > Key: JBIDE-24372 > URL: https://issues.jboss.org/browse/JBIDE-24372 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.4.4.Final > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.4.4.Final > > > Create test that will install devstudio using p2director to catch problem like JBDS-4377 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24374) Create test of devstudio installation using p2director

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-24374: ------------------------------------ Summary: Create test of devstudio installation using p2director Key: JBIDE-24374 URL: https://issues.jboss.org/browse/JBIDE-24374 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, qa Affects Versions: 4.4.4.Final Reporter: Lukáš Valach Assignee: Lukáš Valach Fix For: 4.4.4.Final Create test that will install devstudio using p2director to catch problem like JBDS-4377 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

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 April 2017