October 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26857) Deploy to OpenShift: when pushing to registry, registry url is not informed

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26857?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26857: ------------------------------------- Fix Version/s: 4.14.x > Deploy to OpenShift: when pushing to registry, registry url is not informed > --------------------------------------------------------------------------- > > Key: JBIDE-26857 > URL: https://issues.jboss.org/browse/JBIDE-26857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Labels: deploy_docker_wizard > Fix For: 4.14.x > > > Steps: > # ASSERT: have a local docker image to deploy to OpenShift > # EXEC: in Docker Explorer, select your local docker image and pick "Deploy to OpenShift" > # ASSERT: deploy wizard pops up > Result: > There's a section in the wizard where you can choose to deploy the image to the docker registry on OpenShift. The username & password are informed but the docker registry is not informed, it's left blank. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26857) Deploy to OpenShift: when pushing to registry, registry url is not informed

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26857?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26857: ------------------------------------- Labels: deploy_docker_wizard (was: ) > Deploy to OpenShift: when pushing to registry, registry url is not informed > --------------------------------------------------------------------------- > > Key: JBIDE-26857 > URL: https://issues.jboss.org/browse/JBIDE-26857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Labels: deploy_docker_wizard > Fix For: 4.14.x > > > Steps: > # ASSERT: have a local docker image to deploy to OpenShift > # EXEC: in Docker Explorer, select your local docker image and pick "Deploy to OpenShift" > # ASSERT: deploy wizard pops up > Result: > There's a section in the wizard where you can choose to deploy the image to the docker registry on OpenShift. The username & password are informed but the docker registry is not informed, it's left blank. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26882) Central.itests fails due not blacklisted (but reported - JBIDE-26706) issue in Launcher Application project

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26882?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26882: ------------------------------------ Description: The *blacklist-launcher-application-errors-regexes.json* in central.itests is not updated (it needs to be updated for the *https://issues.jboss.org/browse/JBIDE-26706* issue) and also its current content needs to be reviewed and updated (old and not relevant entries needs to be removed). (was: The *blacklist-launcher-application-errors-regexes.json* in central.itests is not updated (needs to be updated for the *https://issues.jboss.org/browse/JBIDE-26706* issue) and also its current content needs to be reviewed and updated (remove old and not relevant entries).) > Central.itests fails due not blacklisted (but reported - JBIDE-26706) issue in Launcher Application project > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26882 > URL: https://issues.jboss.org/browse/JBIDE-26882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, integration-tests, project-examples > Affects Versions: 4.13.0.AM1 > Environment: OS X 10.14.6 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Minor > > The *blacklist-launcher-application-errors-regexes.json* in central.itests is not updated (it needs to be updated for the *https://issues.jboss.org/browse/JBIDE-26706* issue) and also its current content needs to be reviewed and updated (old and not relevant entries needs to be removed). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26882) Central.itests fails due not blacklisted (but reported - JBIDE-26706) issue in Launcher Application project

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26882?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26882: ------------------------------------ Description: The *blacklist-launcher-application-errors-regexes.json* in central.itests is not updated (needs to be updated for the *https://issues.jboss.org/browse/JBIDE-26706* issue) and also its current content needs to be reviewed and updated (remove old and not relevant entries). (was: The *blacklist-launcher-application-errors-regexes.json* in central.itests is not updated (needs to be updated for the *https://issues.jboss.org/browse/JBIDE-26706* issue)) > Central.itests fails due not blacklisted (but reported - JBIDE-26706) issue in Launcher Application project > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26882 > URL: https://issues.jboss.org/browse/JBIDE-26882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, integration-tests, project-examples > Affects Versions: 4.13.0.AM1 > Environment: OS X 10.14.6 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Minor > > The *blacklist-launcher-application-errors-regexes.json* in central.itests is not updated (needs to be updated for the *https://issues.jboss.org/browse/JBIDE-26706* issue) and also its current content needs to be reviewed and updated (remove old and not relevant entries). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26882) Central.itests fails due not blacklisted (but reported - JBIDE-26706) issue in Launcher Application project

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26882?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26882: ------------------------------------ Priority: Minor (was: Major) > Central.itests fails due not blacklisted (but reported - JBIDE-26706) issue in Launcher Application project > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26882 > URL: https://issues.jboss.org/browse/JBIDE-26882 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, integration-tests, project-examples > Affects Versions: 4.13.0.AM1 > Environment: OS X 10.14.6 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Minor > > The *blacklist-launcher-application-errors-regexes.json* in central.itests is not updated (needs to be updated for the *https://issues.jboss.org/browse/JBIDE-26706* issue) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4789) Disable "show method result after a step operation" by default

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4789?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4789: ------------------------------------- No matter, browsing the documentation the above changes should make preference property to be set. I continue digging... > Disable "show method result after a step operation" by default > -------------------------------------------------------------- > > Key: JBDS-4789 > URL: https://issues.jboss.org/browse/JBDS-4789 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Enhancement > Components: openshift, product > Affects Versions: 12.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 12.13.0.AM1 > > Attachments: show-method-result-after-step-operation.png > > > Stepping over code while debugging is very very slow in current Eclipse. Turns out that this is due to a preference setting that is enabled by default: > *show method result after a step operation* > !show-method-result-after-step-operation.png! > We thus should consider turning this off by default in CRStudio. > The issue is being reported/discussed in Eclipse bugs at https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported. Eclipse thus is considering turning it off by default: https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7 > This is especially painful when remote debugging applications in OpenShift: JBIDE-26794 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26876) Explorer: ctx menu "Show In" > "Web Console" fails with "unauthorized" for CRC

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26876?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26876: ------------------------------------------ this is fixed by a PR in the openshift-restclient at https://github.com/openshift/openshift-restclient-java/pull/401 and a change in the Eclipse tooling at https://github.com/jbosstools/jbosstools-openshift/pull/1882 > Explorer: ctx menu "Show In" > "Web Console" fails with "unauthorized" for CRC > ------------------------------------------------------------------------------ > > Key: JBIDE-26876 > URL: https://issues.jboss.org/browse/JBIDE-26876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > > Steps: > # ASSERT: have a connection to a running crc instance > # EXEC: in Explorer: select the connection and pick *Show In > Web Console* > Result: > Browser is opened to https://api.crc.testing:6443/console. Browser then displays: > {code} > { > "kind": "Status", > "apiVersion": "v1", > "metadata": { > > }, > "status": "Failure", > "message": "forbidden: User \"system:anonymous\" cannot get path \"/console\"", > "reason": "Forbidden", > "details": { > > }, > "code": 403 > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26876) Explorer: ctx menu "Show In" > "Web Console" fails with "unauthorized" for CRC

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26876?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26876: ------------------------------------- Git Pull Request: https://github.com/openshift/openshift-restclient-java/pull/401, https://github.com/jbosstools/jbosstools-openshift/pull/1882 (was: https://github.com/openshift/openshift-restclient-java/pull/401) > Explorer: ctx menu "Show In" > "Web Console" fails with "unauthorized" for CRC > ------------------------------------------------------------------------------ > > Key: JBIDE-26876 > URL: https://issues.jboss.org/browse/JBIDE-26876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > > Steps: > # ASSERT: have a connection to a running crc instance > # EXEC: in Explorer: select the connection and pick *Show In > Web Console* > Result: > Browser is opened to https://api.crc.testing:6443/console. Browser then displays: > {code} > { > "kind": "Status", > "apiVersion": "v1", > "metadata": { > > }, > "status": "Failure", > "message": "forbidden: User \"system:anonymous\" cannot get path \"/console\"", > "reason": "Forbidden", > "details": { > > }, > "code": 403 > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26876) Explorer: ctx menu "Show In" > "Web Console" fails with "unauthorized" for CRC

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26876?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26876: ------------------------------------------ [~odockal]: I found another issue that exists in the current url mapping for OpenShift 3 and is closely related: the following 2 resources open bad URLs causing a 404 in the console * deployments (wich are replication controllers) * routes Steps (for deployments/replication controllers - same applies for routes): # ASSERT: have a project with a replication controller and a route (ex. create an app from template) # EXEC: in OpenShift explorer: select the project # EXEC: open "Properties" view & select the "Deployments" tab # EXEC: in the context menu select "Show In > Web console" Result: Console shows up with an error "404 Not Found" > Explorer: ctx menu "Show In" > "Web Console" fails with "unauthorized" for CRC > ------------------------------------------------------------------------------ > > Key: JBIDE-26876 > URL: https://issues.jboss.org/browse/JBIDE-26876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > > Steps: > # ASSERT: have a connection to a running crc instance > # EXEC: in Explorer: select the connection and pick *Show In > Web Console* > Result: > Browser is opened to https://api.crc.testing:6443/console. Browser then displays: > {code} > { > "kind": "Status", > "apiVersion": "v1", > "metadata": { > > }, > "status": "Failure", > "message": "forbidden: User \"system:anonymous\" cannot get path \"/console\"", > "reason": "Forbidden", > "details": { > > }, > "code": 403 > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26817: ------------------------------------------ [~sbouchet-1] awesome, thanks! > link to "Get involved" shows the page for CAT that was suspended in 2016 > ------------------------------------------------------------------------ > > Key: JBIDE-26817 > URL: https://issues.jboss.org/browse/JBIDE-26817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png, issue.png > > > steps: > # ASSERT: have central opened > # EXEC: click on the link "Get involved" > !image-2019-09-09-21-39-10-326.png! > result: > browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016* > !image-2019-09-09-21-40-21-204.png! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2019