New commit detected on ManageIQ/manageiq-content/fine: https://github.com/ManageIQ/manageiq-content/commit/a8e548f809798a62288d66f0e70a65c39a1a1bfe commit a8e548f809798a62288d66f0e70a65c39a1a1bfe Author: Madhu Kanoor <mkanoor> AuthorDate: Thu Jun 29 16:53:02 2017 -0400 Commit: Satoe Imaishi <simaishi> CommitDate: Fri Aug 11 15:03:46 2017 -0400 Merge pull request #94 from billfitzgerald0120/vm_retire_extend Refactor and create tests for 2 vm_retire_extend methods. (cherry picked from commit 3aea4c41216d48fdae28c7b7dfb6e80878fd3e29) https://bugzilla.redhat.com/show_bug.cgi?id=1480734 .../Email.class/__methods__/vm_retire_extend.rb | 137 ++++++++++-------- .../Email.class/__methods__/vm_retire_extend.rb | 157 +++++++++++---------- .../__methods__/vm_retire_extend_spec.rb | 89 ++++++++++++ .../__methods__/vm_retire_extend_spec.rb | 89 ++++++++++++ 4 files changed, 338 insertions(+), 134 deletions(-) create mode 100644 spec/content/automate/ManageIQ/Cloud/VM/Retirement/Email.class/__methods__/vm_retire_extend_spec.rb create mode 100644 spec/content/automate/ManageIQ/Infrastructure/VM/Retirement/Email.class/__methods__/vm_retire_extend_spec.rb
I was able to reproduce the error "`method_missing`: undefined method `retirement` for #<...> (NoMethodError)" on older versions of 5.7.z and 5.8.1 by just creating a new button under VM and Instance that calls vm_retire_extend. VERIFIED in 5.8.2.0.20170824192913_b09a5f8
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-2017:3005