The subscription is now performed passing the --force option: TASK [redhat-subscription : Manage Red Hat subscription] *********************** Monday 17 June 2019 08:50:01 -0400 (0:00:00.398) 0:01:13.303 *********** fatal: [controller-0]: FAILED! => {"changed": false, "cmd": "/sbin/subscription-manager register --force --baseurl https://rhos-compute-node-08.lab.eng.rdu2.redhat.com/pulp/repos --org Default_Organization --activationkey VALUE_SPECIFIED_IN_NO_LOG_PARAMETER", "msg": "", "rc": 1, "stderr": "", "stderr_lines": [], "stdout": "The system has been registered with ID: 236c7f6f-6159-4f7b-940e-d7a9939b3132\nThe registered system name is: controller-0\nInstalled Product Current Status:\nProduct Name: Red Hat OpenStack\nStatus: Not Subscribed\n\nProduct Name: Red Hat Ceph Storage\nStatus: Not Subscribed\n\nProduct Name: Red Hat Ceph Storage MON\nStatus: Not Subscribed\n\nProduct Name: Red Hat Ceph Storage OSD\nStatus: Not Subscribed\n\nProduct Name: Red Hat Enterprise Linux Server\nStatus: Not Subscribed\n\nProduct Name: Red Hat Enterprise Linux High Availability (for RHEL Server)\nStatus: Not Subscribed\n\nUnable to find available subscriptions for all your installed products.\n", "stdout_lines": ["The system has been registered with ID: 236c7f6f-6159-4f7b-940e-d7a9939b3132", "The registered system name is: controller-0", "Installed Product Current Status:", "Product Name: Red Hat OpenStack", "Status: Not Subscribed", "", "Product Name: Red Hat Ceph Storage", "Status: Not Subscribed", "", "Product Name: Red Hat Ceph Storage MON", "Status: Not Subscribed", "", "Product Name: Red Hat Ceph Storage OSD", "Status: Not Subscribed", "", "Product Name: Red Hat Enterprise Linux Server", "Status: Not Subscribed", "", "Product Name: Red Hat Enterprise Linux High Availability (for RHEL Server)", "Status: Not Subscribed", "", "Unable to find available subscriptions for all your installed products."]} The task failure seems to be due to the Satellite subscription configruation. Tested with puddle: 2019-06-10.3
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:1672