Operations Manager fails after saving resource config with a 500 error.
The following stacktrace is displayed after saving config:
500 An error occurred.
Contact VMware Technical Support to report the problem.
Back to dashboard
NoMethodError
undefined method `[]' for nil
/home/tempest-web/tempest/web/app/presenters/api/product_jobs_resource_configs_update_presenter.rb:12:in `block in apply'
/home/tempest-web/tempest/web/app/presenters/api/product_jobs_resource_configs_update_presenter.rb:9:in `each'
/home/tempest-web/tempest/web/app/presenters/api/product_jobs_resource_configs_update_presenter.rb:9:in `apply'
/home/tempest-web/tempest/web/app/controllers/resources_controller.rb:26:in `update'
/home/tempest-web/tempest/web/vendor/bundle/ruby/3.3.0/gems/actionpack-8.0.2/lib/action_controller/metal/basic_implicit_render.rb:8:in `send_action'
/home/tempest-web/tempest/web/vendor/bundle/ruby/3.3.0/gems/actionpack-8.0.2/lib/abstract_controller/base.rb:226:in `process_action'
/home/tempest-web/tempest/web/vendor/bundle/ruby/3.3.0/gems/actionpack-8.0.2/lib/action_controller/metal/rendering.rb:193:in `process_action'
Ops Manager 3.0.39
Under certain circumstances, certain instance jobs may have no parameters configured and Ops Manager does not guard against this situation on older versions.
The solution is to upgrade Ops Manager to 3.0.40+ or higher which contains a fix. Please obtain the latest Ops Manager release from Broadcom Downloads and arrange an upgrade following documentation for Upgrading your Tanzu Operations Manager deployment.