September 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-26858) Implement missing CDK unit tests

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26858?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-26858: --------------------------------------- [~jeffmaury] [~adietish] [~rob.stryker] Anyone willing to take care of this, this sprint? If not, please move to another relevant fix version. > Implement missing CDK unit tests > -------------------------------- > > Key: JBIDE-26858 > URL: https://issues.jboss.org/browse/JBIDE-26858 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Priority: Major > Fix For: 4.13.0.Final > > > There are missing unit test that require our attention. Ie. CDKServerWizardFragment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26858) Implement missing CDK unit tests

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26858?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26858: ---------------------------------- Fix Version/s: 4.13.0.Final (was: 4.14.x) > Implement missing CDK unit tests > -------------------------------- > > Key: JBIDE-26858 > URL: https://issues.jboss.org/browse/JBIDE-26858 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Priority: Major > Fix For: 4.13.0.Final > > > There are missing unit test that require our attention. Ie. CDKServerWizardFragment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26878) Improve validation of Pull Secret File in CRC Server Wizard and Editor

by Ondrej Dockal (Jira)

Ondrej Dockal created JBIDE-26878: ------------------------------------- Summary: Improve validation of Pull Secret File in CRC Server Wizard and Editor Key: JBIDE-26878 URL: https://issues.jboss.org/browse/JBIDE-26878 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: cdk Affects Versions: 4.13.0.Final Reporter: Ondrej Dockal Assignee: Rob Stryker Fix For: 4.13.0.Final I can image improved validation of Pull secret file that is available in CRC Server wizard and Server Editor. I can imagine all of those validation in action for pull secret path input: * Path does not exist * Is not a file * Is not executable (user cannot read the file) * Is not a valid Pull secret file (probably check for if file's content is a valid json and/or we can probably validate if json's first object is "auths"? This would be nice, but simple json validation seems fine) I believe that last three points could be validated at once by reading the file's content and creating valid json object, or else showing the error that given path is no valid a secret file. It's up implementation, right? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4798) Warning: Illegal reflective access operation has occured

by Ondrej Dockal (Jira)

