[JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo edited comment on SWSQE-113 at 4/4/18 1:12 PM:
-----------------------------------------------------------------------
In order to document things for elastic search
- Executed {code:shell} oc adm policy add-role-to-user admin system:serviceaccount:jaeger-test:jenkins {code}
- Executed {code:shell} oc adm policy add-role-to-user cluster-admin system:serviceaccount:jaeger-test:jenkins {code}
- Disabled Selinux {code:shell} vi /etc/selinux/config{code} and then set to disabled then reboot
- And executed {code:shell} sudo sysctl -w vm.max_map_count=262144 {code}
was (Author: gbaufake):
In order to document things for elastic search
- Executed {code:shell} oc adm policy add-role-to-user admin system:serviceaccount:jaeger-test:jenkins {code}
- Executed {code:shell} oc adm policy add-role-to-user cluster-admin system:serviceaccount:jaeger-test:jenkins {code}
- Disabled Selinux ({code:shell} vi /etc/selinux/config{code} Set to disable then reboot
- And executed {code:shell} sudo sysctl -w vm.max_map_count=262144 {code}
> Allocate OpenShift and Jenkins resources for testing Jaeger productized images
> ------------------------------------------------------------------------------
>
> Key: SWSQE-113
> URL: https://issues.jboss.org/browse/SWSQE-113
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
>
> I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images. I have already started working with [~fbrychta] but we have not completely resolved this yet.
> I can work with either of these two options
> -- A project on an OpenShift Cluster where I can create my own Jenkins instance.
> -- An external Jenkins which has an agent defined which can run on OpenShift.
> I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible. In that case I'd be happy to use the first solution.
> Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo edited comment on SWSQE-113 at 4/4/18 1:11 PM:
-----------------------------------------------------------------------
In order to document things for elastic search
- Executed {code:shell} oc adm policy add-role-to-user admin system:serviceaccount:jaeger-test:jenkins {code}
- Executed {code:shell} oc adm policy add-role-to-user cluster-admin system:serviceaccount:jaeger-test:jenkins {code}
- Disabled Selinux
- And executed {code:shell} sudo sysctl -w vm.max_map_count=262144 {code}
was (Author: gbaufake):
I added
oc adm policy add-role-to-user admin system:serviceaccount:jaeger-test:jenkins on b11 and disabled Selinux
> Allocate OpenShift and Jenkins resources for testing Jaeger productized images
> ------------------------------------------------------------------------------
>
> Key: SWSQE-113
> URL: https://issues.jboss.org/browse/SWSQE-113
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
>
> I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images. I have already started working with [~fbrychta] but we have not completely resolved this yet.
> I can work with either of these two options
> -- A project on an OpenShift Cluster where I can create my own Jenkins instance.
> -- An external Jenkins which has an agent defined which can run on OpenShift.
> I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible. In that case I'd be happy to use the first solution.
> Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo reassigned SWSQE-113:
---------------------------------------------
Assignee: Guilherme Baufaker Rêgo (was: Filip Brychta)
> Allocate OpenShift and Jenkins resources for testing Jaeger productized images
> ------------------------------------------------------------------------------
>
> Key: SWSQE-113
> URL: https://issues.jboss.org/browse/SWSQE-113
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
>
> I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images. I have already started working with [~fbrychta] but we have not completely resolved this yet.
> I can work with either of these two options
> -- A project on an OpenShift Cluster where I can create my own Jenkins instance.
> -- An external Jenkins which has an agent defined which can run on OpenShift.
> I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible. In that case I'd be happy to use the first solution.
> Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo commented on SWSQE-113:
-----------------------------------------------
I added
oc adm policy add-role-to-user admin system:serviceaccount:jaeger-test:jenkins on b11 and disabled Selinux
> Allocate OpenShift and Jenkins resources for testing Jaeger productized images
> ------------------------------------------------------------------------------
>
> Key: SWSQE-113
> URL: https://issues.jboss.org/browse/SWSQE-113
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Filip Brychta
>
> I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images. I have already started working with [~fbrychta] but we have not completely resolved this yet.
> I can work with either of these two options
> -- A project on an OpenShift Cluster where I can create my own Jenkins instance.
> -- An external Jenkins which has an agent defined which can run on OpenShift.
> I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible. In that case I'd be happy to use the first solution.
> Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[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)
7 years, 6 months
[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)
7 years, 6 months
[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)
7 years, 6 months
[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)
7 years, 6 months