January 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26869) CRC server adapter: OpenShift connection that is created is unusable at times

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-26869?page=com.atlassian.jira.plug... ] André Dietisheim updated JBIDE-26869: ------------------------------------- Sprint: devex #173 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019, devex #178 Jan 2020 (was: devex #173 Oct 2019, devex #175 Nov 2019, devex #176 Nov/Dec 2019) > CRC server adapter: OpenShift connection that is created is unusable at times > ----------------------------------------------------------------------------- > > Key: JBIDE-26869 > URL: https://issues.redhat.com/browse/JBIDE-26869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Environment: CRC Beta5 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Critical > Fix For: 4.14.0.AM1 > > Attachments: crc-connection-error.mp4, start-crc-error-openshift-conn.mp4 > > > *Steps* - not reproducibe at 100%, happens from time to time: > # ASSERT: have ~/.crc folder killed > # EXEC: create new CRC server adapter & Start it > # ASSERT: OpenShift connection is created > *Result:* > Connection fails to authorize, reports that it cannot access resources using system:anonymous. Refreshing the connection doesn't help, so it's apparently not a timing issue (ex. creating the connection before the cluster is fully up and running) > {code} > com.openshift.restclient.authorization.ResourceForbiddenException: forbidden: User "system:anonymous" cannot get path "/oauth/authorize" forbidden: User "system:anonymous" cannot get path "/oauth/authorize" > 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.okhttp.OpenShiftAuthenticator.tryAuth(OpenShiftAuthenticator.java:109) > at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.authenticate(OpenShiftAuthenticator.java:62) > at okhttp3.internal.http.RetryAndFollowUpInterceptor.followUpRequest(RetryAndFollowUpInterceptor.kt:213) > at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:102) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112) > at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55) > 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.DefaultClient.request(DefaultClient.java:315) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:307) > 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.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureOpenshift(ConfigureCRCFrameworksListener.java:102) > at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureFrameworks(ConfigureCRCFrameworksListener.java:73) > at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener$1.run(ConfigureCRCFrameworksListener.java:66) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26995) Cont'd: Documenting QE - CI BP in use for CR Studio QE /Adapters

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26995?page=com.atlassian.jira.plug... ] Ondrej Dockal updated JBIDE-26995: ---------------------------------- Sprint: devex #178 Jan 2020 (was: devex #179 Jan/Feb 2020) > Cont'd: Documenting QE - CI BP in use for CR Studio QE /Adapters > ---------------------------------------------------------------- > > Key: JBIDE-26995 > URL: https://issues.redhat.com/browse/JBIDE-26995 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.14.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.14.0.AM1 > > > Cont'd of JBIDE-26788. Adding example adding new job, applying best practices, using templates and shared libraries. Usage of UMB triggering in pipelines. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26995) Cont'd: Documenting QE - CI BP in use for CR Studio QE /Adapters

by Ondrej Dockal (Jira)

