March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-4) Automate Testcases

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-4?page=com.atlassian.jira.plug... ] Hayk Hovsepyan reassigned HAWKULARQE-4: --------------------------------------- Assignee: Hayk Hovsepyan (was: Prachi Yadav) > Automate Testcases > ------------------ > > Key: HAWKULARQE-4 > URL: https://issues.jboss.org/browse/HAWKULARQE-4 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Labels: hawkular-qe-automation > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-72) Polarion data cleanup

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-72?page=com.atlassian.jira.plu... ] Sunil kondkar commented on HAWKULARQE-72: ----------------------------------------- All work related to test cases is done. Worked on linking requirements to test cases marking them as 'verifies' the test case rather than 'relates' is done. ( This is causing missing data in most of the projects) Created a doc mentioning some guidelines. http://pad.engineering.redhat.com/PolarionGuidelines The following report does not show any missing data. https://polarion.engineering.redhat.com/polarion/#/project/pylarion/wiki/... While going through EAP project reports, observed that there are release plans created in Polarion and requirements are marked as 'planned in' which is not in our case. ( These plans are different from test plans) Created few release plans like: Parent: MM-CFME58 Child plans: MM-CFME58-DR1, MM-CFME58-DR2 and MM-CFME58-DR3 link: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/plans Now the remaining task is: Research and link requirements/test cases to the respective plans in Polarion so as to enble reports viewing according to Polarion plans. > Polarion data cleanup > --------------------- > > Key: HAWKULARQE-72 > URL: https://issues.jboss.org/browse/HAWKULARQE-72 > Project: Hawkular QE > Issue Type: Task > Reporter: Sunil kondkar > Assignee: Sunil kondkar > > Task to able to have polarion reports in place. > Reports: > 1) PQI Metrics: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... > 2) Standard Reports: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... > 3) Test Run Status by Plan > 4) Test Run Status by Plan and chosen fields > Tasks: > 1) Find and remove duplicates > 2) Each test case has correct fields > * Description > * Level > * Test type and sub type > * Automated or Manual > * Importance (Severity) > 3) Do we need to create a plan in below link? (Like EAP team has release plans created that are used in reports ' Test Run Status by Plan' and 'Test Run Status by Plan and chosen fields' ) > Link: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/plans > 4) Check if manual test cases are with approved status( Approve if needed) > 5) All automated tests (CF-UI test and CFME tests) - need to be changed to Approved from 'Draft' status. > (Need to check if we can have the polarion export job marking it Approved while executed going forward?) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-7456) Inconsistent description for custom mail server between :read-resource-description on parent and the custom server itself

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7456?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-7456. ----------------------------- Resolution: Rejected > Inconsistent description for custom mail server between :read-resource-description on parent and the custom server itself > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7456 > URL: https://issues.jboss.org/browse/WFLY-7456 > Project: WildFly > Issue Type: Bug > Components: Mail > Affects Versions: 10.1.0.Final > Reporter: Radim Hatlapatka > Assignee: Tomaz Cerar > Priority: Optional > Labels: user_experience > > There is inconsistent description for custom server when reading it as child description => {{/subsystem=mail/mail-session=default:read-resource-description}}, where it is {{Custom mail server configuration}} and when reading its description directly => {{/subsystem=mail/mail-session=default/custom=xxx:read-resource-description}}, where it is {{Mail session server}} > This doesn't look nice from UX PoV, where I believe these values should be the same. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8478) Setting elytron ssl-context on undertow without reload

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8478?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-8478. ----------------------------- Resolution: Rejected You need to pass {allow-resource-service-restart=true} header to operation if you want to have runtime change without reload > Setting elytron ssl-context on undertow without reload > ------------------------------------------------------ > > Key: WFLY-8478 > URL: https://issues.jboss.org/browse/WFLY-8478 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Reporter: Martin Choma > Assignee: Tomaz Cerar > Labels: user_experience > > Please, allow setting of elytron ssl-context on undertow without reload. > {code} > [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/https-listener=https:write-attribute(name=ssl-context,value=server) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8478) Setting elytron ssl-context on undertow without reload

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8478?page=com.atlassian.jira.plugin.... ] Tomaz Cerar moved WFCORE-2448 to WFLY-8478: ------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-8478 (was: WFCORE-2448) Component/s: Security Web (Undertow) (was: Security) Affects Version/s: (was: 3.0.0.Beta7) > Setting elytron ssl-context on undertow without reload > ------------------------------------------------------ > > Key: WFLY-8478 > URL: https://issues.jboss.org/browse/WFLY-8478 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Reporter: Martin Choma > Assignee: Tomaz Cerar > Labels: user_experience > > Please, allow setting of elytron ssl-context on undertow without reload. > {code} > [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/https-listener=https:write-attribute(name=ssl-context,value=server) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8477) Introduce capabilites in undertow subsystem

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8477: --------------------------------- Summary: Introduce capabilites in undertow subsystem Key: WFLY-8477 URL: https://issues.jboss.org/browse/WFLY-8477 Project: WildFly Issue Type: Enhancement Reporter: Tomaz Cerar Assignee: Tomaz Cerar Majority of undertow subsystem should move to capabilites. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8476) Upgrade Artemis 1.5.3.jbossorg-004

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-8476?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-10031 to WFLY-8476: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8476 (was: JBEAP-10031) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: ActiveMQ) (was: JMS) > Upgrade Artemis 1.5.3.jbossorg-004 > ---------------------------------- > > Key: WFLY-8476 > URL: https://issues.jboss.org/browse/WFLY-8476 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1341) Account for additional DB2 FATAL connection errors

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1341?page=com.atlassian.jira.plugin... ] Stefano Maestri commented on JBJCA-1341: ---------------------------------------- [~jolee] yup it's what I've written. Maybe is not so easy to read because I've written all option on the same line just separating them by a column. Editing to make it more readable > Account for additional DB2 FATAL connection errors > -------------------------------------------------- > > Key: JBJCA-1341 > URL: https://issues.jboss.org/browse/JBJCA-1341 > Project: IronJacamar > Issue Type: Enhancement > Components: Validator > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 0 minutes > > Various version of pre 11.x DB2 drivers utilize the -99999 error code for a SQLException. Not all -99999 errors are fatal. For those variations that are known to be fatal, a check should be added to treat as such. > One example would be the -99999 error that indicates "Connection is closed" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2181) Server doesn't start on Windows when started from path that contains space

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2181?page=com.atlassian.jira.plugi... ] Tomaz Cerar reopened WFCORE-2181: --------------------------------- > Server doesn't start on Windows when started from path that contains space > -------------------------------------------------------------------------- > > Key: WFCORE-2181 > URL: https://issues.jboss.org/browse/WFCORE-2181 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Blocker > Fix For: 3.0.0.Alpha18 > > > If one installs his EAP(on Windows) to the location that has a space in the path(...\Program Files\...) is then unable to start it. > This is regression against EAP 7.0.0 and 7.1.0.DR7. > This issue could be caused by JBEAP-6182 ([https://github.com/wildfly/wildfly-core/pull/1886/files]) > Following error is printed > {noformat} > Error: Could not find or load main class Files\ModCluster_Workspace\jboss-eap-7.1\standalone\log\gc.log > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-1) [QE] - JMAN4-111 - Immutability of JBoss Middleware services running in containers

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-1?page=com.atlassian.jira.plug... ] Hayk Hovsepyan commented on HAWKULARQE-1: ----------------------------------------- Taking this task on me to be done. > [QE] - JMAN4-111 - Immutability of JBoss Middleware services running in containers > ---------------------------------------------------------------------------------- > > Key: HAWKULARQE-1 > URL: https://issues.jboss.org/browse/HAWKULARQE-1 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Labels: mm-integration-hawkular-qe > > See [JMAN4-111|https://issues.jboss.org/browse/JMAN4-111] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 March 2017