May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-228) DNS Problems on B13

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-228?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-228. --------------------------------- Resolution: Done This issue will be resolved by https://issues.jboss.org/browse/SWSQE-252 > DNS Problems on B13 > ------------------- > > Key: SWSQE-228 > URL: https://issues.jboss.org/browse/SWSQE-228 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > > When a pod is deployed on B13, sometimes the app is not being routed well. > Some causes of failures are: > - DNS Probe Domain -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-228) DNS Problems on B13

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-228?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-228: ------------------------------------- Problem is visible on other nodes from b12 cluster too. Only b11 node is working fine. Routes to other nodes are not working. I noticed following error in logs on affected nodes: May 24 06:15:05 b13 atomic-openshift-node: I0524 06:15:05.039059 12296 logs.go:41] http: TLS handshake error from 10.16.23.23:52338: remote error: tls: bad certificate This error is not visible on b11 node. I created https://issues.jboss.org/browse/SWSQE-252 to re-install b12 cluster from scratch which seems to be faster solution then fixing the certificate issue. > DNS Problems on B13 > ------------------- > > Key: SWSQE-228 > URL: https://issues.jboss.org/browse/SWSQE-228 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > > When a pod is deployed on B13, sometimes the app is not being routed well. > Some causes of failures are: > - DNS Probe Domain -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-252) Reinstall b12 cluster

by Filip Brychta (JIRA)

Filip Brychta created SWSQE-252: ----------------------------------- Summary: Reinstall b12 cluster Key: SWSQE-252 URL: https://issues.jboss.org/browse/SWSQE-252 Project: Kiali QE Issue Type: Task Reporter: Filip Brychta Assignee: Michael Foley There is an issue reported on b12 cluster - https://issues.jboss.org/browse/SWSQE-228 The fastest/cleanest solution seems to be clean installation of b12 cluster. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8364) mod_cluster allows both simple- and dynamic-load-providers to be defined in the model simultaneously

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8364?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8364: --------------------------------- Issue Type: Bug (was: Task) > mod_cluster allows both simple- and dynamic-load-providers to be defined in the model simultaneously > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-8364 > URL: https://issues.jboss.org/browse/WFLY-8364 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > {code} > <subsystem xmlns="urn:jboss:domain:modcluster:3.0"> > <mod-cluster-config advertise-socket="modcluster" connector="ajp"> > <simple-load-provider factor="5"/> > <dynamic-load-provider> > <load-metric type="cpu"/> > </dynamic-load-provider> > </mod-cluster-config> > </subsystem> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8364) mod_cluster model allows both simple- and dynamic-load-providers to be defined in the model simultaneously

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8364?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8364: --------------------------------- Summary: mod_cluster model allows both simple- and dynamic-load-providers to be defined in the model simultaneously (was: mod_cluster allows both simple- and dynamic-load-providers to be defined in the model simultaneously) > mod_cluster model allows both simple- and dynamic-load-providers to be defined in the model simultaneously > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-8364 > URL: https://issues.jboss.org/browse/WFLY-8364 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > {code} > <subsystem xmlns="urn:jboss:domain:modcluster:3.0"> > <mod-cluster-config advertise-socket="modcluster" connector="ajp"> > <simple-load-provider factor="5"/> > <dynamic-load-provider> > <load-metric type="cpu"/> > </dynamic-load-provider> > </mod-cluster-config> > </subsystem> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10442) mod_cluster proxy operations' rollback handlers make potentially dangerous assumptions

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10442?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10442: ---------------------------------- Summary: mod_cluster proxy operations' rollback handlers make potentially dangerous assumptions (was: mod_cluster proxy operations' rollback handlers make potentially dangerous asumptions) > mod_cluster proxy operations' rollback handlers make potentially dangerous assumptions > -------------------------------------------------------------------------------------- > > Key: WFLY-10442 > URL: https://issues.jboss.org/browse/WFLY-10442 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 13.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > The current implementation of certain mod_cluster proxy operations are registering potentially dangerous rollback handlers. They are making an assumption what was the state of the system prior to the operation. > For instance, if the proxy was already disabled, and a disable operation is called which intermittently fails, a callback handler will be called which will enable the proxy. This is dangerous as attempting to disable an already disabled proxy may potentially enable it. > This behavior should be removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10442) mod_cluster proxy operations' rollback handlers make potentially dangerous assumptions

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10442?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10442: ---------------------------------- Affects Version/s: 13.0.0.Beta1 > mod_cluster proxy operations' rollback handlers make potentially dangerous assumptions > -------------------------------------------------------------------------------------- > > Key: WFLY-10442 > URL: https://issues.jboss.org/browse/WFLY-10442 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 13.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > The current implementation of certain mod_cluster proxy operations are registering potentially dangerous rollback handlers. They are making an assumption what was the state of the system prior to the operation. > For instance, if the proxy was already disabled, and a disable operation is called which intermittently fails, a callback handler will be called which will enable the proxy. This is dangerous as attempting to disable an already disabled proxy may potentially enable it. > This behavior should be removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-228) DNS Problems on B13

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-228?page=com.atlassian.jira.plugin.... ] Filip Brychta reassigned SWSQE-228: ----------------------------------- Assignee: Filip Brychta > DNS Problems on B13 > ------------------- > > Key: SWSQE-228 > URL: https://issues.jboss.org/browse/SWSQE-228 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > > When a pod is deployed on B13, sometimes the app is not being routed well. > Some causes of failures are: > - DNS Probe Domain -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10442) mod_cluster proxy operations' rollback handlers make potentially dangerous asumptions

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-10442: ------------------------------------- Summary: mod_cluster proxy operations' rollback handlers make potentially dangerous asumptions Key: WFLY-10442 URL: https://issues.jboss.org/browse/WFLY-10442 Project: WildFly Issue Type: Bug Components: mod_cluster Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Critical The current implementation of certain mod_cluster proxy operations are registering potentially dangerous rollback handlers. They are making an assumption what was the state of the system prior to the operation. For instance, if the proxy was already disabled, and a disable operation is called which intermittently fails, a callback handler will be called which will enable the proxy. This is dangerous as attempting to disable an already disabled proxy may potentially enable it. This behavior should be removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10441) mod_cluster proxy operations are incorrectly registered at the subsystem level

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10441?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10441: ---------------------------------- Description: mod_cluster proxy operations are incorrectly registered at the subsystem level, {{/subsystem=modcluster}}. These operations are pertaining to a specific mod_cluster configuration, so they should have been registered at the {{/subsystem=modcluster/mod-cluster-config=CONFIGURATION}} level. These need to be deprecated and registered at the correct location. was: mod_cluster proxy operations are incorrectly registered at the subsystem level, {{/subsystem=modcluster}}. These operations are pertaining to a specific mod_cluster configuration, so they should have been registered at the {{/subsystem=modcluster/mod-cluster-config=CONFIGURATION}} level. These need to be deprecated and moved. > mod_cluster proxy operations are incorrectly registered at the subsystem level > ------------------------------------------------------------------------------ > > Key: WFLY-10441 > URL: https://issues.jboss.org/browse/WFLY-10441 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > mod_cluster proxy operations are incorrectly registered at the subsystem level, {{/subsystem=modcluster}}. These operations are pertaining to a specific mod_cluster configuration, so they should have been registered at the {{/subsystem=modcluster/mod-cluster-config=CONFIGURATION}} level. > These need to be deprecated and registered at the correct location. -- 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 May 2018