October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-228) Move 'galleon-m2-repository' from '/home/jboss' to opt

by Michal Jurc (Jira)

[ https://issues.jboss.org/browse/WFWIP-228?page=com.atlassian.jira.plugin.... ] Michal Jurc reassigned WFWIP-228: --------------------------------- Assignee: Jean Francois Denise (was: Brian Stansberry) > Move 'galleon-m2-repository' from '/home/jboss' to opt > ------------------------------------------------------ > > Key: WFWIP-228 > URL: https://issues.jboss.org/browse/WFWIP-228 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Michal Jurc > Assignee: Jean Francois Denise > Priority: Major > > I would recommend moving the {{galleon-m2-repository}} from {{/home/jboss}} in the EAP/WF Galleon builder image from {{~}} to {{/opt}}. As a user, I'd expect the home to be clean after a fresh initialization :) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-228) Move 'galleon-m2-repository' from '/home/jboss' to opt

by Michal Jurc (Jira)

Michal Jurc created WFWIP-228: --------------------------------- Summary: Move 'galleon-m2-repository' from '/home/jboss' to opt Key: WFWIP-228 URL: https://issues.jboss.org/browse/WFWIP-228 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Michal Jurc Assignee: Brian Stansberry I would recommend moving the {{galleon-m2-repository}} from {{/home/jboss}} in the EAP/WF Galleon builder image from {{~}} to {{/opt}}. As a user, I'd expect the home to be clean after a fresh initialization :) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-187: ----------------------------------- [~mchoma] PCV is not created directly by the operator. The operator creates a statefulset and in its spec, it configures *volumeClaimTemplates*[1]. When and how the StatefulSet updates the PVC based on these templates is out of scope of the operator. So if you update the operator storageSpec, you will see that the statefulset.spec.volumeClaimTemplates is updated but the corresponding PVC is not. This seems correct to me as persistent volume are tightly bound to the statefulset. [1] https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.16/#stat... > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-211) emptyDir.sizeLimit not propagated to Pod Spec

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-211?page=com.atlassian.jira.plugin.... ] Martin Choma closed WFWIP-211. ------------------------------ I have created OpenShift bug https://bugzilla.redhat.com/show_bug.cgi?id=1758434. Closing this as nothing to be done in Operator. > emptyDir.sizeLimit not propagated to Pod Spec > --------------------------------------------- > > Key: WFWIP-211 > URL: https://issues.jboss.org/browse/WFWIP-211 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > # {code:yaml} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > name: operator-empty-dir > namespace: mchoma > spec: > applicationImage: 'registry.access.redhat.com/jboss-eap-7/eap72-openshift:1.1' > size: 1 > storage: > emptyDir: > medium: Memory > sizeLimit: 1Mi > {code} > # wait until pod are started and look into pod yaml definition "1 Mi" is not there > {code:yaml} > ... > serviceAccount: default > serviceAccountName: default > subdomain: operator-empty-dir-headless > terminationGracePeriodSeconds: 30 > volumes: > - emptyDir: > medium: Memory > name: operator-empty-dir-volume > - name: default-token-j2grg > secret: > defaultMode: 420 > secretName: default-token-j2grg > status: > conditions: > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-211) emptyDir.sizeLimit not propagated to Pod Spec

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-211?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFWIP-211: ------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1758434 > emptyDir.sizeLimit not propagated to Pod Spec > --------------------------------------------- > > Key: WFWIP-211 > URL: https://issues.jboss.org/browse/WFWIP-211 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > # {code:yaml} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > name: operator-empty-dir > namespace: mchoma > spec: > applicationImage: 'registry.access.redhat.com/jboss-eap-7/eap72-openshift:1.1' > size: 1 > storage: > emptyDir: > medium: Memory > sizeLimit: 1Mi > {code} > # wait until pod are started and look into pod yaml definition "1 Mi" is not there > {code:yaml} > ... > serviceAccount: default > serviceAccountName: default > subdomain: operator-empty-dir-headless > terminationGracePeriodSeconds: 30 > volumes: > - emptyDir: > medium: Memory > name: operator-empty-dir-volume > - name: default-token-j2grg > secret: > defaultMode: 420 > secretName: default-token-j2grg > status: > conditions: > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Martin Choma edited comment on WFWIP-187 at 10/4/19 2:27 AM: ------------------------------------------------------------- [~jmesnil] Question is if kubernetes PVC object should be updated on Operator change. Operator does not do that now for PVC, but does for StatefulSet and Service, so we are at least inconsistent here regarding operator managing kubernetes objects. In case resizing is by default off now (in future can be on), doesn't mean operator cant update PVC. There can be other data changed on PVC (label, annotation, selectros...[1]). I can change reproducer to them if this is necessary. But the point is should be PVC object updated with Operator update? I don't see reason why shouldn't. [1] https://docs.openshift.com/container-platform/3.11/rest_api/api/v1.Persis... was (Author: mchoma): Question is if kubernetes PVC object should be updated on Operator change. Operator does not do that now for PVC, but does for StatefulSet and Service, so we are at least inconsistent here regarding operator managing kubernetes objects. In case resizing is by default off now (in future can be on), doesn't mean operator cant update PVC. There can be other data changed on PVC (label, annotation, selectros...[1]). I can change reproducer to them if this is necessary. But the point is should be PVC object updated with Operator update? I don't see reason why shouldn't. [1] https://docs.openshift.com/container-platform/3.11/rest_api/api/v1.Persis... > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Martin Choma reopened WFWIP-187: -------------------------------- Question is if kubernetes PVC object should be updated on Operator change. Operator does not do that now for PVC, but does for StatefulSet and Service, so we are at least inconsistent here regarding operator managing kubernetes objects. In case resizing is by default off now (in future can be on), doesn't mean operator cant update PVC. There can be other data changed on PVC (label, annotation, selectros...[1]). I can change reproducer to them if this is necessary. But the point is should be PVC object updated with Operator update? I don't see reason why shouldn't. [1] https://docs.openshift.com/container-platform/3.11/rest_api/api/v1.Persis... > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4602) kie-maven-plugin fails with nested kbases and dependency versions declared in bom

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4602?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-4602: ----------------------------------- Assignee: Tibor Zimanyi (was: Mario Fusco) > kie-maven-plugin fails with nested kbases and dependency versions declared in bom > --------------------------------------------------------------------------------- > > Key: DROOLS-4602 > URL: https://issues.jboss.org/browse/DROOLS-4602 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 7.27.0.Final > Reporter: Martin Weiler > Assignee: Tibor Zimanyi > Priority: Major > Labels: support > Attachments: hierarchical-kbase-bom.zip > > > When we build 2 kjars and one kbase "includes" another, kie-maven-plugin fails to resolve the sub kbase if the dependency version is declared in a common bom: > {noformat} > Running test with rules version 7.27.0.Final and -DgenerateModel=NO > 13:01:05,903 [ERROR] Unable to build KieBase, could not find include: subkbase > 13:01:05,908 [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.27.0.Final:build (default-build) on project kbase-parent: Execution default-build of goal org.kie:kie-maven-plugin:7.27.0.Final:build failed: Unable to get KieModule, Errors Existed: Error Messages: > 13:01:05,910 [ERROR] Message [id=1, kieBase=parentkbase, level=ERROR, path=src/main/resources/META-INF/kmodule.xml, line=0, column=0 > 13:01:05,911 [ERROR] text=Unable to build KieBase, could not find include: subkbase] > {noformat} > Note that such a build is successful with RHDM 7.3.1 if the executable model is *not* used (see reproducer). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-199) Operator default values

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-199?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-199: ------------------------------------ [~jmesnil] is this done? Could you mark it resolved so we can check it? > Operator default values > ----------------------- > > Key: WFWIP-199 > URL: https://issues.jboss.org/browse/WFWIP-199 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > Labels: operator > > How should user find default values of parameters? > E.g. for disableHTTPRoute and sessionAffinity. I couldn't find it in api doc [1]. > Looking into CRD [2] I can't see defaults neither. So can user assume default is false? > Could it be somewhere declared explicitly? I think best would be CRD or at leas api doc. > [1] https://github.com/wildfly/wildfly-operator/blob/master/doc/apis.adoc#wil... > [2] https://github.com/wildfly/wildfly-operator/blob/master/deploy/crds/wildf... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-196) Operator missing volumes from secrets and config maps

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-196?page=com.atlassian.jira.plugin.... ] Martin Choma closed WFWIP-196. ------------------------------ I can confirm feature is in registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-tech-preview-ea.... We have developed tests and we have found no issues with feature. > Operator missing volumes from secrets and config maps > ------------------------------------------------------ > > Key: WFWIP-196 > URL: https://issues.jboss.org/browse/WFWIP-196 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Operator is missing way of configuring volumes from secets and config maps > - secrets > -- configuring keystore in ssl > -- configuring keystore for jgroups ASYNC encryption in jgroups (DNS_PING, KUBE_PING)) > - config map > -- Microprofile Config and reading properties from ConfigMap > -- running custom CLI script from config map (EAP7-892) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019