Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Satellite 6 is shipped with Foreman Hooks plugin:

https://github.com/theforeman/foreman_hooks

Documented here:

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/server-administration-guide/102-using-foreman-hooks

When upgrading Satellite, these custom hooks often gets obsolete or not working as they are provided from third party sources. Even hook scripts provided by Red Hat or by Consultants wont work across all versions.

Therefore please add a note in our UPGRADE instructions to BACKUP AND REMOVE all hooks before upgrading. Ask the user to put hooks back only after Satellite is known to be working after upgrade.

Also please add a box in the Using foreman hooks section about the fact that hooks can modify workflows in Satellite and users may be requested to remove all hooks in order to get support from Red Hat.

Thanks

Hello


Changes are now live on the customer portal.

For the Installation Guide, see [1]


For the Server Administration Guide, see [2]

[1] https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server#upgrading_satellite_server


[2] https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/server-administration-guide/102-using-foreman-hooks


However I should have also updated the paragraph with heading "Foreman Hooks' Report Class Renamed to ConfigReport" [3] as it might be irritating to not mention the need to remove hooks before upgrade while explaining about the need to move hooks.

Will improve that now.

[3] https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server





Thank you

Re comment 5

The paragraph with heading "Foreman Hooks' Report Class Renamed to ConfigReport" has been update to take into account the need to remove hooks before upgrading.


Thank you