-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vm retirement is processed by VmRetireRequest state machine. #552
Conversation
Checked commit lfu@b910330 with ruby 2.4.6, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0 |
Pull Request Test Coverage Report for Build 3364
💛 - Coveralls |
Prior to 5.11, retirement (using retire_now) was event based. When retire_now was called for VM retirement, a request_vm_retire event would be raised and come through the event policy request_vm_retire instance in this PR. The code change in this PR removes the unused entries in the request_vm_retire instance, while leaving the necessary policy event check connection. |
@mkanoor Please review. |
@tinaafitz @lfu |
Yes, @mkanoor, that makes sense. I added a doc release note flag to the ticket. We should document any changes to the ManageIQ domain. |
Vm retirement is processed by VmRetireRequest state machine. (cherry picked from commit 3e2fb4b) https://bugzilla.redhat.com/show_bug.cgi?id=1783361
Hammer backport details:
|
Vm retirement is processed by VmRetireRequest state machine. (cherry picked from commit 3e2fb4b) https://bugzilla.redhat.com/show_bug.cgi?id=1783360
Ivanchuk backport details:
|
Blocks ManageIQ/manageiq#19064.
https://bugzilla.redhat.com/show_bug.cgi?id=1702018
@miq-bot add_label bug, hammer/yes, ivanchuk/yes, changelog/yes