Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Assigned Ansible Roles to host group are not automatically installed on the provisioned host after the provisioning is finished.
Version-Release number of selected component (if applicable):
satellite 6.9
satellite 6.10
How reproducible:
100%
Steps to Reproduce:
1.Assign Ansible roles to host group.
2. Increase "Post-provision timeout" to 1500 from satellite GUI.
Administer -> Setting -> Ansible -> Post-provision timeout -> 1500
3. Provision a new machine using the hostgroup.
Actual results:
Assigned Ansible Roles to host group are not automatically installed on the provisioned host after the provisioning is finished.
Expected results:
Assigned Ansible Roles to host group are automatically installed.
(In reply to Ondřej Ezr from comment #2)
> Might this be duplicate of BZ#2025523 ?
yes i believe so.
And workaround from 2025523 by editing host_managed_extensions.rb made it work.
I can close this one as duplicate of BZ#2025523