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.
Description of problem:
When foreman-maintain backup offline fails (i.e. due to insufficient disk space), it does not stop / release maintenance mode. So clients wont be able to connect to the Satellite.
There is no reason to keep Satellite in maintenance mode, and it is unexpected from customer's point of view.
Version-Release number of selected component (if applicable):
Sat 6.8
rubygem-foreman_maintain-0.6.13-1.el7sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. either create some small lvolume, or use some existing one; in example below, I use /boot (which might be dangerous though I use it just for an example?)
2. Run offline backup to a dir on such tiny lvolume:
mkdir /boot/todelete/
foreman-maintain backup offline -y /boot/todelete
3. After the backup fails, check maintenance mode:
foreman-maintain maintenance-mode status
4. optionally try register/check/.. a client to Satellite, or open WebUI
5. remove the incomplete backup (esp. if on /boot :) )
Actual results:
3. shows maintenance-mode: On
4. unable to connect to Sat that way
Expected results:
3. maintenance mode is disabled
4. all functionality/access restored
Additional info:
UPDATE: majority of services remained stopped after the reproducer. That is also a mistake, I think.
So apart of releasing maintenance mode, we should also start the stopped services in this scenario.