March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-83) Resolve EDD and acpi issues in b07, b22, b06, b04?

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-83?page=com.atlassian.jira.plugin.s... ] Filip Brychta commented on SWSQE-83: ------------------------------------ installed b04 with acpi=off, did not find a way how to make it work with acpi enabled. Added it back to rhev userspace cluster > Resolve EDD and acpi issues in b07,b22,b06,b04? > ----------------------------------------------- > > Key: SWSQE-83 > URL: https://issues.jboss.org/browse/SWSQE-83 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > > Some blades do not boot up because of EDD issue. It is stuck during booting on Probing EDD (edd=off to disable), I tried to add that kernel option but it did not help. > Another issue is that blade can't boot with acpi enabled, there is aleady sys-ops ticket for this but it did not help for b04 - https://redhat.service-now.com/pnt?id=ticket&table=x_redha_pnt_devops_tab... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-83) Resolve EDD and acpi issues in b07, b22, b06, b04?

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-83?page=com.atlassian.jira.plugin.s... ] Filip Brychta updated SWSQE-83: ------------------------------- Summary: Resolve EDD and acpi issues in b07,b22,b06,b04? (was: Resolve EDD bug in b07,b22,b06,b04?) > Resolve EDD and acpi issues in b07,b22,b06,b04? > ----------------------------------------------- > > Key: SWSQE-83 > URL: https://issues.jboss.org/browse/SWSQE-83 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > > Some blades do not boot up because of EDD issue. It is stuck during booting on Probing EDD (edd=off to disable), I tried to add that kernel option but it did not help. > Another issue is that blade can't boot with acpi enabled, there is aleady sys-ops ticket for this but it did not help for b04 - https://redhat.service-now.com/pnt?id=ticket&table=x_redha_pnt_devops_tab... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-83) Resolve EDD bug in b07, b22, b06, b04?

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-83?page=com.atlassian.jira.plugin.s... ] Filip Brychta updated SWSQE-83: ------------------------------- Description: Some blades do not boot up because of EDD issue. It is stuck during booting on Probing EDD (edd=off to disable), I tried to add that kernel option but it did not help. Another issue is that blade can't boot with acpi enabled, there is aleady sys-ops ticket for this but it did not help for b04 - https://redhat.service-now.com/pnt?id=ticket&table=x_redha_pnt_devops_tab... was: Some blades do not boot up because of EDD issue. It is stuck during booting on Probing EDD (edd=off to disable), I tried to add that kernel option but it did not help. There is aleady sys-ops ticket for this but it did not help - https://redhat.service-now.com/pnt?id=ticket&table=x_redha_pnt_devops_tab... > Resolve EDD bug in b07,b22,b06,b04? > ----------------------------------- > > Key: SWSQE-83 > URL: https://issues.jboss.org/browse/SWSQE-83 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > > Some blades do not boot up because of EDD issue. It is stuck during booting on Probing EDD (edd=off to disable), I tried to add that kernel option but it did not help. > Another issue is that blade can't boot with acpi enabled, there is aleady sys-ops ticket for this but it did not help for b04 - https://redhat.service-now.com/pnt?id=ticket&table=x_redha_pnt_devops_tab... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3712) Provided mechanism to disable configuration file backup

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3712?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3712: ------------------------------------------ Analysis of this needs to account for all scenarios. For example, in the read-only-server-config=standalone.xml use case, it's the history that allows reload to work. Use case is that the config is golden but not modifiable, but if they use the CLI to affect some runtime behavior and have to reload to get that to work, the reload draws from history. IOW user is willing to temporarily shift a server off the golden image. A possible behavior in that case is just to log something (INFO or WARN) in case of reload, and the server reloads back to the original config. > Provided mechanism to disable configuration file backup > ------------------------------------------------------- > > Key: WFCORE-3712 > URL: https://issues.jboss.org/browse/WFCORE-3712 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Ken Wills > > For certain use cases, e.g. cloud with non-writable storage, the automatic persistence backup of configuration files (standalone.xml etc) is not needed or desired. > It would be nice to have a mechanism to disable this. > Example: > {quote} > 17:42:13,104 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: java.lang.IllegalStateException: WFLYCTL0056: Could not rename /opt/datagrid/standalone/configuration/standalone_xml_history/current to /opt/datagrid/standalone/configuration/standalone_xml_history/20180326-174213103 > at org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDirectory(ConfigurationFile.java:638) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] > at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:470) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] > at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] > at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:451) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] > at org.jboss.as.server.ServerService.boot(ServerService.java:373) [wildfly-server-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:301) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_161] > 17:42:13,106 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3712) Provided mechanism to disable configuration file backup

by Ken Wills (JIRA)

