July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-340) Unable to start elasticsearch instance in B24

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-340?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-340. ------------------------------------------- Resolution: Done > Unable to start elasticsearch instance in B24 > --------------------------------------------- > > Key: SWSQE-340 > URL: https://issues.jboss.org/browse/SWSQE-340 > Project: Kiali QE > Issue Type: Bug > Reporter: Jeeva Kandasamy > Assignee: Guilherme Baufaker Rêgo > > Unable to start Elastic search instance in B24, throws the following error, > Namespace: https://b24.jonqe.lab.eng.bos.redhat.com:8443/console/project/jaeger-test2 > {code:text} > create Pod elasticsearch-0 in StatefulSet elasticsearch failed error: Internal error occurred: failed calling admission webhook "sidecar-injector.istio.io": Post https://istio-sidecar-injector.istio-system.svc:443/inject?timeout=30s: dial tcp: lookup istio-sidecar-injector.istio-system.svc on 10.16.23.50:53: no such host > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-340) Unable to start elasticsearch instance in B24

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-340?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-340: ----------------------------------------------- [~jkandasa] I've removed this admission webhook. You may try to reinstall. If that happens again you can workaround with: {code:shell} oc delete mutatingwebhookconfiguration istio-sidecar-injector {code} > Unable to start elasticsearch instance in B24 > --------------------------------------------- > > Key: SWSQE-340 > URL: https://issues.jboss.org/browse/SWSQE-340 > Project: Kiali QE > Issue Type: Bug > Reporter: Jeeva Kandasamy > Assignee: Guilherme Baufaker Rêgo > > Unable to start Elastic search instance in B24, throws the following error, > Namespace: https://b24.jonqe.lab.eng.bos.redhat.com:8443/console/project/jaeger-test2 > {code:text} > create Pod elasticsearch-0 in StatefulSet elasticsearch failed error: Internal error occurred: failed calling admission webhook "sidecar-injector.istio.io": Post https://istio-sidecar-injector.istio-system.svc:443/inject?timeout=30s: dial tcp: lookup istio-sidecar-injector.istio-system.svc on 10.16.23.50:53: no such host > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-340) Unable to start elasticsearch instance in B24

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-340?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-340: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Unable to start elasticsearch instance in B24 > --------------------------------------------- > > Key: SWSQE-340 > URL: https://issues.jboss.org/browse/SWSQE-340 > Project: Kiali QE > Issue Type: Bug > Reporter: Jeeva Kandasamy > Assignee: Guilherme Baufaker Rêgo > > Unable to start Elastic search instance in B24, throws the following error, > Namespace: https://b24.jonqe.lab.eng.bos.redhat.com:8443/console/project/jaeger-test2 > {code:text} > create Pod elasticsearch-0 in StatefulSet elasticsearch failed error: Internal error occurred: failed calling admission webhook "sidecar-injector.istio.io": Post https://istio-sidecar-injector.istio-system.svc:443/inject?timeout=30s: dial tcp: lookup istio-sidecar-injector.istio-system.svc on 10.16.23.50:53: no such host > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-341) Pipeline Support For Productized Jaeger

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-341: ---------------------------------- Summary: Pipeline Support For Productized Jaeger Key: SWSQE-341 URL: https://issues.jboss.org/browse/SWSQE-341 Project: Kiali QE Issue Type: Sub-task Reporter: Matt Mahoney Assignee: Michael Foley -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELYWEB-4) Upgrade WildFly Elytron to 1.4.0.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELYWEB-4?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELYWEB-4. ----------------------------------- Fix Version/s: 1.2.0.Final (was: 1.2.1.CR1) Resolution: Done > Upgrade WildFly Elytron to 1.4.0.Final > -------------------------------------- > > Key: ELYWEB-4 > URL: https://issues.jboss.org/browse/ELYWEB-4 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-304) Kiali Builder is not deploying other Branches

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-304?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan closed SWSQE-304. -------------------------------- Resolution: Done reopen it if it happens again > Kiali Builder is not deploying other Branches > ---------------------------------------------- > > Key: SWSQE-304 > URL: https://issues.jboss.org/browse/SWSQE-304 > Project: Kiali QE > Issue Type: QE Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Hayk Hovsepyan > > - If you try to deploy a different tag than latest, you will find this issue > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-59) Enable CDI by default when MP Config usage is detected in the deployment

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFWIP-59?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil commented on WFWIP-59: ---------------------------------- That seems backwards to me. We only register CDI extension if CDI is enabled (more accurately if it is part of a Weld deployment), not the other way around. That's how it is done for JPA, JMS and JSF (note that it is also possible to use MicroProfile Config without CDI but it's a minor use case). > Enable CDI by default when MP Config usage is detected in the deployment > ------------------------------------------------------------------------ > > Key: WFWIP-59 > URL: https://issues.jboss.org/browse/WFWIP-59 > Project: WildFly WIP > Issue Type: Enhancement > Components: MP Config > Reporter: Rostislav Svoboda > Assignee: Jeff Mesnil > Priority: Critical > > Enable CDI by default when MP Config usage is detected in the deployment. > Currently users are forced to add empty {{beans.xml}} to the deployment every time they want to use MP Config - e.g. in simple servlet scenario > {code} > @WebServlet("/") > public class HelloServlet extends HttpServlet { > @Inject > @ConfigProperty(name = "port_number") > Integer port; > @Override > protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws IOException { > resp.getWriter().println("Value of port: " + port); > } > } > {code} > MP Config without CDI makes no sense to me. MP Config subsystem should be able to ensure CDI is enabled. CCing [~manovotn] [~brian.stansberry] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2707) CSS for test results panel/dock design

