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:
When creating and modifying provisioning templates within the Satellite 6.x web interface there is no easy way (discoverable!!) to test the modifications except repeatedly building systems and watching them fail, then read piles of logs, turn on debugging, etc..
Version-Release number of selected component (if applicable):
6.1.5
How reproducible:
always
Steps to Reproduce:
1. Create a template.
2. Intentionally create code that fails to build
3. Provision a machine
Actual results:
The kickstart template build fails. Satellite continues provisioning the machine. The system build usually fails. No notification that the system build failed. The system remains stuck in the building state. Someone has to determine that it is a stuck build rather than a slow build. Connect to a console for the system and see why it is stuck. Determine that the template failed to be retrieved. Determine why the template didn't work in the first place.
Expected results:
The kickstart template build fails. An error is generated. Satellite rolls back the provisioning operation (kind of like when registering/setting up the system in IdM fails).
The user then can see which portion of the template (provisioning/snippet/finish) failed and then use a test template button (maybe beside the Resolve Template button - or better yet on a diagnostics page) and use this to refine templates to meet a build.. Probably better as part of a hostgroup configuration.
Additional info:
Workaround Create a new host and submit the provisioning request. Go to the Compute resource and power off the vm machine. Using the IP address information in the host build tab access:
https://sat6.example.com/unattended/provision?spoof=IPADDR
This will indeed show you exactly which template is causing the problem and give you an as-good-as-it-gets error message.
Documented in an odd place - What's inside provisioning templates. Not listed in troubleshooting templates on the Foreman site. Should also be list in troubleshooting templates.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.