Description of problem: UI enhancement to display the (service/vm) retirement_state attribute in the Lifecycle section of VM, Instance and Service in addition to the retirement_date. The possible values are 'retiring', 'retired', and 'error'. The new retirement enhancement uses the retirement_state attribute to track the retirement progress. The retired flag and date are set at the end of a successful retirement state machine as opposed to the previous behavior which was to set the retired flag and date at the beginning of retirement, regardless of the success/failure of the retirement. This information is important because it will show that a retirement process in in progress and/or failed with an error. Without this change, the user would have no idea that a retirement is in progress or failed with an error. Additional info: https://trello.com/c/SjGRWKZM
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/228d6ffb9d10e5ca7e7b2544019e8866566051a2 commit 228d6ffb9d10e5ca7e7b2544019e8866566051a2 Author: Tina Fitzgerald <tfitzger> AuthorDate: Fri Mar 20 15:35:43 2015 -0400 Commit: Tina Fitzgerald <tfitzger> CommitDate: Mon Mar 23 15:45:42 2015 -0400 Add retirement_state to service and VM summary information. Removed duplicate code from cloud and infra helpers https://bugzilla.redhat.com/show_bug.cgi?id=1203301 vmdb/app/helpers/service_helper/textual_summary.rb | 6 +++- .../app/helpers/vm_cloud_helper/textual_summary.rb | 33 ---------------------- vmdb/app/helpers/vm_helper/textual_summary.rb | 6 +++- .../app/helpers/vm_infra_helper/textual_summary.rb | 33 ---------------------- 4 files changed, 10 insertions(+), 68 deletions(-)
Created attachment 1017156 [details] retirement state Verified in 5.4.0.0.22.20150420163946_26004d1
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://rhn.redhat.com/errata/RHBA-2015-1100.html