April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1126) Update kiali-build jenkins slave to use operator-sdk 0.17.0

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1126?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1126: ---------------------------------- Sprint: Kiali Sprint #38, Kiali Sprint #39 (was: Kiali Sprint #38) > Update kiali-build jenkins slave to use operator-sdk 0.17.0 > ----------------------------------------------------------- > > Key: SWSQE-1126 > URL: https://issues.redhat.com/browse/SWSQE-1126 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1127) Add OCP 4.5 to provisioning jobs

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1127?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1127: ---------------------------------- Sprint: Kiali Sprint #38, Kiali Sprint #39 (was: Kiali Sprint #38) > Add OCP 4.5 to provisioning jobs > -------------------------------- > > Key: SWSQE-1127 > URL: https://issues.redhat.com/browse/SWSQE-1127 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We need to add OCP 4.5 to UPI and IPI provisioning jobs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1060) Increase quota for volumes in istio-dev project

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1060?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1060: ---------------------------------- Sprint: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39 (was: Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38) > Increase quota for volumes in istio-dev project > ----------------------------------------------- > > Key: SWSQE-1060 > URL: https://issues.redhat.com/browse/SWSQE-1060 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > Jaeger team is using volumes for kafka and 2 TB quota is not enough. We need to increase it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-907) UI Automations - Fix random failures on master

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-907?page=com.atlassian.jira.plugin... ] Hayk Hovsepyan updated SWSQE-907: --------------------------------- Sprint: Kiali Sprint #26, Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39 (was: Kiali Sprint #26, Kiali Sprint #32, Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38) > UI Automations - Fix random failures on master > ---------------------------------------------- > > Key: SWSQE-907 > URL: https://issues.redhat.com/browse/SWSQE-907 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1129) Automate Masthead status

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1129?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1129: ---------------------------------- Sprint: Kiali Sprint #38, Kiali Sprint #39 (was: Kiali Sprint #38) > Automate Masthead status > ------------------------ > > Key: SWSQE-1129 > URL: https://issues.redhat.com/browse/SWSQE-1129 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1733 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-612) QE CI/CP Integration, best practices - stage 2

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-612?page=com.atlassian.jira.plugin... ] Hayk Hovsepyan updated SWSQE-612: --------------------------------- Sprint: Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38, Kiali Sprint #39 (was: Kiali Sprint #36, Kiali Sprint #37, Kiali Sprint #38) > QE CI/CP Integration, best practices - stage 2 > ---------------------------------------------- > > Key: SWSQE-612 > URL: https://issues.redhat.com/browse/SWSQE-612 > Project: Kiali QE > Issue Type: Story > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > This story is to track future tasks when the stage 1 is finished. > Tasks from this story might be worked simultaneously with stage 1 tasks but with lower priority. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-315) XP OpenShift image http management interface secured with no user by default

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFWIP-315?page=com.atlassian.jira.plugin... ] Jean Francois Denise commented on WFWIP-315: -------------------------------------------- [~mchoma], when the server starts, it applies the following script: https://github.com/wildfly/wildfly-cekit-modules/blob/0.18.4/jboss/contai... that unsecures the management interface. Could you check the standalone-openshift.xml file once the server has been started. > XP OpenShift image http management interface secured with no user by default > ---------------------------------------------------------------------------- > > Key: WFWIP-315 > URL: https://issues.redhat.com/browse/WFWIP-315 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Attachments: standalone-openshift.cd19.xml, standalone-openshift.xp.xml > > > In one test with XP image [1] I am experiencing problem of failing rediness probe. > {code} > sh-4.2$ python -d /opt/eap/bin/probes/runner.py --debug -c READY --loglevel=DEBUG probe.eap.dmr.EapProbe probe.eap.dmr.HealthCheckProbe > DEBUG:__main__:Starting probe runner with args: Namespace(check=[<Status.READY: 8>], debug=True, logfile=None, loglevel='DEBUG', probes=['probe.eap.dmr.EapProbe', 'probe.eap.dmr.HealthCheckProbe']) > INFO:__main__:Loading probe: probe.eap.dmr.EapProbe > DEBUG:probe.eap.dmr.EapProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=*** > INFO:__main__:Loading probe: probe.eap.dmr.HealthCheckProbe > DEBUG:probe.eap.dmr.HealthCheckProbe:Configuration set as follows: host=localhost, port=9990, user=eapadmin, password=*** > INFO:__main__:Probes will fail for the following states: [HARD_FAILURE, FAILURE, NOT_READY] > INFO:__main__:Running probes > INFO:__main__.ProbeRunner:Running the following probes: [probe.eap.dmr.EapProbe, probe.eap.dmr.HealthCheckProbe] > INFO:__main__.ProbeRunner:Running probe: probe.eap.dmr.EapProbe > INFO:probe.eap.dmr.EapProbe:Executing the following tests: [probe.eap.dmr.ServerStatusTest, probe.eap.dmr.BootErrorsTest, probe.eap.dmr.DeploymentTest] > INFO:probe.eap.dmr.EapProbe:Sending probe request to http://localhost:9990/management > DEBUG:probe.eap.dmr.EapProbe:Probe request = { > "operation": "composite", > "json.pretty": 1, > "steps": [ > { > "operation": "read-attribute", > "name": "server-state" > }, > { > "operation": "read-boot-errors", > "address": { > "core-service": "management" > } > }, > { > "operation": "read-attribute", > "name": "status", > "address": { > "deployment": "*" > } > } > ], > "address": [] > } > INFO:urllib3.connectionpool:Starting new HTTP connection (1): localhost > DEBUG:urllib3.connectionpool:"POST /management HTTP/1.1" 403 188 > DEBUG:probe.eap.dmr.EapProbe:Probe response: <Response [403]> > ERROR:probe.eap.dmr.EapProbe:Unexpected failure sending probe request > Traceback (most recent call last): > File "/s2i-output/server/bin/probes/probe/api.py", line 142, in execute > results = self.sendRequest(request) > File "/s2i-output/server/bin/probes/probe/dmr.py", line 97, in sendRequest > self.failUnusableResponse(response, request, url) > File "/s2i-output/server/bin/probes/probe/dmr.py", line 108, in failUnusableResponse > unusable = not respDict or not respDict["outcome"] or respDict["outcome"] != "failed" or not respDict["result"] > KeyError: 'result' > INFO:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned statuses [FAILURE] > DEBUG:__main__.ProbeRunner:Probe probe.eap.dmr.EapProbe returned messages "Error sending probe request: 'result'" > {code} > Note there is {{Response [403]}} which makes me think it will be related with legacy security switch with Elytron. > When I look at CD19 standalon-openshift.xml I see by default management interface is unsecured. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is secured by legacy security ManagementRealm pointing to mgmt-users.properties > In contrast in XP images it is secured by default by {{management-http-authentication}} which is pointing to {{mgmt-users.properties}}, which is empty by default. Once ADMIN_PASSWORD, ADMIN_USERNAME is applied it is filled with that user > {code} > <management-interfaces> > <http-interface http-authentication-factory="management-http-authentication" console-enabled="false"> > <http-upgrade enabled="true" sasl-authentication-factory="management-sasl-authentication"/> > <socket-binding http="management-http"/> > </http-interface> > </management-interfaces> > {code} > I think both approaches should be consistent (no matter if legacy or Elytron). E.g. unsecured by default and secured when ADMIN_PASSWORD, ADMIN_USERNAME specified (like in case of CD19) > [1] docker-registry.upshift.redhat.com/kwills/eap-xp1-openjdk8-openshift-rhel... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-314) [EAP7-1386] additional ConfigSources are always initialized