Ken Wills created WFCORE-3712: --------------------------------- Summary: Provided mechanism to disable configuration file backup Key: WFCORE-3712 URL: https://issues.jboss.org/browse/WFCORE-3712 Project: WildFly Core Issue Type: Enhancement Reporter: Ken Wills For certain use cases, e.g. cloud with non-writable storage, the automatic persistence backup of configuration files (standalone.xml etc) is not needed or desired. It would be nice to have a mechanism to disable this. Example: {quote} 17:42:13,104 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: java.lang.IllegalStateException: WFLYCTL0056: Could not rename /opt/datagrid/standalone/configuration/standalone_xml_history/current to /opt/datagrid/standalone/configuration/standalone_xml_history/20180326-174213103 at org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDirectory(ConfigurationFile.java:638) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(ConfigurationFile.java:470) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.successfulBoot(BackupXmlConfigurationPersister.java:94) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] at org.jboss.as.controller.AbstractControllerService.finishBoot(AbstractControllerService.java:451) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] at org.jboss.as.server.ServerService.boot(ServerService.java:373) [wildfly-server-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:301) [wildfly-controller-2.1.18.Final-redhat-1.jar:2.1.18.Final-redhat-1] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_161] 17:42:13,106 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2001) Can't enter time of day portion of Date object belonging to a fact in test Scenarios

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2001?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2001: --------------------------------------- This will be addressed by the new scenario simulation and testing tool. No point in fixing in the existing testing tool. > Can't enter time of day portion of Date object belonging to a fact in test Scenarios > ------------------------------------------------------------------------------------- > > Key: DROOLS-2001 > URL: https://issues.jboss.org/browse/DROOLS-2001 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Environment: Running on Windows 7 with BRMS Standalone 5.1. Issue arises in both firefox and google chrome browsers. > Reporter: Jeff Forte > Assignee: Guilherme Carreiro > > I have a set of facts that hold a Date asset for comparison between each other. The comparison is supposed to be between the time of day of the object; however, when trying to enter the date and time of day into the test scenario the time of day portion always gets wiped upon running the scenario. The date stays but there is no long any time of day and I can't seem to find a way to enter the time even with the "enter date" button. I can't test while this is happening. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2000) Test Scenario: Not possible to use a global

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2000?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-2000: ---------------------------------- Fix Version/s: (was: 7.7.0.Final) > Test Scenario: Not possible to use a global > ------------------------------------------- > > Key: DROOLS-2000 > URL: https://issues.jboss.org/browse/DROOLS-2000 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 7.7.0.Final > Reporter: Toni Rikkola > Assignee: Guilherme Carreiro > Priority: Blocker > > Tried with two globals. One added into a DRL file and another added with menu New->Global Variable(s). > Neither of these two show up in the Test Scenario popup. Tried a full build, reopening the test scenario and even restarting the workbench. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2000) Test Scenario: Not possible to use a global

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2000?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2000: --------------------------------------- This will be addressed by the new scenario simulation and testing tool. No point in fixing in the existing testing tool. > Test Scenario: Not possible to use a global > ------------------------------------------- > > Key: DROOLS-2000 > URL: https://issues.jboss.org/browse/DROOLS-2000 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 7.7.0.Final > Reporter: Toni Rikkola > Assignee: Guilherme Carreiro > Priority: Blocker > > Tried with two globals. One added into a DRL file and another added with menu New->Global Variable(s). > Neither of these two show up in the Test Scenario popup. Tried a full build, reopening the test scenario and even restarting the workbench. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2001) Can't enter time of day portion of Date object belonging to a fact in test Scenarios

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2001?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-2001: ---------------------------------- Fix Version/s: (was: 7.7.0.Final) > Can't enter time of day portion of Date object belonging to a fact in test Scenarios > ------------------------------------------------------------------------------------- > > Key: DROOLS-2001 > URL: https://issues.jboss.org/browse/DROOLS-2001 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Environment: Running on Windows 7 with BRMS Standalone 5.1. Issue arises in both firefox and google chrome browsers. > Reporter: Jeff Forte > Assignee: Guilherme Carreiro > > I have a set of facts that hold a Date asset for comparison between each other. The comparison is supposed to be between the time of day of the object; however, when trying to enter the date and time of day into the test scenario the time of day portion always gets wiped upon running the scenario. The date stays but there is no long any time of day and I can't seem to find a way to enter the time even with the "enter date" button. I can't test while this is happening. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10108) Upgrade to CXF 3.2.4

by Peter Palaga (JIRA)

Peter Palaga created WFLY-10108: ----------------------------------- Summary: Upgrade to CXF 3.2.4 Key: WFLY-10108 URL: https://issues.jboss.org/browse/WFLY-10108 Project: WildFly Issue Type: Component Upgrade Reporter: Peter Palaga Assignee: Peter Palaga An upgrade to CXF 3.2.4 is required by WildFly Camel, see https://github.com/wildfly-extras/wildfly-camel/issues/2460 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 2018