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:
I have not tested this scenario yet, but I'm pretty sure we haven't accounted for it yet.

If a user sets a capsule as the content source for a provision, but that capsule does not actually have the content, it's obv. not going to work.

We need to implement checks to see if content for a desired installation exists on a capsule before allowing user to select it.

[10:26] < jsherrill> cswiii: we also need to validate that there is a kickstart tree with that release version and arch in the selected content view/lifecycle environment



Version-Release number of selected component (if applicable):

Satellite-6.0.3-RHEL-6-20140626.1

Yes, it is.  At host save time, we could validate that a kickstart tree is actually synced to a specified capsule

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.