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.

In Red Hat Satellite 6.2, it is possible to move from a disconnected environment to a connected environment.

An outline of how to perform this transition must be added to the documentation.

Upstream bug assigned to ehelms

Upstream bug component is Content Management

Moving to POST since upstream bug http://projects.theforeman.org/issues/10950 has been closed
-------------
Eric Helms
Applied in changeset commit:katello|8dca623812b7b0895e90d45988916e99296df5f7.

Hi Bryan,

Thank you for checking in on this bug.

My main aim in raising this one is to cover the workload required to add a note or procedure to the documentation and provide guidance to users.

Would it be ok to keep this one in the documentation queue? My apologies if I have misunderstood the proper process or what we might required on the documentation side.

Kind regards,

Andrew