November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-266) no way how to force scale down

by Martin Svehla (Jira)

Martin Svehla created WFWIP-266: ----------------------------------- Summary: no way how to force scale down Key: WFWIP-266 URL: https://issues.jboss.org/browse/WFWIP-266 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Svehla Assignee: Ondrej Chaloupka inspired by upstream issue https://github.com/wildfly/wildfly-operator/issues/100. I take part of description from it {quote} When transaction scale down process reviews the state of transactions in the pods it checks if there are no unfinished prepared transactions. If there are found some then it does not permit the pod being terminated and the pod is moved to state SCALING_DOWN_RECOVERY_DIRTY. It's left there until all transactions are safely recovered. There are cases when transaction is never recovered in automated manner. It's time when transaction is in heuristic state. Such transaction needs to be handled manually by administrator and he is expected to connect to the app server with jboss-cli.sh and verify the transaction state. {quote} There is no way how to ignore status of tx processing (tx in this case, I guess there will be more cases in future) and force scale down. Users might want it during development, where data integrity doesn't matter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-265) Operator missing shared storage between containers or pods

by Martin Svehla (Jira)

Martin Svehla created WFWIP-265: ----------------------------------- Summary: Operator missing shared storage between containers or pods Key: WFWIP-265 URL: https://issues.jboss.org/browse/WFWIP-265 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Svehla Assignee: Jeff Mesnil Operator is missing way of configuring volumes such - it can be shared between containers in one pod (emptyDir) - it can be shared between pods (Persistent Volume Claim) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4677) [DMN Designer] Data Types - Handle read-only Data Types in the drag and drop list

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4677?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4677: -------------------------------------- Labels: UXTeam drools-tools ux (was: drools-tools ux) > [DMN Designer] Data Types - Handle read-only Data Types in the drag and drop list > --------------------------------------------------------------------------------- > > Key: DROOLS-4677 > URL: https://issues.jboss.org/browse/DROOLS-4677 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.29.0.Final > Reporter: Guilherme Gomes > Assignee: Elizabeth Clayton > Priority: Major > Labels: UXTeam, drools-tools, ux > > The new drag and drop mechanism, added by the [Data Type UI enhancements|https://docs.google.com/presentation/u/1/d/10GZUd6oLaQohK27i...] does not specify how to handle read-only data types. > Scenarios: > - A User drags a regular data type to a position inside of read-only data type > - A User drags a read-only data type to a position inside of regular data type > _Notice: Read only data types appear when a DMN model has another DMN model included, and the external one has some data types._ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-264) Operator missing way to configure multiple containers inside pod

by Martin Svehla (Jira)

Martin Svehla created WFWIP-264: ----------------------------------- Summary: Operator missing way to configure multiple containers inside pod Key: WFWIP-264 URL: https://issues.jboss.org/browse/WFWIP-264 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Svehla Assignee: Jeff Mesnil User scenario: As a user I am able to run multiple containers under pod - init container pattern [1] - side car container pattern [1] Note, this is pattern which {{istio}} use. [1] https://matthewpalmer.net/kubernetes-app-developer/articles/multi-contain... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-263) Operator is missing pod network settings

by Martin Svehla (Jira)

Martin Svehla created WFWIP-263: ----------------------------------- Summary: Operator is missing pod network settings Key: WFWIP-263 URL: https://issues.jboss.org/browse/WFWIP-263 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Svehla Assignee: Jeff Mesnil As a user I am able to tweak network configuration {code:yaml} dnsPolicy: hostAliases: hostIPC: hostNetwork: hostPID: hostname: subdomain: {code} [1] https://docs.openshift.com/container-platform/3.11/rest_api/apis-apps/v1b... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-262) Operator is missing node/pod affinity setting

by Martin Svehla (Jira)

Martin Svehla created WFWIP-262: ----------------------------------- Summary: Operator is missing node/pod affinity setting Key: WFWIP-262 URL: https://issues.jboss.org/browse/WFWIP-262 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Svehla Assignee: Jeff Mesnil As a user I am able to configure pod/node affinity {code:yaml} affinity: nodeAffinity: preferredDuringSchedulingIgnoredDuringExecution: requiredDuringSchedulingIgnoredDuringExecution: podAffinity: preferredDuringSchedulingIgnoredDuringExecution: requiredDuringSchedulingIgnoredDuringExecution: podAntiAffinity: preferredDuringSchedulingIgnoredDuringExecution: requiredDuringSchedulingIgnoredDuringExecution: nodeName: nodeSelector: schedulerName tolerations" {code} [1] https://docs.openshift.com/container-platform/3.11/rest_api/apis-apps/v1b... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-261) Operator does not provide way to configure https

by Martin Svehla (Jira)

Martin Svehla created WFWIP-261: ----------------------------------- Summary: Operator does not provide way to configure https Key: WFWIP-261 URL: https://issues.jboss.org/browse/WFWIP-261 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Svehla Assignee: Jeff Mesnil Operator is missing way of configuring - https port, e.g. 8443 - termination policy (passthrough, edge, reencrypt) - way to specify certificates -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12791) CXF-8118 - CXF LoggingInInterceptor, CachedWriter leaks

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFLY-12791?page=com.atlassian.jira.plugin... ] Ilia Vassilev commented on WFLY-12791: -------------------------------------- Resolved in CXF 3.3.4 > CXF-8118 - CXF LoggingInInterceptor, CachedWriter leaks > ------------------------------------------------------- > > Key: WFLY-12791 > URL: https://issues.jboss.org/browse/WFLY-12791 > Project: WildFly > Issue Type: Bug > Components: Web Services > Environment: Fuse 7.3.1 on EAP 7.2.0 > CXF 3.2.5.redhat-00001 > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Critical > Labels: downstream_dependency > > The LoggingInInterceptor use an instance of CachedWriter but never close it causing a leak in the static list CachedWriter.streamList. > I know that LoggingInInterceptor has been deprecated but it still available in CXF. > https://issues.apache.org/jira/browse/CXF-8118 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-260) Eap operator is missing on redhat-operators-stage/redhat-operators-art on quay.io

by Martin Svehla (Jira)

Martin Svehla created WFWIP-260: ----------------------------------- Summary: Eap operator is missing on redhat-operators-stage/redhat-operators-art on quay.io Key: WFWIP-260 URL: https://issues.jboss.org/browse/WFWIP-260 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Svehla Assignee: Jeff Mesnil According to https://docs.google.com/document/d/12BPNG4I3TCh-hBWLXeiIUQ5e4CmnwJijJEkSX... this is place where it can be tested manually from stage OperatorHub. We do not expect changes in codebase, rather this is more productization blocker. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12790) CXF-8105 - introduce a property for JMS transport client to decide reset JMS connection or not when client timeout

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFLY-12790?page=com.atlassian.jira.plugin... ] Ilia Vassilev updated WFLY-12790: --------------------------------- Release Notes Text: (was: Resolved in CXF 3.3.4) > CXF-8105 - introduce a property for JMS transport client to decide reset JMS connection or not when client timeout > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-12790 > URL: https://issues.jboss.org/browse/WFLY-12790 > Project: WildFly > Issue Type: Enhancement > Components: Web Services > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > > https://issues.apache.org/jira/browse/CXF-8105 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 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 November 2019