Description of problem: Retirement log message should include who initiated the retirement. Version-Release number of selected component (if applicable): 5.9, has been fixed on master here: https://github.com/ManageIQ/manageiq/pull/17898 How reproducible: always Steps to Reproduce: retire a thing and see that https://github.com/ManageIQ/manageiq/pull/17898/files#diff-5c80c9a5ecc28374ffccc13421a61b65L206 doesn't include info about who started the retirement 1. 2. 3. Actual results: Expected results: Additional info:
https://github.com/ManageIQ/manageiq/pull/17944
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
Hey Ievgen! So it looks like that never got merged on the g/branch, so you'd have to be on a more recent appliance than that. Could you please tell me what version you are on?
Ah, thanks. Any chance you might be willing to give me the IP please so I can see what's happening?
Created attachment 1494480 [details] 0 count of original log message
I attached a screenshot, the logs don't even show the original log message before I changed it in that PR. Could you please retry a retirement (not one that's scheduled, one that happens immediately)?
Could you please test this PR on the CFME UI? I'm not sure how this behaves on a pod.
Hey Ievgen! I'm so sorry about this. I think if you look at the appliance logs you'll see: Requester [admin] raising Retirement Event for [cu-24x7] with queue options: {:zone=>"default"} I gave you wrong information earlier, the method that runs this logging only happens on system retirement, not retire_now. So in the UI if you set something to retire sometime in the future that's more than 15 minutes (15 minutes being the regularity with which the scheduler on that box is running) you'll be able to test this. Sorry for the confusion!
Verified in 5.10.0.20
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0212