Vm.stop is never called during the retirement phase because generic pre_retirement state-machine method, moving to automate.
ETA: because there is no generic pre_retirement state-machine method
https://github.com/ManageIQ/manageiq/pull/10415
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/5a99030b06f3a1302b65ac53ff335aa83923ab63 commit 5a99030b06f3a1302b65ac53ff335aa83923ab63 Author: Tina Fitzgerald <tfitzger> AuthorDate: Thu Aug 11 14:42:14 2016 -0400 Commit: Tina Fitzgerald <tfitzger> CommitDate: Thu Aug 11 14:42:14 2016 -0400 Automate - Cloud Retirement - Add google specific retirement states. https://bugzilla.redhat.com/show_bug.cgi?id=1364894 .../StateMachines/Methods.class/__class__.yaml | 40 ++++++++++++++++++++++ .../Methods.class/__methods__/pre_retirement.rb | 10 ++++++ .../Methods.class/__methods__/pre_retirement.yaml | 12 +++++++ .../Methods.class/checkpreretirement.yaml | 2 ++ .../StateMachines/Methods.class/preretirement.yaml | 2 ++ 5 files changed, 66 insertions(+) create mode 100644 db/fixtures/ae_datastore/ManageIQ/Cloud/VM/Retirement/StateMachines/Methods.class/__methods__/pre_retirement.rb create mode 100644 db/fixtures/ae_datastore/ManageIQ/Cloud/VM/Retirement/StateMachines/Methods.class/__methods__/pre_retirement.yaml
Greg, the PR doesn't have darga label, but we have 5.6.z clone for this bug. Are we going to backport this to darga?
Yes, it should be back-ported. I added the darga/yes label.