You sir, are a Genius... Your employer however irks me....
Yes, that was an exact excerpt from the playbook. And yes, the pool name was wrong. But the playbook USED to work and I got that pool name from Red Hat Subscription Manager a while back. Not only that, but that pool name is used in the examples in the Ansible documentation (proof to me that I wasn't imagining it)... So I suspect that at some point in the last month or so Red Hat changed the name of the pool. (Or fixed it so that the wrong name would no longer work). Anyway... Thank you for your assistance. Adam On Tuesday, April 5, 2016 at 3:08:54 PM UTC-7, [email protected] wrote: > > > It does sound like the system isn't attached to any subscription pools, > which likely means > auto-attach failed (or possibly, if it was working before, that a > subscription expired). > > /var/log/rhsm/rhsm.log on that system should indicate if there was a > failure. Also just > checking 'subscription-manager list' or 'subscription-manager repos > --list-enabled' to > see if it's registered but not attached ('subscribed') or if it's > registered+subscribed but > missing applicable repos. > > Oh, and if that's a direct cut of the playbook, the pool name may be wrong > [ 'RedHat Enterprise Server' vs 'Red Hat Enterprise Linux Server' etc) > > On Monday, April 4, 2016 at 6:36:58 PM UTC-4, Adam Morris wrote: >> >> Greetings, >> >> I have been using Ansible for a while now and one of my playbooks for >> configuring servers includes this... >> >> - name: Register a Redhat system (>= RHEL 6) >> redhat_subscription: state=present username=<redacted> >> password=<redacted> >> pool='\ARedHat Enterprise Server\Z' >> autosubscribe=true >> when: ansible_distribution == "RedHat" and ansible_distribution_version >> >= "6.0" >> >> - name: make sure yum-utils is installed >> raw: yum -y install yum-utils >> when: ansible_os_family == "RedHat" >> >> This was working perfectly, but recently I have been getting errors like >> this... >> >> TASK [common : Register a Redhat system (>= RHEL 6)] >> *************************** >> >> ok: [u90324] >> >> >> >> TASK [common : make sure yum-utils is installed] >> ******************************* >> >> fatal: [u90324]: FAILED! => {"changed": false, "failed": true, "rc": 1, >> "stderr": "", "stdout": "Loaded plugins: langpacks, product-id, >> subscription-manager\r\nThis system is registered to Red Hat Subscription >> Management, but is not receiving updates. You can use subscription-manager >> to assign subscriptions.\r\nThere are no enabled repos.\r\n Run \"yum >> repolist all\" to see the repos you have.\r\n You can enable repos with >> yum-config-manager --enable <repo>\r\n", "stdout_lines": ["Loaded plugins: >> langpacks, product-id, subscription-manager", "This system is registered to >> Red Hat Subscription Management, but is not receiving updates. You can use >> subscription-manager to assign subscriptions.", "There are no enabled >> repos.", " Run \"yum repolist all\" to see the repos you have.", " You can >> enable repos with yum-config-manager --enable <repo>"]} >> >> >> I think that this might be an issue with subscription manager rather than >> Ansible, but has anyone else seen this or is this just my problem? I am >> wondering whether RedHat has broken auto-attach... Probably time to break >> out the VM and test this all again. >> >> >> Thanks, >> >> >> Adam >> > -- 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/80ec9610-9d1b-46cc-990d-9cd6ef4020d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