Ondrej Dockal created JBIDE-26995: ------------------------------------- Summary: Cont'd: Documenting QE - CI BP in use for CR Studio QE /Adapters Key: JBIDE-26995 URL: https://issues.redhat.com/browse/JBIDE-26995 Project: Tools (JBoss Tools) Issue Type: Task Components: qa Affects Versions: 4.14.0.AM1 Reporter: Ondrej Dockal Assignee: Ondrej Dockal Fix For: 4.14.0.AM1 Cont'd of JBIDE-26788. Adding example adding new job, applying best practices, using templates and shared libraries. Usage of UMB triggering in pipelines. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26893) Create universal template and label that would accommodate different rhel needed by interop testing team

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26893?page=com.atlassian.jira.plug... ] Ondrej Dockal updated JBIDE-26893: ---------------------------------- Description: We would like to use universal label that would cover different rhel versions that are required by interop testing. The idea is that we will keep one/two label for interop testing slave: rhel-interop (and possibly for both stream, so rhel7-interop and rhel8-interop), which would have used image: rhel-interop-7(8)-snapshot that would have actually needed rhel version to test. During provisioning we will replace snapshot with proper rhel. This way we can keep these two labels and do not need to change interop test job label all the time via PR in cci-config repo. Reqs: * UMB trigger for interop rhel to run provision job with * job will be parametrized based on rhel version given by umb message * jenkins provisioning job build description needs to be updated to have available info about rhel version Pros: * do not need to change code via PR every time there is new bits to test * probably can be fully automated Cons: * only one version to test at a time * complex and possibly unstable? was: We would like to use universal label that would cover different rhel versions that are required by interop testing. The idea is that we will keep one/two label for interop testing slave: rhel-interop (and possibly for both stream, so rhel-interop-7 and rhel-interop-8), which would have used image: rhel-interop-7(8)-snapshot that would have actually needed rhel version to test. During provisioning we will replace snapshot with proper rhel. This way we can keep these two labels and do not need to change interop test job label all the time via PR in cci-config repo. Reqs: * UMB trigger for interop rhel to run provision job with * job will be parametrized based on rhel version given by umb message * jenkins provisioning job build description needs to be updated to have available info about rhel version Pros: * do not need to change code via PR every time there is new bits to test * probably can be fully automated Cons: * only one version to test at a time * complex and possibly unstable? > Create universal template and label that would accommodate different rhel needed by interop testing team > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26893 > URL: https://issues.redhat.com/browse/JBIDE-26893 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests, qa > Affects Versions: 4.13.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: jenkins > Fix For: 4.14.0.AM1 > > > We would like to use universal label that would cover different rhel versions that are required by interop testing. The idea is that we will keep one/two label for interop testing slave: rhel-interop (and possibly for both stream, so rhel7-interop and rhel8-interop), which would have used image: rhel-interop-7(8)-snapshot that would have actually needed rhel version to test. During provisioning we will replace snapshot with proper rhel. This way we can keep these two labels and do not need to change interop test job label all the time via PR in cci-config repo. > Reqs: > * UMB trigger for interop rhel to run provision job with > * job will be parametrized based on rhel version given by umb message > * jenkins provisioning job build description needs to be updated to have available info about rhel version > > Pros: > * do not need to change code via PR every time there is new bits to test > * probably can be fully automated > Cons: > * only one version to test at a time > * complex and possibly unstable? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4779) Server adapter: should be able to freely set a war name [JBIDE-26694]

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBDS-4779?page=com.atlassian.jira.plugin... ] André Dietisheim commented on JBDS-4779: ---------------------------------------- [~mgreenbe] any chance you'd find the time to test this please? > Server adapter: should be able to freely set a war name [JBIDE-26694] > --------------------------------------------------------------------- > > Key: JBDS-4779 > URL: https://issues.redhat.com/browse/JBDS-4779 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 12.11.0.GA > Environment: CodeReady Studio, as used with OpenShift > Reporter: Rick Wagner > Assignee: Jeff MAURY > Priority: Major > Fix For: 12.14.0.AM1 > > > The user does not have a choice in naming of deployment artifacts. See verbose description in community tracker JBIDE-26694. > [1] https://issues.jboss.org/browse/JBIDE-26694 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4786) Prepare sending UMB message for staging bits of Studio (JBoss Tools)

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBDS-4786?page=com.atlassian.jira.plugin... ] Ondrej Dockal updated JBDS-4786: -------------------------------- Sprint: devex #172 Sep 2019, devex #176 Nov/Dec 2019, devex #178 Jan 2020 (was: devex #172 Sep 2019, devex #176 Nov/Dec 2019) > Prepare sending UMB message for staging bits of Studio (JBoss Tools) > -------------------------------------------------------------------- > > Key: JBDS-4786 > URL: https://issues.redhat.com/browse/JBDS-4786 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Task > Components: installer > Affects Versions: 12.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: ci-trigger, qe-ci > Fix For: 12.14.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26788) Prepare write up of using & examples on jcasc + cci-config for codeready studio/adapters on PSI jenkins

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26788?page=com.atlassian.jira.plug... ] Ondrej Dockal updated JBIDE-26788: ---------------------------------- Sprint: devex #172 Sep 2019, devex #176 Nov/Dec 2019, devex #178 Jan 2020 (was: devex #172 Sep 2019, devex #176 Nov/Dec 2019) > Prepare write up of using & examples on jcasc + cci-config for codeready studio/adapters on PSI jenkins > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26788 > URL: https://issues.redhat.com/browse/JBIDE-26788 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.14.0.AM1 > > > Prepare short readme & docs of steps, procedures, examples, etc. for using jcasc [1] + codeready studio declaration repo [2] , all for usage on psi jenkins [3]. > [1]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc > [2]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config > [3]: https://issues.jboss.org/browse/JBIDE-26737 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26893) Create universal template and label that would accommodate different rhel needed by interop testing team

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26893?page=com.atlassian.jira.plug... ] Ondrej Dockal updated JBIDE-26893: ---------------------------------- Sprint: devex #178 Jan 2020 > Create universal template and label that would accommodate different rhel needed by interop testing team > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26893 > URL: https://issues.redhat.com/browse/JBIDE-26893 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests, qa > Affects Versions: 4.13.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: jenkins > Fix For: 4.14.0.AM1 > > > We would like to use universal label that would cover different rhel versions that are required by interop testing. The idea is that we will keep one/two label for interop testing slave: rhel-interop (and possibly for both stream, so rhel-interop-7 and rhel-interop-8), which would have used image: rhel-interop-7(8)-snapshot that would have actually needed rhel version to test. During provisioning we will replace snapshot with proper rhel. This way we can keep these two labels and do not need to change interop test job label all the time via PR in cci-config repo. > Reqs: > * UMB trigger for interop rhel to run provision job with > * job will be parametrized based on rhel version given by umb message > * jenkins provisioning job build description needs to be updated to have available info about rhel version > > Pros: > * do not need to change code via PR every time there is new bits to test > * probably can be fully automated > Cons: > * only one version to test at a time > * complex and possibly unstable? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26682) Configure trigger for new openstack rhel image and have our image-provisioning job automated

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26682?page=com.atlassian.jira.plug... ] Ondrej Dockal updated JBIDE-26682: ---------------------------------- Sprint: devex #178 Jan 2020 > Configure trigger for new openstack rhel image and have our image-provisioning job automated > -------------------------------------------------------------------------------------------- > > Key: JBIDE-26682 > URL: https://issues.redhat.com/browse/JBIDE-26682 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.14.x > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.14.0.AM1 > > > Find out openstack rhel image UMB message that is sent after image is built, trigger provisioning job and prepare proper configured rhel base image. > * find out umb message > * set up the job with the trigger > * prepare universal jenkins template for the image > * assure verification of the image before saving -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26893) Create universal template and label that would accommodate different rhel needed by interop testing team

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26893?page=com.atlassian.jira.plug... ] Ondrej Dockal updated JBIDE-26893: ---------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.14.x) > Create universal template and label that would accommodate different rhel needed by interop testing team > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26893 > URL: https://issues.redhat.com/browse/JBIDE-26893 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests, qa > Affects Versions: 4.13.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: jenkins > Fix For: 4.14.0.AM1 > > > We would like to use universal label that would cover different rhel versions that are required by interop testing. The idea is that we will keep one/two label for interop testing slave: rhel-interop (and possibly for both stream, so rhel-interop-7 and rhel-interop-8), which would have used image: rhel-interop-7(8)-snapshot that would have actually needed rhel version to test. During provisioning we will replace snapshot with proper rhel. This way we can keep these two labels and do not need to change interop test job label all the time via PR in cci-config repo. > Reqs: > * UMB trigger for interop rhel to run provision job with > * job will be parametrized based on rhel version given by umb message > * jenkins provisioning job build description needs to be updated to have available info about rhel version > > Pros: > * do not need to change code via PR every time there is new bits to test > * probably can be fully automated > Cons: > * only one version to test at a time > * complex and possibly unstable? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 January 2020