Created attachment 1023076 [details] Extract from production.log Description of problem: Unable to reprovision a foreman configured system; error page appears when the reprovisioning button is clicked. Version-Release number of selected component (if applicable): 5.4.0.0.25 How reproducible: Always Steps to Reproduce: 1. Setup a foreman provider 2. Select a configured system 3. Click the "Lifycycle > Provision Configured System" button Actual results: Error page with: undefined method `common_configuration_profiles_for_selected_hosts' for #<Class:0x000000086adb48> [miq_request/prov_edit] Expected results: A provision dialog is shown. Additional info:
usually undefined method blah for #<Class> implies you called self.class in a class method.
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/f2668ad23f02913efcd31732c7fb085940ed11b5 commit f2668ad23f02913efcd31732c7fb085940ed11b5 Author: Brandon Dunne <bdunne> AuthorDate: Thu May 7 10:03:53 2015 -0400 Commit: Brandon Dunne <bdunne> CommitDate: Thu May 7 14:46:43 2015 -0400 Use the updated method name https://bugzilla.redhat.com/show_bug.cgi?id=1219439 vmdb/app/models/miq_provision_configured_system_foreman_workflow.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/153a4d25edea5d86769c06d713619d8fafb2128f commit 153a4d25edea5d86769c06d713619d8fafb2128f Author: Brandon Dunne <bdunne> AuthorDate: Thu May 7 15:01:57 2015 -0400 Commit: Brandon Dunne <bdunne> CommitDate: Thu May 7 15:01:57 2015 -0400 Add spec for MiqProvisionConfiguredSystemForemanWorkflow Specifically #allowed_configuration_profiles https://bugzilla.redhat.com/show_bug.cgi?id=1219439 vmdb/spec/factories/miq_dialog.rb | 5 +++++ vmdb/spec/factories/miq_request_workflow.rb | 6 ++++++ ...iq_provision_configured_system_foreman_workflow_spec.rb | 14 ++++++++++++++ 3 files changed, 25 insertions(+) create mode 100644 vmdb/spec/models/miq_provision_configured_system_foreman_workflow_spec.rb
Verified fixed in 5.4.0.0.26 - 5.4.0.0.26.20150511144816_f924bd4.
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