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.

Created attachment 934209 [details]
foreman debug

Description of problem:
Trying to create a new Openstack CR in Sat 6 on RHEL 7

Version-Release number of selected component (if applicable):
Snap 7 Compose 3

How reproducible:
Always

Steps to Reproduce:
1. Set up Satellite 6 GA Snap 7 Compose 3
2. Attempt to add an Openstack CR
3. Test connection

Actual results:
Unable to save
Permission denied - connect(2) (Errno::EACCES)

Expected results:
Tenants load

Additional info:
Denial is:
type=AVC msg=audit(1409770421.707:2580): avc:  denied  { name_connect } for  pid=7002 comm="ruby" dest=5000 scontext=system_u:system_r:passenger_t:s0 tcontext=system_u:object_r:commplex_main_port_t:s0 tclass=tcp_socket

Need:
require {
	type commplex_main_port_t;
	type passenger_t;
	class tcp_socket name_connect;
}
allow passenger_t commplex_main_port_t:tcp_socket name_connect;

*** This bug has been marked as a duplicate of bug 1136991 ***