Ops Manager Network Configuration Failures in VMware Tanzu Application Service (TAS) for VMs

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Operations Manager (Ops Manager) requires all service brokers to be associated with a service network. When this condition is not met, it can result in vague error messages.

Vague error messages show up when saving networks in the BOSH Director's tile or when performing product configuration during automation staging:

{"errors":{"base":["undefined method `name' for nil:NilClass"]}}

Obtain the rails debug logs. This can be found here: https://OPSMAN_FQDN/debug/rails_log

Look for the stack traces surrounding the error:

E, [2020-01-15T19:34:47.621778 #716] ERROR -- :         Exception caught via rescue_from (code 500):
        (See app/controllers/application_controller.rb)
        undefined method `name' for nil:NilClass
    /home/tempest-web/tempest/web/app/validators/service_networks_assignment_validator.rb:26:in `block in service_networks_remain_present_for_actual_products'
/usr/local/lib/ruby/2.4.0/delegate.rb:83:in `each'
/usr/local/lib/ruby/2.4.0/delegate.rb:83:in `method_missing'
/home/tempest-web/tempest/web/app/validators/service_networks_assignment_validator.rb:20:in `service_networks_remain_present_for_actual_products

The specific error in the rails debug logs:

/home/tempest-web/tempest/web/app/validators/service_networks_assignment_validator.rb:26:in `block in service_networks_remain_present_for_actual_products'

This indicates it is verifying service networks for service brokers at the the time of failure. Ops Manager requires all service brokers to be associated with a service network.

 

Environment

Operations Manager/Foundation Core

Cause

The error occurs because Ops Manager requires all service brokers to be associated with a service network. 

Resolution

1. Check all service broker tiles to confirm they are associated with a service network and the service network exists. If all apparent service brokers are correctly associated with service networks then proceed to step 2.

2. Verify all recently installed tiles to make none of them declare itself as a service broker by mistake. This can be confirmed in the tile's yaml definition file. The definition file can be obtained by unzipping the tile, changing the .pivotal to .zip and unzipping, and it is located under the metadata / directory.

Search for the property called service_broker, this is typically among the first properties listed in this file and should be located near in the top section.

It will look similar to this:

service_broker: true

The resolution path will be determined by the source of the tile:
 

a. If this happens with a Tanzu specific tile, contact Support.

b. If this happens with a tile from a Tanzu partner, contact Support for the third party partner. Look at the tile on Broadcom Tanzu Network, it will show how to get support for a given tile.

c. If this happens with a custom tile, one developed by a customer, then the you must address this or uninstall the tile.

d. If this happens in a tile developed by the field team, like a Platform Architect or a Solutions Architect (these are not supported), then the you must fix or contact their PA/SA and request help to fix.