Ondrej Dockal created JBDS-4798: ----------------------------------- Summary: Warning: Illegal reflective access operation has occured Key: JBDS-4798 URL: https://issues.jboss.org/browse/JBDS-4798 Project: Red Hat CodeReady Studio (devstudio) Issue Type: Bug Components: installer Affects Versions: 12.13.0.AM1 Reporter: Ondrej Dockal Assignee: Jeff MAURY Fix For: 12.x When running the installer jar I got warning when on java 11. {code} WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.izforge.izpack.installer.InstallerFrame (file:/home/odockal/Downloads/codereadystudio-12.13.0.GA-v20190929-1916-B5040-installer-standalone.jar) to field sun.awt.X11.XToolkit.awtAppClassName WARNING: Please consider reporting this to the maintainers of com.izforge.izpack.installer.InstallerFrame WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26868) Connection wizard: errors when login to https://api.openshift4-crs.crs.codereadyqe.com

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26868?page=com.atlassian.jira.plugi... ] André Dietisheim commented on JBIDE-26868: ------------------------------------------ According to [~jkopriva] this is an issue of configuration in the cluster. There thus isn't anything that we can fix in Eclipse/openshift-restclient-java. Postponing to after 4.13.Final so that josef can fix those and test again. > Connection wizard: errors when login to https://api.openshift4-crs.crs.codereadyqe.com > -------------------------------------------------------------------------------------- > > Key: JBIDE-26868 > URL: https://issues.jboss.org/browse/JBIDE-26868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.13.0.AM1 > Environment: https://console-openshift-console.apps.openshift4-crs.crs.codereadyqe.com/ > (created with openshift installer on openstack) > Reporter: André Dietisheim > Assignee: Josef Kopriva > Priority: Major > Labels: connection_wizard > Fix For: 4.14.x > > > Steps: > # EXEC: (VPN required) go to https://console-openshift-console.apps.openshift4-crs.crs.codereadyqe.com/ and login using: htpasswd > developer/developer > # EXEC: once logged in, pick "Copy Login Command" from the menu in the top right corner - you'll have to log in again and hit "Display Token". You'll get a command displayed that you'll have to copy: > {code} > oc login --token=XXXXXX --server=https://api.openshift4-crs.crs.codereadyqe.com:6443 > {code} > # EXEC: open connection wizard, hit "Paste Login Command" button & pick "Finish" > Result: > {code} > com.openshift.restclient.authorization.ResourceForbiddenException: forbidden: User "system:anonymous" cannot get path "/apis" forbidden: User "system:anonymous" cannot get path "/apis" > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:111) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:66) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184) > at okhttp3.RealCall.execute(RealCall.kt:66) > at com.openshift.internal.restclient.ApiTypeMapper.request(ApiTypeMapper.java:265) > at com.openshift.internal.restclient.ApiTypeMapper.readEndpoint(ApiTypeMapper.java:257) > at com.openshift.internal.restclient.ApiTypeMapper.getApiGroups(ApiTypeMapper.java:220) > at com.openshift.internal.restclient.ApiTypeMapper.init(ApiTypeMapper.java:155) > at com.openshift.internal.restclient.ApiTypeMapper.isSupported(ApiTypeMapper.java:84) > at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:148) > at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:301) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:243) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:226) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:423) > at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:63) > at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:237) > at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:300) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:434) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26876?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26876: ------------------------------------- Summary: Explorer: ctx menu "Show In" > "Web Console" for CRC fails with "unauthorized" (was: Explorer: Show In > Web Console for CRC fails with "unauthorized") > Explorer: ctx menu "Show In" > "Web Console" for CRC fails with "unauthorized" > ------------------------------------------------------------------------------ > > 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, 11 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: ------------------------------------- Summary: Explorer: ctx menu "Show In" > "Web Console" fails with "unauthorized" for CRC (was: Explorer: ctx menu "Show In" > "Web Console" for CRC fails with "unauthorized") > 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, 11 months

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26876?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-26876 at 9/27/19 2:48 PM: ------------------------------------------------------------------- To have these url mappings done right, we'd need to know the version of the OpenShift that we're talking to. For CRC, this seems not to be doable at the moment unless we simply assume that if the client has no OpenShift cluster version, it'll be OpenShift 4: JBIDE-26877 was (Author: adietish): To have these url mappings done right, we'd need to know the version of the OpenShift that we're talking to. For CRC, this seems not to be doable at the moment: JBIDE-26877 > Explorer: Show In > Web Console for CRC fails with "unauthorized" > ----------------------------------------------------------------- > > 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, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26877) Connection, OpenShift 4/CRC: wont show OpenShift master version

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26877?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-26877 at 9/27/19 10:44 AM: -------------------------------------------------------------------- This problem exists not only for CRC but also for the OpenShift 4 cluster that CHE QE is using. So this is not CRC specific. The very same problem can be observed with the oc command line - there's apparently no OpenShift version being reported: {code} $ ~/.crc/bin/oc get clusterversion Error from server (Forbidden): clusterversions.config.openshift.io is forbidden: User "andre" cannot list resource "clusterversions" in API group "config.openshift.io" at the cluster scope $ ~/.crc/bin/oc version Client Version: v4.2.0 Kubernetes Version: v1.13.4+f61b934 {code} was (Author: adietish): This problem exists not only for CRC but also for the OpenShift 4 cluster that CHE QE is using. So this is not CRC specific. The very same problem can be observed with the oc command line - there's apparently no OpenShift version being reported: ``` $ ~/.crc/bin/oc get clusterversion Error from server (Forbidden): clusterversions.config.openshift.io is forbidden: User "andre" cannot list resource "clusterversions" in API group "config.openshift.io" at the cluster scope $ ~/.crc/bin/oc version Client Version: v4.2.0 Kubernetes Version: v1.13.4+f61b934 ``` > Connection, OpenShift 4/CRC: wont show OpenShift master version > --------------------------------------------------------------- > > Key: JBIDE-26877 > URL: https://issues.jboss.org/browse/JBIDE-26877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.14.x > > Attachments: image-2019-09-27-15-47-36-396.png, properties-crc.png > > > Here's how OpenShift Master Version looks for CRC (OpenShift 4): > !properties-crc.png! > Here's how OpenShift Master Version is reported for employee.openshift.com (OpenShift 3.11 currently): > !image-2019-09-27-15-47-36-396.png! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26877) Connection, OpenShift 4/CRC: wont show OpenShift master version

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26877?page=com.atlassian.jira.plugi... ] André Dietisheim edited comment on JBIDE-26877 at 9/27/19 10:43 AM: -------------------------------------------------------------------- This problem exists not only for CRC but also for the OpenShift 4 cluster that CHE QE is using. So this is not CRC specific. The very same problem can be observed with the oc command line - there's apparently no OpenShift version being reported: ``` $ ~/.crc/bin/oc get clusterversion Error from server (Forbidden): clusterversions.config.openshift.io is forbidden: User "andre" cannot list resource "clusterversions" in API group "config.openshift.io" at the cluster scope $ ~/.crc/bin/oc version Client Version: v4.2.0 Kubernetes Version: v1.13.4+f61b934 ``` was (Author: adietish): This problem exists not only for CRC but also for the OpenShift 4 cluster that CHE QE is using. So this is not CRC specific. > Connection, OpenShift 4/CRC: wont show OpenShift master version > --------------------------------------------------------------- > > Key: JBIDE-26877 > URL: https://issues.jboss.org/browse/JBIDE-26877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.14.x > > Attachments: image-2019-09-27-15-47-36-396.png, properties-crc.png > > > Here's how OpenShift Master Version looks for CRC (OpenShift 4): > !properties-crc.png! > Here's how OpenShift Master Version is reported for employee.openshift.com (OpenShift 3.11 currently): > !image-2019-09-27-15-47-36-396.png! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 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 September 2019