[JBoss JIRA] (SWSQE-115) Update Ansible to 2.5 on Jenkins Slaves
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-115?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-115:
------------------------------------------
Description:
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"
was:
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)]
{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)]
{panel}
ansible-playbook test_mesh.yml --syntax-check
playbook: test_mesh.yml (executes it fine)
> Update Ansible to 2.5 on Jenkins Slaves
> ----------------------------------------
>
> Key: SWSQE-115
> URL: https://issues.jboss.org/browse/SWSQE-115
> Project: Kiali QE
> Issue Type: Bug
> 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, 1 month
[JBoss JIRA] (SWSQE-115) Update Ansible to 2.5 on Jenkins Slaves
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-115?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-115:
------------------------------------------
Description:
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)]
{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)]
{panel}
ansible-playbook test_mesh.yml --syntax-check
playbook: test_mesh.yml (executes it fine)
was:
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)]
{panel:title=ansible 2.4.2.0}
{panel}
{panel}
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'>
{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)]
{panel}
ansible-playbook test_mesh.yml --syntax-check
playbook: test_mesh.yml (executes it fine)
> Update Ansible to 2.5 on Jenkins Slaves
> ----------------------------------------
>
> Key: SWSQE-115
> URL: https://issues.jboss.org/browse/SWSQE-115
> Project: Kiali QE
> Issue Type: Bug
> 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)]
> {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)]
> {panel}
> ansible-playbook test_mesh.yml --syntax-check
> playbook: test_mesh.yml (executes it fine)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-115) Update Ansible to 2.5 on Jenkins Slaves
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-115?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-115:
------------------------------------------
Description:
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)]
{panel:title=ansible 2.4.2.0}
{panel}
{panel}
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'>
{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)]
{panel}
ansible-playbook test_mesh.yml --syntax-check
playbook: test_mesh.yml (executes it fine)
was:
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)]
{panel}
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'>
{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)]
{panel}
ansible-playbook test_mesh.yml --syntax-check
playbook: test_mesh.yml (executes it fine)
> Update Ansible to 2.5 on Jenkins Slaves
> ----------------------------------------
>
> Key: SWSQE-115
> URL: https://issues.jboss.org/browse/SWSQE-115
> Project: Kiali QE
> Issue Type: Bug
> 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)]
> {panel:title=ansible 2.4.2.0}
> {panel}
> {panel}
> 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'>
> {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)]
> {panel}
> ansible-playbook test_mesh.yml --syntax-check
> playbook: test_mesh.yml (executes it fine)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-115) Update Ansible to 2.5 on Jenkins Slaves
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-115?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-115:
------------------------------------------
Description:
Hi [~fbrychta],
I needed to update ansible from 2.4 to 2.5 in order to make Test Mesh playbook to work
ansible --version
{panel:title=My 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)]
{panel}
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'>
ansible --version (
> 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)]
ansible-playbook test_mesh.yml --syntax-check
playbook: test_mesh.yml (executes it fine)
was:
Hi [~fbrychta],
I needed to update ansible from 2.4 to 2.5 in order to make Test Mesh playbook to work
ansible --version
> 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)]
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'>
ansible --version (
> 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)]
ansible-playbook test_mesh.yml --syntax-check
playbook: test_mesh.yml (executes it fine)
> Update Ansible to 2.5 on Jenkins Slaves
> ----------------------------------------
>
> Key: SWSQE-115
> URL: https://issues.jboss.org/browse/SWSQE-115
> Project: Kiali QE
> Issue Type: Bug
> 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
> ansible --version
> {panel:title=My 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)]
> {panel}
> 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'>
> ansible --version (
> > 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)]
> ansible-playbook test_mesh.yml --syntax-check
> playbook: test_mesh.yml (executes it fine)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-115) Update Ansible to 2.5 on Jenkins Slaves
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-115?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-115:
------------------------------------------
Description:
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)]
{panel}
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'>
{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)]
{panel}
ansible-playbook test_mesh.yml --syntax-check
playbook: test_mesh.yml (executes it fine)
was:
Hi [~fbrychta],
I needed to update ansible from 2.4 to 2.5 in order to make Test Mesh playbook to work
ansible --version
{panel:title=My 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)]
{panel}
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'>
ansible --version (
> 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)]
ansible-playbook test_mesh.yml --syntax-check
playbook: test_mesh.yml (executes it fine)
> Update Ansible to 2.5 on Jenkins Slaves
> ----------------------------------------
>
> Key: SWSQE-115
> URL: https://issues.jboss.org/browse/SWSQE-115
> Project: Kiali QE
> Issue Type: Bug
> 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)]
> {panel}
> 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'>
> {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)]
> {panel}
> ansible-playbook test_mesh.yml --syntax-check
> playbook: test_mesh.yml (executes it fine)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-115) Update Ansible to 2.5 on Jenkins Slaves
by Guilherme Baufaker Rêgo (JIRA)
Guilherme Baufaker Rêgo created SWSQE-115:
---------------------------------------------
Summary: Update Ansible to 2.5 on Jenkins Slaves
Key: SWSQE-115
URL: https://issues.jboss.org/browse/SWSQE-115
Project: Kiali QE
Issue Type: Bug
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
ansible --version
> 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)]
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'>
ansible --version (
> 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)]
ansible-playbook test_mesh.yml --syntax-check
playbook: test_mesh.yml (executes it fine)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10134) ee8.preview.mode property is racy
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-10134?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-10134:
---------------------------------
Workaround Description: Set the {{ee8.preview.mode}} property in the {{JAVA_OPTS}}. For standalone this can be done in the appropriate {{standalone.conf}} file for the environment. For domain it can be set in the appropriate {{domain.conf}} for the environment in the {{HOST_CONTROLLER_JAVA_OPTS}} environment variable.
> ee8.preview.mode property is racy
> ---------------------------------
>
> Key: WFLY-10134
> URL: https://issues.jboss.org/browse/WFLY-10134
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Reporter: David Lloyd
> Priority: Critical
>
> The {{ee8-temp}} tests set the {{ee8.preview.mode}} property in the server management model, relying on system properties to get parsed and set before extensions which use Java EE 8 APIs are loaded. This assumption appears to be invalid.
> System properties are installed by the boot controller thread, and extensions are loaded in server service threads. In testing with the latest jboss-modules, I've observed cases where the controller thread does not add system properties until after some extension loading has happened in the server service threads. I haven't untangled why this happens only with the most recent jboss-modules in play, but the race exists regardless.
> Setting the {{ee8.preview.mode}} in {{arquillian.xml}} appears to work around the issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3727) NPE in io.undertow.security.impl.BasicAuthenticationMechanism.authenticate when picketbox subsystem removed
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3727?page=com.atlassian.jira.plugi... ]
Stuart Douglas reassigned WFCORE-3727:
--------------------------------------
Assignee: Darran Lofthouse (was: Stuart Douglas)
> NPE in io.undertow.security.impl.BasicAuthenticationMechanism.authenticate when picketbox subsystem removed
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3727
> URL: https://issues.jboss.org/browse/WFCORE-3727
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Ilia Vassilev
> Assignee: Darran Lofthouse
>
> After enabling elytron, the security subsystem was removed. The war using jboss-web.xml security-domain looks like it is not used when the picketbox security subsystem is removed.
> {code}
> java.lang.NullPointerException
> at io.undertow.security.impl.BasicAuthenticationMechanism.authenticate(BasicAuthenticationMechanism.java:167)
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:245)
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:263)
> at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:231)
> at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:125)
> at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:99)
> at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:92)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55)
> at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:330)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> The war has jboss-web.xml:
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-web>
> <security-domain>other</security-domain>
> </jboss-web>
> {code}
> {code}
> <subsystem xmlns="urn:jboss:domain:undertow:4.0">
> ...
> <application-security-domains>
> <application-security-domain name="other" http-authentication-factory="application-http-authentication"/>
> </application-security-domains>
> </subsystem>
> <subsystem xmlns="urn:wildfly:elytron:1.2" final-providers="combined-providers" disallowed-providers="OracleUcrypto">
> ...
> <http>
> <http-authentication-factory name="application-http-authentication" http-server-mechanism-factory="global" security-domain="ApplicationDomain">
> <mechanism-configuration>
> <mechanism mechanism-name="BASIC">
> <mechanism-realm realm-name="Application Realm"/>
> </mechanism>
> <mechanism mechanism-name="FORM"/>
> </mechanism-configuration>
> </http-authentication-factory>
> <provider-http-server-mechanism-factory name="global"/>
> </http>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month