Description of problem:

When a user tries to import a manifest of type SAM into Satellite, is does not import properly. When viewing the Manifest pop up in the UI after a failed attempt, users can not refresh or delete the manifest, the options are greyed out.

Trying to change the manifest type to Satellite in the portal and import the manifest has same issues, i.e. the manifest never imports.

Propose we prevent users from being able to import any manifest that is not Satellite type. Currently there is still an option in access.redhat.com to create a SAM Manifest type. This option is still available in access.redhat.com to be used as a manifest type. There is an RFE to remove it from the portal:

https://issues.redhat.com/browse/TEAMNADO-7674

However, that RFE is dependent on another RFE, because some users still use these SAM Manifests for non-satellite applications, i.e. BigFix and JFrog:

https://issues.redhat.com/browse/RHEL-7079 

How reproducible:
always
 

Is this issue a regression from an earlier version:
seems like it could be a regression, because I recall earlier Satellite's not having an issue with SAM Manifest types
 

Steps to Reproduce:

1. create a SAM Manifest from access.redhat.com

2. add subscriptions to it

3. try to import it into the Satellite UI

Actual behavior:
The manifest does not import properly. The import page shows the "Refresh" and "Delete" options as greyed out

Expected behavior:
Satellite should verify they manifest type, and reject anything that isn't a Satellite manifest type.