April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2449) Various bugs in executable model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2449?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2449. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/0e4ac1d91487dfdacb46a11d702299f... > Various bugs in executable model > -------------------------------- > > Key: DROOLS-2449 > URL: https://issues.jboss.org/browse/DROOLS-2449 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > > The executable model suffers of the following problems: > * jbpm processes aren't merged into the KieBase generated from the model > * missing nodes sharing when rules belong to different packages > * wrong property reactivity mask in consequence when updating a field via getter (e.g. person.getCars().add("BMW") ) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2450) Various bugs in executable model

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2450: ----------------------------------- Summary: Various bugs in executable model Key: DROOLS-2450 URL: https://issues.jboss.org/browse/DROOLS-2450 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco The executable model suffers of the following problems: * jbpm processes aren't merged into the KieBase generated from the model * missing nodes sharing when rules belong to different packages * wrong property reactivity mask in consequence when updating a field via getter (e.g. person.getCars().add("BMW") ) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9834) Upgrade mod_cluster to 1.3.9.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9834?page=com.atlassian.jira.plugin.... ] Radoslav Husar closed WFLY-9834. -------------------------------- Resolution: Done Duplicate of WFLY-9999. > Upgrade mod_cluster to 1.3.9.Final > ---------------------------------- > > Key: WFLY-9834 > URL: https://issues.jboss.org/browse/WFLY-9834 > Project: WildFly > Issue Type: Component Upgrade > Components: mod_cluster > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Changelog > https://issues.jboss.org/projects/MODCLUSTER/versions/12335982 > Relevant fixes are > * https://issues.jboss.org/browse/MODCLUSTER-639 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2449) Various bugs in executable model

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2449: ----------------------------------- Summary: Various bugs in executable model Key: DROOLS-2449 URL: https://issues.jboss.org/browse/DROOLS-2449 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco The executable model suffers of the following problems: * jbpm processes aren't merged into the KieBase generated from the model * missing nodes sharing when rules belong to different packages * wrong property reactivity mask in consequence when updating a field via getter (e.g. person.getCars().add("BMW") ) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-115) Update Ansible to 2.5 on Jenkins Slaves

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-115?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-115: -------------------------------- Issue Type: Task (was: Bug) > Update Ansible to 2.5 on Jenkins Slaves > ---------------------------------------- > > Key: SWSQE-115 > URL: https://issues.jboss.org/browse/SWSQE-115 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > > Hi [~fbrychta], > I needed to update ansible from 2.4 to 2.5 in order to make Test Mesh playbook to work > {panel:title=ansible 2.4.2.0} > config file = /etc/ansible/ansible.cfg > configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] > ansible python module location = /usr/lib/python2.7/site-packages/ansible > executable location = /usr/bin/ansible > python version = 2.7.5 (default, May 3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)] > By executing the test_mesh ansible playbook, I get a syntax error: > {code:shell} > ansible-playbook test_mesh.yml --syntax-check > ERROR! The field 'loop' is supposed to be a string type, however the incoming data structure is a <class 'ansible.parsing.yaml.objects.AnsibleSequence'> > {code} > {panel} > {panel:title=ansible 2.5.0} > config file = /etc/ansible/ansible.cfg > configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] > ansible python module location = /usr/lib/python2.7/site-packages/ansible > executable location = /bin/ansible > python version = 2.7.14 (default, Mar 14 2018, 13:36:31) [GCC 7.3.1 20180303 (Red Hat 7.3.1-5)] > On Ansible 2.5.0, I don't get the error > {code} > ansible-playbook test_mesh.yml --syntax-check > playbook: test_mesh.yml (executes it fine) > {code} > {panel} > I know that Ansible 2.5.0 was released some days ago, so if we are using on RHEL, maybe it would need to update it from sources, even Brew or Pulp. I was able to track ansible repository (http://pulp.dist.prod.ext.phx2.redhat.com/content/dist/rhel/server/7/7Ser...) but I had no success installing it on slave2. > On Fedora, it is widespread on the "main repositories" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-110) Update OC on Ansible Image

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-110?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-110: -------------------------------- Issue Type: Task (was: Bug) > Update OC on Ansible Image > -------------------------- > > Key: SWSQE-110 > URL: https://issues.jboss.org/browse/SWSQE-110 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > > Started by user Guilherme Baufaker Rêgo > Running in Durability level: MAX_SURVIVABILITY > [Pipeline] node > Still waiting to schedule task > jenkins-slave-ansible-os-client-tools-kxpss is offline > Running on jenkins-slave-ansible-os-client-tools-kxpss in /home/jenkins/workspace/Istio+Mesh+Ansible Pipeline > [Pipeline] { > [Pipeline] stage > [Pipeline] { (Clone Istio Repository) > [Pipeline] checkout > Cloning the remote Git repository > Cloning repository https://github.com/gbaufake/istio.git > > git init /home/jenkins/workspace/Istio+Mesh+Ansible Pipeline/istio # timeout=10 > Fetching upstream changes from https://github.com/gbaufake/istio.git > > git --version # timeout=10 > > git fetch --tags --progress https://github.com/gbaufake/istio.git +refs/heads/*:refs/remotes/origin/* > > git config remote.origin.url https://github.com/gbaufake/istio.git # timeout=10 > > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > > git config remote.origin.url https://github.com/gbaufake/istio.git # timeout=10 > Fetching upstream changes from https://github.com/gbaufake/istio.git > > git fetch --tags --progress https://github.com/gbaufake/istio.git +refs/heads/*:refs/remotes/origin/* > > git rev-parse refs/remotes/origin/kiali-addon^{commit} # timeout=10 > > git rev-parse refs/remotes/origin/origin/kiali-addon^{commit} # timeout=10 > Checking out Revision e5be3cd1b2acc60e3ce4ed798f91366947367e17 (refs/remotes/origin/kiali-addon) > > git config core.sparsecheckout # timeout=10 > > git checkout -f e5be3cd1b2acc60e3ce4ed798f91366947367e17 > Commit message: "Kiali as Istio Addon" > > git rev-list --no-walk e5be3cd1b2acc60e3ce4ed798f91366947367e17 # timeout=10 > [Pipeline] } > [Pipeline] // stage > [Pipeline] stage > [Pipeline] { (Ansible Playbook) > [Pipeline] dir > Running in /home/jenkins/workspace/Istio+Mesh+Ansible Pipeline/istio/install/ansible > [Pipeline] { > [Pipeline] sh > [ansible] Running shell script > + oc login https://osemaster.os37-gbaufake.osepool.centralci.eng.rdu2.redhat.com:8443 --token=cXd1vapqDSQbW3kWxg7qvuuGgKglMlxvQUaGzH4Mf5s --insecure-skip-tls-verify > Logged into "https://osemaster.os37-gbaufake.osepool.centralci.eng.rdu2.redhat.com:8443" as "user1" using the token provided. > You have access to the following projects and can switch between them with 'oc project <projectname>': > bookinfo > * default > istio-system > kiali-test-box > kiali-test-breadth-sink > kiali-test-breath > kiali-test-circle > kiali-test-circle-callback > kiali-test-depth > kiali-test-depth-sink > kiali-test-hourglass > kube-public > kube-system > logging > management-infra > openshift > openshift-infra > openshift-node > samples > Using project "default". > Welcome! See 'oc help' to get started. > [Pipeline] sh > [ansible] Running shell script > + oc version > oc v1.5.0+031cbe4 > kubernetes v1.5.2+43a9be4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > [~fbrychta] can you update oc to 3.7? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-117) Resolve "The node was low on resource: imagefs." on b20

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-117?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-117. --------------------------------- Resolution: Done So here is what was causing the problem. Default threshold is imagefs.available<15%. B20 is already 85% full. Basically it was trying to pull the image but failed because of reaching the threshold. There was not much to clean so I removed the b20 from the cluster. I created SWSQE-116 to reinstall it. > Resolve "The node was low on resource: imagefs." on b20 > ------------------------------------------------------- > > Key: SWSQE-117 > URL: https://issues.jboss.org/browse/SWSQE-117 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > > Jeeva reported problem with pods on b20 which were not started because of "The node was low on resource: imagefs." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-111) Update from Openshift 3.7 to Openshift 3.9

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-111?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-111: ------------------------------------------ Parent Issue: SWSQE-116 (was: SWSQE-63) > Update from Openshift 3.7 to Openshift 3.9 > ------------------------------------------ > > Key: SWSQE-111 > URL: https://issues.jboss.org/browse/SWSQE-111 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-116) Reinstall openshift production cluster

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-116?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-116: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Reinstall openshift production cluster > -------------------------------------- > > Key: SWSQE-116 > URL: https://issues.jboss.org/browse/SWSQE-116 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Guilherme Baufaker Rêgo > > Currently there are following problems with our OS cluster: > * docker on nodes is using loopback devices which is strongly discouraged for production use > * small partition for imagefs and nodefs which is causing issues "The node was low on resource: imagefs" > * different root passwords > We need to: > # investigate recommended partitioning for production OS clusters (also think about RAID versions available on each blade) > # reinstall RHELs with recommended partitions > # Configuring Docker Storage as described in https://docs.openshift.com/container-platform/3.9/install_config/install/... > # install OS 3.9 > # create mojo documentation -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-117) Resolve "The node was low on resource: imagefs." on b20

by Filip Brychta (JIRA)

Filip Brychta created SWSQE-117: ----------------------------------- Summary: Resolve "The node was low on resource: imagefs." on b20 Key: SWSQE-117 URL: https://issues.jboss.org/browse/SWSQE-117 Project: Kiali QE Issue Type: Task Reporter: Filip Brychta Assignee: Filip Brychta Jeeva reported problem with pods on b20 which were not started because of "The node was low on resource: imagefs." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 April 2018