August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4609) Core threads in EnhancedQueueExecutor might timeout below core pool size even if allowCoreTimeOut is false

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFCORE-4609?page=com.atlassian.jira.plugi... ] Miroslav Novak commented on WFCORE-4609: ---------------------------------------- Yes, JBTHR-49 is fixed in 2.3.3.Final. This will be something else. > Core threads in EnhancedQueueExecutor might timeout below core pool size even if allowCoreTimeOut is false > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4609 > URL: https://issues.jboss.org/browse/WFCORE-4609 > Project: WildFly Core > Issue Type: Bug > Components: IO > Affects Versions: 10.0.0.Beta2 > Reporter: Miroslav Novak > Assignee: Flavia Rainone > Priority: Major > > I can see unexpected behavior in EnhancedQueueExecutor [1]. Even when I set allowsCoreThreadTimeOut to false, sometimes happens that pool size goes below core size by a few threads. > Test scenario: > - create EnhancedQueueExecutor with coreSize=3, maxSize=6, allowsCoreThreadTimeOut=false, keepAliveTimeout=1000ms > - submit 6 threads into executor and wait until all are running so maxSize is reached > - allow all threads to finish and wait some time for threads to timeout > Expected result is that poolSize will be 3 as coreSize=3 but sometimes happens that poolSize is 2 or 1. > This might not be a bug as EnhancedQueueExecutor estimates its pool size and might allow to timeout more threads than coreSize. I'm creating this jira so it's explained for future reference. > [1] https://github.com/jbossas/jboss-threads/blob/2.3.3.Final/src/main/java/o... > [2] https://issues.jboss.org/browse/EAP7-488 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-171) Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-171?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-171: ------------------------------------ As it is changing user interface for working with template I would prefere to add it under RFE process. I mean does it need documentation, tests? Given templates are going to be deprecated in favor of Operators, what is the priority of this change? Is there real demand for this change? > Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME > ------------------------------------------------------------ > > Key: WFWIP-171 > URL: https://issues.jboss.org/browse/WFWIP-171 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > Is it expected? Is this work tracked somewhere? > [1] https://github.com/jboss-container-images/jboss-eap-7-openshift-image/blo... > [2] https://github.com/luck3y/jboss-eap-7-openshift-image/blob/CLOUD-3331/tem... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-171) Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-171?page=com.atlassian.jira.plugin.... ] Martin Choma reopened WFWIP-171: -------------------------------- > Template eap73-sso-s2i contains new parameter SSO_IMAGE_NAME > ------------------------------------------------------------ > > Key: WFWIP-171 > URL: https://issues.jboss.org/browse/WFWIP-171 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > Is it expected? Is this work tracked somewhere? > [1] https://github.com/jboss-container-images/jboss-eap-7-openshift-image/blo... > [2] https://github.com/luck3y/jboss-eap-7-openshift-image/blob/CLOUD-3331/tem... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-936) Fix UI tests UI/REST health mishmatch

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-936?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-936: ------------------------------------- kiali-1.0 branch PR - https://github.com/Kiali-QE/kiali-qe-python/pull/191 > Fix UI tests UI/REST health mishmatch > ------------------------------------- > > Key: SWSQE-936 > URL: https://issues.jboss.org/browse/SWSQE-936 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: automation > > Some tests fail because of different health:HealthType displayed in UI and returned by rest. > UI by default shows Last 1 minute when showing health and rest was using > 10m by default which was causing mishmash and test failures. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-936) Fix UI tests UI/REST health mishmatch

by Filip Brychta (Jira)

