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:

The satellite-installer --upgrade does not cut off client requests, which can result in actions being taken while the upgrade is occurring.

Ideally, users would be able to run a command or rake task to quiesce the satellite server. This would include:

* no longer responding to client checkins under /rhsm
* finishing all pending tasks and not accepting new tasks
* clearing all work queued for "listen on candlepin events" and "monitor event queue" tasks

Once the server is quiesced, the upgrade can proceed. By default, the server will become active once the upgrade is complete.

This feature would mostly be useful for upgrades, but users may want to use it when shutting the satellite down for other maintenance.

I'm planning to add this into the upgrade enhancements, even if it meant just temporarily sutrning on iptables on 443 port, which is one of the ways to achieve this.

For the record, foreman-maintain script will allow "poor's man" solution to proper shutdown, until this RFE is resolved.

Foreman maintain now proivdes this feature. To use it, run the following before the upgrade:

foreman-maintain advanced procedure run maintenance-mode-{dis,en}able