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.

Templates API does proxy all templates kinds, but it requires URL to be in this form:

/unattended/:kind

In case of hostgroup provisioning, URLs are different:

/unattended/template/XXX/YYY

[lzap@lzapx foreman]$ curl -3 -H "Accept:application/json" -H "Content-Type: application/json" -d '{}' -k -X GET http://localhost:8448/unattended/template
Failed to retrieve template template for {"splat"=>[], "captures"=>["template"], "kind"=>"template"}: Error retrieving template for {:url=>"http://192.168.122.1:8448"} from 127.0.0.1: Net::HTTPNotFound

[lzap@lzapx foreman]$ curl -3 -H "Accept:application/json" -H "Content-Type: application/json" -d '{}' -k -X GET http://localhost:8448/unattended/template/clonetest/test-machines-rhel68

Requested url was not found

Workaround: Configure Satellite for direct access (non-proxied mode).

Upstream bug assigned to lzap

Upstream bug component is Uncategorized

Upstream bug assigned to lzap

Upstream bug component is Uncategorized

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17045 has been resolved.

Since this is 6.2 and 6.3 bug, I am cloning this one into 6.3 as well.

We are closing this as resolved in the next release as it is fixed in the upcoming rebase of 6.3