Filip Brychta created SWSQE-936: ----------------------------------- Summary: Fix UI tests UI/REST health mishmatch Key: SWSQE-936 URL: https://issues.jboss.org/browse/SWSQE-936 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta Some tests fail because of different health:HealthType displayed in UI and returned by rest. UI by default shows Last 1 minute when showing health and rest was using 10m by default which was causing mishmash and test failures. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-898) Prepare for BOS lab outage

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-898?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-898. --------------------------------- Resolution: Done > Prepare for BOS lab outage > -------------------------- > > Key: SWSQE-898 > URL: https://issues.jboss.org/browse/SWSQE-898 > Project: Kiali QE > Issue Type: Story > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Critical > Labels: infrastructure > > There is an outage scheduled on Tuesday, August 20th and Wednesday the 21st. > This outage will affect jon/kiali qe infrastructure and following systems will not be accessible: > - https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/ > - http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/ > - https://foreman.jonqe.lab.eng.bos.redhat.com > - https://rhevm.jonqe.lab.eng.bos.redhat.com > - all Dell system b01 -- b25 > For JON it means following: > - no provisioning via foreman > - no jenkins jobs > For kiali it means following: > - no jenkins jobs (PR testing, nightly testing, provisioning of ocp4 in PSI, ...) > - ocp 3.11 clusters in bladecenter will not be available > - ocp 4 clusters in PSI will not be affected so manual testing will be possible but automatic provisioning of new cluster will not be available (jenkins will be down) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-920) Shut down machines before outage

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-920?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-920. --------------------------------- Resolution: Done Detailed steps - https://docs.google.com/document/d/1QRABnGYjgG9J0_QImiMPA78uL8NXmjLJbV864... > Shut down machines before outage > -------------------------------- > > Key: SWSQE-920 > URL: https://issues.jboss.org/browse/SWSQE-920 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Machines must be shut down gracefully according to prepared plan before the outage. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-177) Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-177?page=com.atlassian.jira.plugin.... ] Martin Choma edited comment on WFWIP-177 at 8/20/19 3:23 AM: ------------------------------------------------------------- It turned out it is caused by recent docker CVE fix. It is tracked by [1]. In OCP terms: - I see test fails on v3.11.129 (docker-1.13.1-103.git7f2769b.el7.x86_64) - I see test pass on v3.11.82, v3.11.117 (docker-1.13.1-96.gitb2f74b2.el7.x86_64) [1] https://bugzilla.redhat.com/show_bug.cgi?id=1738599 [2] https://github.com/openshift/source-to-image/issues/987 was (Author: mchoma): It turned out it is caused by recent docker CVE fix. It is tracked by [1]. In OCP terms: - I see test fails on v3.11.129 - I see test pass on v3.11.82, v3.11.117 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1738599 [2] https://github.com/openshift/source-to-image/issues/987 > Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink > -------------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-177 > URL: https://issues.jboss.org/browse/WFWIP-177 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > Use case is providing settings.xml as secret. I wonder if this could be some ubi7 file permission issue. > {code} > Receiving source from STDIN as archive ... > Using docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD... as the s2i builder image > error: Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366" > ERROR: Error occurred during injecting "/var/run/secrets/openshift.io/build/test-secret" to "/etc/test-secret": Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366" > error: build error: non-zero (13) exit code from docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD... > {code} > {code:yaml|title=BuildConfig} > apiVersion: build.openshift.io/v1 > kind: BuildConfig > metadata: > creationTimestamp: '2019-08-19T13:20:41Z' > name: sti-secret-settings > namespace: mchoma > resourceVersion: '1345248' > selfLink: >- > /apis/build.openshift.io/v1/namespaces/mchoma/buildconfigs/sti-secret-settings > uid: 249b6a94-c284-11e9-b93c-fa163e9a0fb6 > spec: > failedBuildsHistoryLimit: 5 > nodeSelector: {} > output: > to: > kind: ImageStreamTag > name: 'sti-secret-settings:latest' > postCommit: {} > resources: {} > runPolicy: Serial > source: > binary: {} > secrets: > - destinationDir: /etc/test-secret > secret: > name: test-secret > type: Binary > strategy: > sourceStrategy: > env: > - name: MAVEN_ARGS > value: install -s /etc/test-secret/settings.xml > from: > kind: DockerImage > name: >- > docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD... > incremental: false > type: Source > successfulBuildsHistoryLimit: 5 > triggers: > - generic: > allowEnv: true > secret: secret101 > type: Generic > status: > lastVersion: 1 > {code} > {code:yaml|title=Secret} > apiVersion: v1 > data: > settings.xml: >- > PHNldHRpbmdzPgogPHByb2ZpbGVzPiAgPHByb2ZpbGU+ICAgICA8aWQ+dGVzdDwvaWQ+ICAgICA8cmVwb3NpdG9yaWVzPiAgICAgICA8cmVwb3NpdG9yeT4gICAgICAgICA8aWQ+RUFQLTc8L2lkPiAgICAgICAgIDxuYW1lPkVBUDcgcmVwbzwvbmFtZT4gICAgICAgICA8dXJsPmh0dHBzOi8vbWF2ZW4ucmVwb3NpdG9yeS5yZWRoYXQuY29tL2dhLzwvdXJsPiAgICAgICA8L3JlcG9zaXRvcnk+ICAgICA8L3JlcG9zaXRvcmllcz4gICA8L3Byb2ZpbGU+ICA8L3Byb2ZpbGVzPiAgPGFjdGl2ZVByb2ZpbGVzPiAgICA8YWN0aXZlUHJvZmlsZT50ZXN0PC9hY3RpdmVQcm9maWxlPiA8L2FjdGl2ZVByb2ZpbGVzPiA8L3NldHRpbmdzPg== > kind: Secret > metadata: > creationTimestamp: '2019-08-19T13:20:41Z' > name: test-secret > namespace: mchoma > resourceVersion: '1345244' > selfLink: /api/v1/namespaces/mchoma/secrets/test-secret > uid: 246843e8-c284-11e9-b93c-fa163e9a0fb6 > type: Opaque > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-177) Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-177?page=com.atlassian.jira.plugin.... ] Martin Choma edited comment on WFWIP-177 at 8/20/19 3:21 AM: ------------------------------------------------------------- It turned out it is caused by recent docker CVE fix. It is tracked by [1]. In OCP terms: - I see test fails on v3.11.129 - I see test pass on v3.11.82, v3.11.117 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1738599 [2] https://github.com/openshift/source-to-image/issues/987 was (Author: mchoma): It turned out it is caused by recent docker CVE fix. It is tracked by [1]. In OCP terms: - I see test fails on v3.11.129 and v3.11.117 - I see test pass on v3.11.82 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1738599 [2] https://github.com/openshift/source-to-image/issues/987 > Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink > -------------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-177 > URL: https://issues.jboss.org/browse/WFWIP-177 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Ken Wills > Priority: Major > > Use case is providing settings.xml as secret. I wonder if this could be some ubi7 file permission issue. > {code} > Receiving source from STDIN as archive ... > Using docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD... as the s2i builder image > error: Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366" > ERROR: Error occurred during injecting "/var/run/secrets/openshift.io/build/test-secret" to "/etc/test-secret": Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366" > error: build error: non-zero (13) exit code from docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD... > {code} > {code:yaml|title=BuildConfig} > apiVersion: build.openshift.io/v1 > kind: BuildConfig > metadata: > creationTimestamp: '2019-08-19T13:20:41Z' > name: sti-secret-settings > namespace: mchoma > resourceVersion: '1345248' > selfLink: >- > /apis/build.openshift.io/v1/namespaces/mchoma/buildconfigs/sti-secret-settings > uid: 249b6a94-c284-11e9-b93c-fa163e9a0fb6 > spec: > failedBuildsHistoryLimit: 5 > nodeSelector: {} > output: > to: > kind: ImageStreamTag > name: 'sti-secret-settings:latest' > postCommit: {} > resources: {} > runPolicy: Serial > source: > binary: {} > secrets: > - destinationDir: /etc/test-secret > secret: > name: test-secret > type: Binary > strategy: > sourceStrategy: > env: > - name: MAVEN_ARGS > value: install -s /etc/test-secret/settings.xml > from: > kind: DockerImage > name: >- > docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD... > incremental: false > type: Source > successfulBuildsHistoryLimit: 5 > triggers: > - generic: > allowEnv: true > secret: secret101 > type: Generic > status: > lastVersion: 1 > {code} > {code:yaml|title=Secret} > apiVersion: v1 > data: > settings.xml: >- > PHNldHRpbmdzPgogPHByb2ZpbGVzPiAgPHByb2ZpbGU+ICAgICA8aWQ+dGVzdDwvaWQ+ICAgICA8cmVwb3NpdG9yaWVzPiAgICAgICA8cmVwb3NpdG9yeT4gICAgICAgICA8aWQ+RUFQLTc8L2lkPiAgICAgICAgIDxuYW1lPkVBUDcgcmVwbzwvbmFtZT4gICAgICAgICA8dXJsPmh0dHBzOi8vbWF2ZW4ucmVwb3NpdG9yeS5yZWRoYXQuY29tL2dhLzwvdXJsPiAgICAgICA8L3JlcG9zaXRvcnk+ICAgICA8L3JlcG9zaXRvcmllcz4gICA8L3Byb2ZpbGU+ICA8L3Byb2ZpbGVzPiAgPGFjdGl2ZVByb2ZpbGVzPiAgICA8YWN0aXZlUHJvZmlsZT50ZXN0PC9hY3RpdmVQcm9maWxlPiA8L2FjdGl2ZVByb2ZpbGVzPiA8L3NldHRpbmdzPg== > kind: Secret > metadata: > creationTimestamp: '2019-08-19T13:20:41Z' > name: test-secret > namespace: mchoma > resourceVersion: '1345244' > selfLink: /api/v1/namespaces/mchoma/secrets/test-secret > uid: 246843e8-c284-11e9-b93c-fa163e9a0fb6 > type: Opaque > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4434) Setup drools-wb for Sonar analysis

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4434?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-4434: ------------------------------------- Labels: ScenarioSimulation (was: ) > Setup drools-wb for Sonar analysis > ---------------------------------- > > Key: DROOLS-4434 > URL: https://issues.jboss.org/browse/DROOLS-4434 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Configure drools-wb to enable sonarcloud analysis on it -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 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

jboss-jira August 2019