by Petr Kremensky (Jira)

[ https://issues.redhat.com/browse/WFWIP-314?page=com.atlassian.jira.plugin... ] Petr Kremensky closed WFWIP-314. -------------------------------- Resolution: Explained Thanks [~ron_sigal], I can see now that this is indeed an implementation specific behaviour, thus closing as explained. > [EAP7-1386] additional ConfigSources are always initialized > ----------------------------------------------------------- > > Key: WFWIP-314 > URL: https://issues.redhat.com/browse/WFWIP-314 > Project: WildFly WIP > Issue Type: Quality Risk > Reporter: Petr Kremensky > Assignee: Ronald Sigal > Priority: Minor > > I've noticed that three additional config sources provided by EAP7-1386 are always registered among config sources, even they are empty. I'll probably reject this one myself soon :) as I still have to look into the implementation of SPI for mp config, so I can assume that this is just out of box behaviour we have no control over. > Test with a simple servlet from [helloworld|https://github.com/wildfly/quickstart/tree/master/helloworld] quickstart with following addition: > {code:java} > ConfigProvider.getConfig().getConfigSources().forEach(configSource -> { > System.out.println("================================="); > System.out.println(configSource.getName()); > System.out.println(configSource.getOrdinal()); > System.out.println("Property names: " + configSource.getPropertyNames().stream().collect(Collectors.joining(", "))); > }); > {code} > output: > {noformat} > ================================= > SysPropConfigSource > 400 > [Standalone], awt.toolkit, ... > ================================= > EnvConfigSource > 300 > PATH, INVOCATION_ID, ... > ================================= > null:null:ServletConfigSource > 60 > ================================= > null:null:FilterConfigSource > 50 > ================================= > null:ServletContextConfigSource > 40 > {noformat} > Notice that {{PropertiesConfigSource}} is missing there as none was put to classpath. On the other hand {PropertiesConfigSource} is present once added to classpath, even it is empty. > {noformat} > ... > ================================= > PropertiesConfigSource[source=vfs:/content/helloworld.war/WEB-INF/classes/META-INF/microprofile-config.properties] > 100 > Property names: > ================================= > null:null:ServletConfigSource > 60 > Property names: > ================================= > null:null:FilterConfigSource > 50 > Property names: > ================================= > null:ServletContextConfigSource > 40 > Property names: > {noformat} > As stated before, I'd probably close this one myself once I'll take deeper look into it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5275) Descope Traits

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5275?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5275: --------------------------------- Sprint: 2020 Week 16-18 (from Apr 13) > Descope Traits > -------------- > > Key: DROOLS-5275 > URL: https://issues.redhat.com/browse/DROOLS-5275 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5275) Descope Traits

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5275?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5275: --------------------------------- Story Points: 8 > Descope Traits > -------------- > > Key: DROOLS-5275 > URL: https://issues.redhat.com/browse/DROOLS-5275 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 April 2020