May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4474) Missing path validation of a log file while update path

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4474?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-4474: --------------------------------------- I don't think there is much we can really do here TBH. There is a [{{FileCorrect}}|https://github.com/wildfly/wildfly-core/blob/5a12c1bad47db0bfbf836b279d262bdf352d16c7/logging/src/main/java/org/jboss/as/logging/correctors/FileCorrector.java#L33-L44] that sets the {{relative-to}} attribute if it was previously set and the {{path}} was deemed *not* to be an absolute path. It's been like that for a long time so I don't think we can really change that behavior at this point. For some of the failures you'd need to quote the path in the operation so CLI can parse it. For example the {{C:*server.log}} in CLI should be {code} /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path="C:*server.log"}) {code} That would result in the {{relative-to}} being set though so you'd end up with a path like : {{C:\servers\wildfly\standalone\logs\C:*server.log}} > Missing path validation of a log file while update path > -------------------------------------------------------- > > Key: WFCORE-4474 > URL: https://issues.jboss.org/browse/WFCORE-4474 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Affects Versions: 9.0.0.Beta4 > Reporter: Vratislav Marek > Assignee: James Perkins > Priority: Major > > After the first successful set of a valid path, you can set an invalid path. > It is can be relative to that while "relative-to" parameter is overridden, the validator doesn't validate it. > Discovered on Windows. > A code block is divided, but it is holding sequence to reproduce. > _This works as expected._ > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.nio.file.InvalidPathException: Illegal char < > :> at index 61: D:\\Tests\\clear\\wildfly-17.0.0.Beta1-SNAPSHOT\\standalone\\log\\C:/server.log", > "rolled-back" => true > } > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\server.log}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.nio.file.InvalidPathException: Illegal char < > :> at index 61: D:\\Tests\\clear\\wildfly-17.0.0.Beta1-SNAPSHOT\\standalone\\log\\C:server.log", > "rolled-back" => true > } > {code} > _Still works as expected. But After this successful write-attribute command, it that changing._ > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\\server.log}) > {"outcome" => "success"} > {code} > *Now there is a problem, it that not works as expected. The validator accepts invalid path.* > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:server.log}) > {"outcome" => "success"} > {code} > _But not accept all invalid paths._ > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:*server.log}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.nio.file.InvalidPathException: Illegal char < > *> at index 2: C:*server.log", > "rolled-back" => true > } > {code} > _Verification if the unsuccessful update changes something. But not._ > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\\server.log}) > {"outcome" => "success"} > {code} > _Verification if is really set in the property value. Yes_ > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file) > { > "outcome" => "success", > "result" => {"path" => "C:\\server.log"} > } > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file) > { > "outcome" => "success", > "result" => {"path" => "C:server.log"} > } > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file) > { > "outcome" => "success", > "result" => {"path" => "C:/server.log"} > } > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file) > { > "outcome" => "success", > "result" => {"path" => "C:server.log"} > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-626) Investigate options to share docker registry with istio team

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-626?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-626: ---------------------------------- Sprint: Kiali Sprint #23 (was: Kiali Sprint #22) > Investigate options to share docker registry with istio team > ------------------------------------------------------------ > > Key: SWSQE-626 > URL: https://issues.jboss.org/browse/SWSQE-626 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > Tiago runs his docker registry in Central CI > We run our registry in b22 ocp cluster. > Do we want to run just one registry? > What would be content: > * product images > * jenkins slaves images > * ?? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-712) Ability to create 2nd bookinfo via operator

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-712?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-712: ---------------------------------- Sprint: Kiali Sprint #23 (was: Kiali Sprint #22) > Ability to create 2nd bookinfo via operator > ------------------------------------------- > > Key: SWSQE-712 > URL: https://issues.jboss.org/browse/SWSQE-712 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: infrastructure > > Currently our https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/bookinfo-operator/ > jenkins job allows to create only one bookinfo namespace. > But UI Automation framework requires bookinfo2 namespace for parallel running. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-729) publish_jenkins_console.py failing to push Jenkins console logs

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-729?page=com.atlassian.jira.plugin.... ] Matthew Mahoney closed SWSQE-729. --------------------------------- Resolution: Done No longer an issue > publish_jenkins_console.py failing to push Jenkins console logs > --------------------------------------------------------------- > > Key: SWSQE-729 > URL: https://issues.jboss.org/browse/SWSQE-729 > Project: Kiali QE > Issue Type: Bug > Reporter: Matthew Mahoney > Assignee: Hayk Hovsepyan > Priority: Major > Labels: infrastructure > > All kiali-core-pr-e2e-test jobs show the following error, which is resulting in an error on all kiali PR's: > Jenkins CI: kiali-core-pr-e2e-test [#1016](https://paste.fedoraproject.org/paste/oCuXUwipkTMlLuqVdypgEA) > :red_circle: PRT Failed, Please Contact QE -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-560) OCP 4.0 on Openstack

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-560?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-560: ---------------------------------- Sprint: Kiali Sprint #23 (was: Kiali Sprint #22) > OCP 4.0 on Openstack > -------------------- > > Key: SWSQE-560 > URL: https://issues.jboss.org/browse/SWSQE-560 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > New Openshift Installer supports OpenStack (https://github.com/openshift/installer/blob/master/docs/user/openstack/RE...) > It can be a substitute for OSOOS. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-704) Review jenkins2 settings

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-704?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-704: ---------------------------------- Sprint: Kiali Sprint #23 (was: Kiali Sprint #22) > Review jenkins2 settings > ------------------------ > > Key: SWSQE-704 > URL: https://issues.jboss.org/browse/SWSQE-704 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Check https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/configure for kubernetes settings and usage of b21.jonqe.lab.eng.bos.redhat.com which is now part of prod cluster. > Also update https://mojo.redhat.com/docs/DOC-1168333 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-734) Upload Jaeger Auatomation Runs Into Polarion

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-734?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-734: ---------------------------------- Sprint: Kiali Sprint #23 (was: Kiali Sprint #22) > Upload Jaeger Auatomation Runs Into Polarion > -------------------------------------------- > > Key: SWSQE-734 > URL: https://issues.jboss.org/browse/SWSQE-734 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: pqi > > Using the polarion_uploader, upload Jaeger automation runs into Polarion for TP-11 release. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-723) Be ready for Day2 testing

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-723?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-723: ---------------------------------- Sprint: Kiali Sprint #23 (was: Kiali Sprint #22) > Be ready for Day2 testing > ------------------------- > > Key: SWSQE-723 > URL: https://issues.jboss.org/browse/SWSQE-723 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: infrastructure > > When Service Mesh GA will be happen, > there is always a risk to have a Day2 testing of customer scenarios which failed on GA. > Action Item: > Have booked a baremetal servers (bladecenter, PSI, beaker... whatever) with OCP 4.1 installed. > So when an issue happens on customer side, we can rapidly reproduce that and cooperate with dev on fixing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-713) There is too many jenkins slaves

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-713?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-713: ---------------------------------- Sprint: Kiali Sprint #23 (was: Kiali Sprint #22) > There is too many jenkins slaves > -------------------------------- > > Key: SWSQE-713 > URL: https://issues.jboss.org/browse/SWSQE-713 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > There are multiple jenkins slaves started for one jenkins job. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-695) Map Jira Workflows To Tablue Graphs

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-695?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-695: ---------------------------------- Sprint: Kiali Sprint #23 (was: Kiali Sprint #22) > Map Jira Workflows To Tablue Graphs > ----------------------------------- > > Key: SWSQE-695 > URL: https://issues.jboss.org/browse/SWSQE-695 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Prachi Yadav > Priority: Major > Labels: pqi > > Two parts to this task: > 1) Because only a couple team members have access to Tablue, generate Kiali metric graphs in Tablue and Paste them into a team accessablel doc so that we can analyze these metrics > 2) Map Jira Workflow queries to Tablue graphs, so that we can better understand how each of the Tablue graphs are generated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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

jboss-jira May 2019