Yum module having weird results

Latest response

I am running a post build ansible playbook that installs required packages and makes various config changes. We use Satellite 6.3. After a fresh build I my playbook gets stuck when it runs the yum module. This is at the begining of the playbook, below is the piece where it gets stuck.


  • hosts: "{{ host }}"
    gather_facts: true
    become: true

    tasks:

    • name: Install required packages
      yum:
      name: "{{ packages }}"
      vars:
      packages:

      • net-snmp
      • net-snmp-utils
      • net-snmp-libs
      • sg3_utils
      • nfs-utils
      • vim-enhanced
      • net-tools
      • bash-completion
      • bind-utils
      • lsof

The playbook will stay here indefenitley or until I kill the play. This is the only thing I see in the messages log of the target server. This repeats until I kill the play. I am able to run the yum install manually and it does what it should without issue. Any idea why this is happening with yum via ansible?

Sep 12 14:45:34 pcyv472771 subscription-manager: Added subscription for 'Content Access' contract 'None'
Sep 12 14:45:34 pcyv472771 subscription-manager: Added subscription for product ' Content Access'
Sep 12 14:45:39 pcyv472771 subscription-manager: Added subscription for 'Content Access' contract 'None'
Sep 12 14:45:39 pcyv472771 subscription-manager: Added subscription for product ' Content Access'

Responses

Ronald,

I haven't run into this before, but the message seems to indicate that the host does not have a valid subscription. It appears to be trying to apply a subscription called "Content Access" rather than something like "Red Hat Enterprise Linux Server" or another valid product name. I would look a bit earlier and verify that the host has a valid subscription.