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:
Currently, there's a gap in the integration of being able to update RHV hosts - Satellite doesn't verify hosts are in 'maintenance' mode before updating them.
In fact, if they are not, it should put them into maintenance mode (with a clear reason for doing so) - and verify it succeeded to do so.
If a host is running VMs and packages underneath are being upgraded, things may go south.
Note that unfortunately there is no way ATM to 'lock' a host into maintenance mode, so theoretically there's a chance for someone to move it back to 'UP' state (which is why the reason is needed).
Version-Release number of selected component (if applicable):
Any
How reproducible:
Always.
Additional info:
See https://bugzilla.redhat.com/show_bug.cgi?id=1157372#c9 for a customer use case for this.
Ivan, this is not a RFE. I contemplated on this, but I concluded it as a gap in the feature design (and therefore implementation), which may have severe consequences for the customer environment.
I'm not sure this kind of automation shouln't go into CloudForms , that should have more overview around the virtualiation layout (and has some methods around entering maintetnace mode into VSphere already).
https://access.redhat.com/documentation/en/red-hat-cloudforms/4.1/paged/methods-available-for-automation/chapter-1-methods-available-for-use-with-cloudforms-management-engine
As a short-term solution, if using the remote execution functionality with 6.2, it's possible to provide custom template for updates, and additional scripting could be put into the template to turn the host into maintanence mode. It would require however for the host to be able to turn itself into maintanence mode from command line.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.