by Sarah Rambacher (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2707?page=com.atlassian.jira.plugi... ] Sarah Rambacher commented on DROOLS-2707: ----------------------------------------- Yes - that's not one of the chart options as far as I could tell, but someone that can dig into the Javascript could probably add it easily if needed. > CSS for test results panel/dock design > -------------------------------------- > > Key: DROOLS-2707 > URL: https://issues.jboss.org/browse/DROOLS-2707 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-05 at 11.33.41 AM.png, Screen Shot 2018-07-11 at 3.03.50 PM.png > > > As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules. > *Verification conditions:* > - CSS styles that employ relevant PatternFly styles and/or patterns, such as: http://www.patternfly.org/pattern-library/data-visualization/donut-chart/... > - CSS that articulates the design wireframe attached, and: > https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476070 > https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX... > - Reviewed by scrum team prior to PR/dev delivery. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-59) Enable CDI by default when MP Config usage is detected in the deployment

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFWIP-59: -------------------------------------- Summary: Enable CDI by default when MP Config usage is detected in the deployment Key: WFWIP-59 URL: https://issues.jboss.org/browse/WFWIP-59 Project: WildFly WIP Issue Type: Enhancement Components: MP Config Reporter: Rostislav Svoboda Assignee: Jeff Mesnil Priority: Critical Enable CDI by default when MP Config usage is detected in the deployment. Currently users are forced to add empty {{beans.xml}} to the deployment every time they want to use MP Config - e.g. in simple servlet scenario {code} @WebServlet("/") public class HelloServlet extends HttpServlet { @Inject @ConfigProperty(name = "port_number") Integer port; @Override protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws IOException { resp.getWriter().println("Value of port: " + port); } } {code} MP Config without CDI makes no sense to me. MP Config subsystem should be able to ensure CDI is enabled. CCing [~manovotn] [~brian.stansberry] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2671) Find a way how to write integration tests for Canvas

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2671?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2671: --------------------------------- Summary: Find a way how to write integration tests for Canvas (was: Find a way how to test wider integration scenarios.) > Find a way how to write integration tests for Canvas > ---------------------------------------------------- > > Key: DROOLS-2671 > URL: https://issues.jboss.org/browse/DROOLS-2671 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Juraj Soltes > > An inspiration -> document about Lienzo testing: https://docs.google.com/document/d/1glJ6zccSH2fRB9ymmMC8mGIaqEeK2dXraQVbK... > Acceptance criteria: A way (or several ways) how to test the Lienzo based system on integration level is discovered. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 July 2018