I can reproduce this error on a Red Hat Enterprise Linux Server 7.3 Maipo
vm.
(duchess) [duchess@localhost:jeffrey-wen] ansible-playbook yum.yml
PLAY [Test yum module installs.]
***********************************************
TASK [setup]
*******************************************************************
ok: [localhost]
TASK [Install base applications]
***********************************************
failed: [localhost] (item=[u'epel-release', u'vim-enhanced', u'gcc', u'wget'
, u'libsemanage-python', u'policycoreutils-python', u'setroubleshoot', u
'tmux']) => {"changed":false,"failed":true,"item": ["epel-release",
"vim-enhanced", "gcc", "wget", "libsemanage-python",
"policycoreutils-python", "setroubleshoot", "tmux"], "msg": "No package
matching 'epel-release' found available,installed or updated", "rc": 126,
"results": ["No package matching 'epel-release' found available, installed
or updated"]}
PLAY RECAP
*********************************************************************
localhost : ok=1 changed=0 unreachable=0 failed=1
(duchess) [duchess@localhost:jeffrey-wen] ansible --version
ansible 2.2.0.0
config file = /etc/ansible/ansible.cfg
configured module search path = Default w/o overrides
(duchess) [duchess@localhost:jeffrey-wen] cat yum.yml
---
- name: Test yum module installs.
hosts: localhost
become: yes
tasks:
- name: Install base applications
yum:
name: "{{ item }}"
state: present
with_items:
- epel-release
- vim-enhanced
- gcc
- wget
- libsemanage-python
- policycoreutils-python
- setroubleshoot
- tmux
...
# vim: ft=ansible:
(duchess) [duchess@localhost:jeffrey-wen] cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.3 (Maipo)
I suppose CentOS is more forgiving than RHEL, but the way to make this work
as you intend is to adjust your playbook so that 'epel-release' is
installed with the yum_repository module, like so:
---
- name: Test yum module installs.
hosts: localhost
become: yes
tasks:
- name: What if we use yum_repository?
yum_repository:
baseurl: https://dl.fedoraproject.org/pub/epel/7Server/x86_64/
description: "Epel release."
name: epel-release
state: present
- name: Install base applications
yum:
name: "{{ item }}"
state: present
with_items:
- gcc
- libsemanage-python
- policycoreutils-python
- setroubleshoot
- tmux
- vim-enhanced
- wget
...
# vim: ft=ansible:
Which will produce the following output:
(duchess) [duchess@localhost:jeffrey-wen] ansible-playbook yum.yml
PLAY [Test yum module installs.]
***********************************************
TASK [setup]
*******************************************************************
ok: [localhost]
TASK [What if we use yum_repository?]
******************************************
changed: [localhost]
TASK [Install base applications]
***********************************************
changed: [localhost] => (item=[u'gcc', u'libsemanage-python', u
'policycoreutils-python', u'setroubleshoot', u'tmux', u'vim-enhanced', u
'wget'])
PLAY RECAP
*********************************************************************
localhost : ok=3 changed=2 unreachable=0 failed=0
Hope that helps.
Cheers mate!
On Wednesday, November 23, 2016 at 12:27:53 PM UTC-8, Alexander H. Laughlin
wrote:
>
> I have not yet had time to set up a test bed for this, but I'm planning on
> doing that today so I'll update you with my results.
>
> On Wed, Nov 23, 2016 at 6:20 AM 'Jeffrey Wen' via Ansible Project <
> [email protected]> wrote:
>
>> I have confirmed that this does work on *CentOS Linux release 7.2.1511
>> (Core)*
>>
>> However, it does not work on *Red Hat Enterprise Linux Server release
>> 7.3 (Maipo)*
>>
>>
>> On Tuesday, November 22, 2016 at 9:50:36 PM UTC-5, Jeffrey Wen wrote:
>>>
>>> I am using Red Hat Enterprise Linux Server release 7.3 (Maipo)
>>>
>>> On Tuesday, November 22, 2016 at 5:23:51 PM UTC-5, Alexander H. Laughlin
>>> wrote:
>>>>
>>>> I'm afraid I can't reproduce this on a CentOS 7 vm running in
>>>> virtualbox. Are you using RedHat? If so, which version?
>>>>
>>>> The playbook I used for reference, along with the results.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> (duchess) [duchess@centos:jeffrey-wen] cat yum.yml
>>>>
>>>> ---
>>>>
>>>> - name: Test yum module installs.
>>>>
>>>> hosts: localhost
>>>>
>>>> become: yes
>>>>
>>>> tasks:
>>>>
>>>> - name: Install base applications
>>>>
>>>> yum:
>>>>
>>>> name: "{{ item }}"
>>>>
>>>> state: present
>>>>
>>>> with_items:
>>>>
>>>> - epel-release
>>>>
>>>> - vim-enhanced
>>>>
>>>> - gcc
>>>>
>>>> - wget
>>>>
>>>> - libsemanage-python
>>>>
>>>> - policycoreutils-python
>>>>
>>>> - setroubleshoot
>>>>
>>>> - tmux
>>>>
>>>> ...
>>>>
>>>> # vim: ft=ansible:
>>>>
>>>> (duchess) [duchess@centos:jeffrey-wen] ansible-playbook yum.yml
>>>>
>>>> PLAY [Test yum module installs.]
>>>> ***********************************************
>>>>
>>>>
>>>> TASK [setup]
>>>> *******************************************************************
>>>>
>>>>
>>>> ok: [localhost]
>>>>
>>>>
>>>> TASK [Install base applications]
>>>> ***********************************************
>>>>
>>>> changed: [localhost] => (item=[u'epel-release', u'vim-enhanced', u'gcc'
>>>> , u'wget', u'libsemanage-python', u'policycoreutils-python', u
>>>> 'setroubleshoot', u'tmux'])
>>>>
>>>>
>>>> PLAY RECAP
>>>> *********************************************************************
>>>>
>>>> localhost : ok=2 changed=1 unreachable=0
>>>> failed=0
>>>>
>>>>
>>>> (duchess) [duchess@centos:jeffrey-wen] ansible --version
>>>>
>>>> ansible 2.2.0.0
>>>>
>>>> config file = /etc/ansible/ansible.cfg
>>>>
>>>> configured module search path = Default w/o overrides
>>>>
>>>> (duchess) [duchess@centos:jeffrey-wen]
>>>>
>>>>
>>>> On Tuesday, November 22, 2016 at 11:27:51 AM UTC-8, Jeffrey Wen wrote:
>>>>>
>>>>> My playbook that installs some generic applications on all of my
>>>>> servers:
>>>>>
>>>>> - name: Install base applications
>>>>> yum: name={{ item }} state=present
>>>>> with_items:
>>>>> - epel-release
>>>>> - vim-enhanced
>>>>> - gcc
>>>>> - wget
>>>>> - libsemanage-python
>>>>> - policycoreutils-python
>>>>> - setroubleshoot
>>>>> - tmux
>>>>>
>>>>>
>>>>> I get an error message for each of the following packages:
>>>>> "msg": "No package matching 'libsemanage-python' found available,
>>>>> installed or updated", "rc": 126
>>>>>
>>>>> "msg": "No package matching 'policycoreutils-python' found available,
>>>>> installed or updated", "rc": 126
>>>>>
>>>>> "msg": "No package matching 'setroubleshoot found available,
>>>>> installed or updated", "rc": 126
>>>>>
>>>>> "msg": "No package matching 'tmux' found available, installed or
>>>>> updated", "rc": 126
>>>>>
>>>>> If I remove those packages from the item list, the install goes
>>>>> through fine.
>>>>>
>>>>> I have also verified that if I manually run the following command on
>>>>> the remote server, it exists
>>>>> yum install libsemanage-python policycoreutils-python setroubleshoot
>>>>> tmux
>>>>>
>>>>> If I remove the package from the item list and install it
>>>>> individually, it will *work*:
>>>>> - name: Install libsemanage-python
>>>>> yum: name=libsemanage-python state=present
>>>>>
>>>>> *Has anyone run into a similar scenario and figured out why it is
>>>>> causing this?*
>>>>>
>>>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Ansible Project" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/ansible-project/WnKg0GYz0O8/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> To post to this group, send email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ansible-project/0380bea5-1624-41c4-ad2a-270caf8d8efa%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/ansible-project/0380bea5-1624-41c4-ad2a-270caf8d8efa%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> A. H. Laughlin
> Chief Financial Officer
> Office of Finance
> Gahan Corporation
>
>
--
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/f1596b64-e5d0-4a6e-b30c-9cd46f5c3311%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
